I just installed windows 8 and i got a lot of problems with CS6 Extended (Design and web premium creative suite installed) and GPU use (i never had a problem under windows 7).
My sistem is updated and equipped with a I7, 8 GB RAM and a Radeon HD 5870 card and i'm working winth Canon EOS 1Dx and EOS 5D mkIII raw files (but the problems appear also with snall jpg)
When PS use the GPU acceleration the display becone crazy showing a lot of different things.
This is the first list of things appening:
A) very often (about 95% of times) when i use the crop tool the image start to flicker from visible to black ( http://www.asf-images.com/ps1.jpg ) so it is impossible to work; sometimes (50% of times) images become visible again moving the mouse to a different location and after moving again the mouse the images fade to black and so on... frustrating.
B) cropping become very slow
C) during crop images a big distorsion appear ( http://www.asf-images.com/ps2.jpg)
D) sometimes during crop or changing the GPU setting the border outside the image become filled of gray/white little square as a trasparent layer (http://www.asf-images.com/ps4.jpg)
E) after canceling the crop tool action (using the cancel button in the Option tool bar) the image fade to black (http://www.asf-images.com/ps5.jpg )
This appens also with blur tool, liquify and all that use the mercury engine.
Changing GPU drawing mode from normal to basic or advanced all works but after closing and reopening PS problems are still visible
Sometimes the graphic card GPU disapper (http://www.asf-images.com/ps3.jpg)
Last: sorry for my english :-)
You're not alone.
Apparently the display drivers provided with the OS are insufficient to support Photoshop's GPU usage well enough.
Have you tried visiting the AMD web site, seeking out the latest Catalyst driver release for your hardware and OS, and downloading/installing it?
Unfortunately, this is one good reason among many that you really should avoid upgrading to a brand new operating system on the first day of its release. I know this doesn't help you, Zottwalker, but this is written for those who haven't upgraded yet.
Hm, maybe the manufacturers of the products ought to be the ones to "blaze through" the problems before the products are released.
Gee, what a concept - Microsoft, AMD, and Adobe all working together with the pre-release versions so that the released version actually works for users.
I believe that Chris Cox worked on trying to get AMD and Microsoft to include proper and working drivers for the Windows 8 release. But apparently that input wasn't enough to get the job done, becuase in these modern times greedy businessmen always push to release software products before they're finished. It can always be fixed later through the "cloud", right? Sheesh.
But even beyond that, there has been an important shift: Microsoft no longer considers it a high priority that you should actually be able to WORK with Windows. Their focus has shifted from powering business to powering toys (consumer tablets, that sort of thing). As such, they care most about the applications that they'll be selling in their shiny new App Store, and almost not at all whether you and your desktop applications work. Thus the very basis for the philosophy "Microsoft released it, it must be worth having" is now suspect.
Some of that can be mitigated. I've been running Windows 8 for a year now, and I've had my Windows 8 book done and on sale well before the public release. Some folks have taken advantage of it and have had a much smoother experience, but I can't document around software that just doesn't work.
As it is, my best advice was and remains this: Watch and wait while other poor users blaze through the problems.
I sound like a helluva skeptic, don't I? But I'm really an early adopter technophile who has been around since before there ever was a Microsoft. That should help you understand the weight of my statement above.
Hi Noel, yes drivers uploaded and up-to-date.
Onestly speaking (and before becoming a journalist i studied and worked in IT field) this could happens and i could accept from a garage-band software house; not from billion dollars companies like M$ and Adobe; i pretend (not espect, pretend) that they test theyr product before starting to sell it.
And test in deep. My crefit card worked properly when i clicked on "Buy" button; i didn't paid half of money because something goes wrong ;-)
I think that until we accept this saying only "yes, it always appens with new product" nothing will change.
My car worked from her first day why not my OS??? :-)
Noel Carboni wrote:
Watch and wait while other poor users blaze through the problems.
You surprised me with the above statement. I though you were a sadist and enjoyed the pain new OS and device driver inflect upon early adopters. You not warped after all.
One of the best thing about retirement is I'm no longer required to be the fist to test new releases of software.
Photoshop is about the only program I test new releases of. For I always want what's new in ACR. I don't load the beta code for it can not be installed as standard Photoshop. I don't feel the need to spend $300 for 3D support I have no need of it.
I never update my ATI drivers before I read your driver threads.
My laptop is about to die so Windows 8 may be in my future. Start testing more and report. I want some good reading before I commit.
You not warped after all.
Not quite sure how to take that.
I enjoy scoping out new technology. In fact, I have already tested Windows 8, mostly in virtual machines, but even on hardware. In my case I tested on a workstation with a Radeon HD 5670 before I sold that machine. It seemed to work, but I can't say I put much time at all into testing Photoshop on it.
I have been running Windows 8 in virtual machines since the day the first public preview was made available.
So I do like taking on the pain of a new OS release myself. But as you say, I tend to post my findings here in hopes that I can save others some hassles. In the case of display drivers, there's often not an easy way to roll back unless you really know the ins and outs of Windows.
One has to wonder why display driver writers don't do a better job of that, making it possible for users to install/uninstall versions at will. Everybody does it! Even gamers, to whom the hardware and software is targeted are continually trying different drivers to try to get the best looking blood spatter and highest frame rates.
But my particular recommendation here goes beyond just display drivers... Windows 8 is the first release from Microsoft that actively takes a step DOWN in functionality. Other than their new play-toy Metro interface, the desktop side of Windows 8 is LESS functional than Windows 7. There's simply no compelling reason to upgrade!
I've had the exact same issue after uprgrading to WIN8 PRO so I've tested a couple of things like changing the Photoshop.exe to run in compatibility mode or to install the latest Catalyst suite (12.11 beta) but neither approach managed to resolve the problem. Anyway I've found a temporary work around: Go to EDIT > PREFERENCES > PERFORMANCE and uncheck the "USE GRAPHIC PROCESSOR" box - close Photoshop and restart it.
Works like charm here and hopefully on your side too.
"Works like a charm" usually means that something provides all the functionality. With Use Graphics Processor unchecked you have disabled a number of features some would consider critical. That may be a workaround to having a working GPU driver, but it's not going to be an acceptable fix for most folks.
Hi Wally, unfortunately unchecking the use GPU box you disable all features that benefit of gpu acceleration and seems to me like "i feel pain in my left leg; ok, i'll cut my leg to avoid pain".
If in your new car the AC doesn't work and that vendor just tell you: simply, to avoid probles don't use your AC what do you think about? You could consider this answer the solution to the problem?
I tried a lot of programs and games to test my graphic card and i got problems only from creative suite; so need to ask myself: where is the bug? In windows? In to the driver? In mercury???
I hope in q quick answer...
This is Adobe's temporary solution until they can work things out with AMD: http://helpx.adobe.com/photoshop/kb/image-background-transparent-or-fl ickers.html
Thanks for your suggestion Carl, but as i wrote in my first message this solution doesn't work; seems good just after the settings change; but once i close PS after reopening PS the problems is still present and live :-(
Yes, problems are less frequents but still on. This in all 3 GPU modes from basic to advanced.
The curious thing is that frequency is erratic; i means that sometimes when i start to work with PS i notice no probles and i had no problems for all the session.
Closing and reopening PS flickering and all the rest of the dark band came out again. Frequency is not tied to gpu mode but is erratically connected to the work session
Have you tried reinstalling with compatability mode set to windows 7?
Right click the installer setup.exe file
Go to properties
Go to compatibility
Select windows 7
Run the Setup.exe
Don't know whether this will help at all, but I am about to install windows 8 myself, would be very useful to know if this will help resolve/prevent any issues when i come to installing CS6.
Running CS5 with Windows 8 64bit and was having all the issues as the original poster. Tried updating drivers, GPU settings, etc with no luck. Changing to Win7 compatibility mode seems to have fixed the problems for now. Hope I can get through all the files I am wokring on now!
Hi Zottwalker, My graphics processor was disabled by the latest display driver, this may be related to your problem . I searched and replaced it we an older driver, works fine now, hope this helps.
Further to my earlier post, have a look here http://www.minecraftforum.net/topic/1086017-ati-radeons-and-windows-8- the-fix/
Sorry you are having a problem. We have identified the problem and are working with Intel and AMD on a solution. In the meantime please run PS in Basic mode. This should clear up most of the transparency around the image and flickering issues.
I just got a new computer which had windows8. I bought PS CS6 at the same time. I am happy to have found this post because I didn't understand why all the flickering and changing background screens was going on. It drives me nuts! Plus, it's very hard to edit photos when they are flickering or going completely black. I did the suggestion listed above from David and tried editing one photo....no flickering or changing backgrounds from white...to gray...to black....to checkerboard. So far, so good.
I have an issue with Windows 8 and Photoshop CS6 as well. I just installed Windows 8, then reinstalled CS6, but as soon as I open Photoshop, it locks up. Everytime. No matter what. I cannot change any settings because I cannot get to any menus in Photoshop. As SOON as the Workspace loads, the program hangs. Every time. What could be the problem?
xfile 102, It seems the problem is PS CS6 and Windows 8 do not get along so well together. I just wonder if Adobe will send something to correct the issues to those of us that are having these problems.
I Have this problem as well. I can run CS 5 in Windows 8 without problems. Adobe programming has always been dubious. Clearly GPU acceleration in CS6 with ATI drivers was never adequately tested by Adobe. It has nothing to do with Windows 8 and everything to do with incompetent Adobe programming and their attitude toward customers. Class action suit?
Bmoag, there are a number of problems listed in this thread. What goes wrong for you, specifically?
Have you tried all the Advanced GPU modes (e.g., specifically Basic mode, and remembering to restart Photoshop after making any change)?
We tested ATI/AMD drivers quite extensively, and worked with AMD to resolve all issues found.
But Win8 came out after Photoshop CS6, and the Win8 GPU drivers have many known problems, in addition to know GPU bugs in the OS itself.
Please read the topic before adding ridiculous claims of responsibility.
I mentioned the problems I am experiencing in a post listed above. Noel, the problem in changing to Basic GPU mode is that you lose the ability to use certain tools (for example, the blur tool is one of the tools that do not work for me in CS6/Windows 8 when I make the change to Basic mode.) I would like to have Photoshope set up in advanced mode, have the ability to use all the tools that are offered in CS6, and have it work correctly.
Noel, MANY of us arent even able to get PS to load fully without hanging to change any settings. Even after multiple reinstalls. Somepeople it hangs at load, so there is no opportunity to change settings and reload.
@ Chris - Funny how many other GPU intensive programs and games I have that work FLAWLESSLY with Win8, yet you clain Win8 to be the problem when the ONLY program I have problems with is CS6.
Chris, have you considered a secret key combination during startup (or a separate program) that would allow people to reconfigure GPU settings? With my accelerated plug-ins I provide a configuration dialog that can be invoked separately.
I thought you already had some interlocks in place ("GPU Sniffer Crashed") to prevent GPU-based Catch-22 lockups. Isn't there some path that should lead to [ ] Use Graphics Processor being disabled entirely?
xfile - the only time we've had people failing to load Photoshop CS6 was due to bugs in third party plugins, bugs in video card drivers, or corrupt font files.
Other than the GPU bugs in Win8, most people aren't having any trouble running Photoshop on Win8.
Games use the GPU differently from apps like Photoshop.
Just because the bugs only manifest in some applications and not others does not mean that they do not exist. In this case it probably means that the game is using more simple 3D code and fewer shaders. And we really have been working with AMD and Microsoft, and really do know the nature of these bugs.
If Photoshop crashed or hung during a GPU call, we should disable it anyway on next launch (because we'll see a status file that says the GPU calls never finished).
I'm not sure of any other workarounds to force the GPU off.
Any further news on this?
I've had to completely disable GPU usage in Photoshop in order to get it to behave. But that of course turns off a lot of advantages CS6 brought.
I'm concerned this is just going to live on and never get fixed.
That was a nice way to say "how could we possibly know, Podsnap, since you haven't provided any detailed info about your system?"
ATI is still advertising Catalyst 12.11 beta 11 as their latest driver build, with 12.10 being their latest release. Both are utterly a bust with Photoshop on Windows 7; I have heard they're not really functional with Windows 8 either.
I guess it was ATI's turn to feel the heat, since we're not hearing as many complaints from nVidia users lately.
Podsnap, have you tried enabling the GPU but setting it specifically to Basic mode? You have to close and restart Photoshop to test. Also, try the various checkboxes on/off in the advanced settings dialog.
Podsnap....I have the same concerns as you. I changed GPU to Basic...which took care of wierd way that CS6 behaves...but, by changing to Basic mode I lost tools that are "suppose" to be available to use in CS6. I wonder the same thing as you....since I have never received any information from Adobe as to what to expect....as to if the issue will ever be resolved and if so when and....how will those that have CS6 be alerted to the problem being resolved.
Europe, Middle East and Africa