"Photoshop CC (2014)"

[digitaldog]

Unfortunately that did not work for me on a Win 7 64-bit computer. 

In what way? Any info will help fix the issue.

[yaredna]

If you want facts and/or knowledge, I'll give it–if you want to rant and rage, screw you...and yes, the Photoshop CC (2014) full app upgrade actually enforces my statement that dual code bases resulted in Adobe dropping CS7...the original CC app needed to have a whole new code branch, hence the new CC (2014) code base. There's only so much Adobe can do with code before a new app code needs to be spawned. If you understood software development, you would understand this.

For all software engineers on this forum, this statement from that same guy (??) whose inferiority complex pushes him to insult other members (e.g. "screw you" in the quote above), is simply insulting to their knowledge and their day jobs.

Branch management, version control, installation scripts, licensing demons, etc.. There are absolutely no technical reasons behind Adobe's decision. It was a business decision. Is it the right business decision for their shareholders? Future will tell. So far, what we have seen:
. Fewer key features introduced in comparable timeframes
. Emergence of lot of alternative software
. Move from PC to tablet continuing at a rapid pace
. Pirating is still going strong, particularly OUS

Oh well, that ship has sailed...

[Schewe]

Oh well, that ship has sailed...

Yep...so, still beating the dead horse? That horse is dead (and you are still wrong about the "technical issues" relating to major code branches of super large cross platform applications but it's clear nothing I say will make a dent in your armor).

Sorry, I chose not to engage in this worthless discussion...from now on, you are talking to yourself.

[David Luery]

In what way? Any info will help fix the issue.

Apologies for not being more informative.  I have a Win 7 64-bit computer.  I reinstalled PKS 2.0.7 after Ps CC2014 had been installed.  But PKS did not show up in as selections in the File > Automate menu. 

For that reason plus the fact that some panels I use did not work in CC2014, I have uninstalled CC2014 for the time being.

Best regards,

David

[digitaldog]

I reinstalled PKS 2.0.7 after Ps CC2014 had been installed.  But PKS did not show up in as selections in the File > Automate menu. 

The only time I've heard that happening is if there's a 32 bit plug-in installed for 64-bit Photoshop or vise versa. I'd download the latest installer and try again. You can also go into the PS help menu, select System Info and you'll see a report that includes what plug-in's loaded, which didn't.

[Gerald Barber]

I have the same problem - no PKS in Photoshop CC 2014. I tried downloading the latest installer and reinstalling and this did not solve the problem.

[digitaldog]

I have the same problem - no PKS in Photoshop CC 2014. I tried downloading the latest installer and reinstalling and this did not solve the problem.

Again,run the system info from Photoshop's Help menu, that would give us a clue what's going on.
Everything on Mac works as it should thus far. So maybe it's the installer? If you see it not loading in the report, that tells us one thing.

[Gerald Barber]

Again,run the system info from Photoshop's Help menu, that would give us a clue what's going on.
Everything on Mac works as it should thus far. So maybe it's the installer? If you see it not loading in the report, that tells us one thing.

I did. It's not listed as a loaded plug-in in help->system info, nor is it listed in help->about plug-in. It was listed in both places the previous version (Photoshop CC x64). I downloaded the installer today so I'm using the latest version of the installer but, for some reason, it is not getting installed correctly. If it help I'm running Windows 8.1 x64 Update I.

[digitaldog]

I did. It's not listed as a loaded plug-in in help->system info, nor is it listed in help->about plug-in. It was listed in both places the previous version (Photoshop CC x64). I downloaded the installer today so I'm using the latest version of the installer but, for some reason, it is not getting installed correctly. If it help I'm running Windows 8.1 x64 Update I.

Send me an email, I'll send you a zip to install manually.

[digitaldog]

Actually this may help other Win users. Here's a zip of PhotoKit Sharpener II that isn't an installer. Unzip, place directly into the Plug-In folder. Does it work? If so, we need to look into the installer itself. You can find the zip at:

http://www.digitaldog.net/files/PKSII_Win_toolbox plug-in module.zip

Make sure you also don't have any PG plug-ins in the CC 2014 directory.

[Gerald Barber]

Actually this may help other Win users. Here's a zip of PhotoKit Sharpener II that isn't an installer. Unzip, place directly into the Plug-In folder. Does it work? If so, we need to look into the installer itself. You can find the zip at:

http://www.digitaldog.net/files/PKSII_Win_toolbox plug-in module.zip

Make sure you also don't have any PG plug-ins in the CC 2014 directory.

We're making progress. I downloaded the zip file, unzipped it, deleted the PG plug-ins that were in the CC 2014 directory (presumable from the install attempt earlier today) and placed the newly downloaded files directly into the Plug-in folder. The plug-ins now show up in help->system info, help->about plug-in, and as a selection option in file->automate. Unfortunately, attempting to run any of the PG plug-ins from file->automate crashes Photoshop with the following generic error message "Adobe Photoshop CC 2014 has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."

[digitaldog]

Windows will close the program and notify you if a solution is available."

Yup, seems two issues. One is the installer which the zip process bypasses but then the bug you report which our engineer is looking into.

[alfin]

PKS2 installer works with CC 2014 on Windows 7/64.

[datro]

...the original CC app needed to have a whole new code branch, hence the new CC (2014) code base. There's only so much Adobe can do with code before a new app code needs to be spawned. If you understood software development, you would understand this.

I do understand this (I'm in the software business), and I'm also in agreement with an earlier poster that it is actually good that Adobe allowed for both CC and CC 2014 to coexist.  But here's where I think Adobe should go one step further:  As the OP pointed out, it is a REAL PAIN to have to re-create all your personal preferences each time a new code base for PS comes out.  I for one would like to see some effort from Adobe to carry forward all possible user preferences into the new version.  MANY software vendors do this as a matter of course with new installs over an existing application, and it would certainly make our life easier.

Dave

[Peter McLennan]

Adobe, I love the CC system, but this is retarded.

It is not absolutely clear.  For example, what's the difference between "Install" and "Try"  ?  This appears on my CC installer app.  I'm a full CC subscriber, so why the "try"  ? 

Besides, Yoda said "There is no try"

[Lupin]

Has anyone found a fix for the interface bug in Photoshop CC 2014?

There are four choices of UI font size - Tiny, Small, Medium and Large - but it stays on Tiny even if one of the others is selected.

[digitaldog]

There are four choices of UI font size - Tiny, Small, Medium and Large - but it stays on Tiny even if one of the others is selected.

Quit and restart?

[Lupin]

Quit and restart?

Restarting makes no difference - it's still stuck on 'Tiny' and the menus are all unreadable for me (font is far too small).

This is a bug in the UI. The 'UI Font Size' selector (in Edit>Preferences>Interface) worked fine in all previous versions of CC, but it doesn't work at all in CC 2014.

[digitaldog]

Works on this end after restarting. But to be clear, what changes is the font size in the Option's bar using Text Tool.

[hjulenissen]

...If you understood software development, you would understand this.

I think that this is a weak argument. Are you a world authority on software development? If I could find some credited software developer that disagreed with you, would you change your mind?

-h