I've been enjoying nearly flawless performance from the Catalyst 12.6 driver set for my Radeon HD 5670 on Windows 7 x64, but as I always need to test new driver releases for my own products, I'm about to download Catalyst 12.8, released on August 15th, and see how it works with Photoshop CS6 et. al.

1. I encountered an error where the Microsoft Installer crashed during the update - this hasn't happened before with a Catalyst release. However, upon closing the installer the Catalyst Install Manager retried the installation of that component and it ultimately succeeded.

2. I did some before/after benchmarks, and after the restart the display performance is slightly better (e.g., 1% or 2%).

3. Photoshop CS6 subjectively seems to come up a little faster. I timed it with a stopwatch and from a cold start Photoshop comes up to the point where the UI is fully displayed iin 3.4 seconds. This is a few tenths faster than before (3.6 seconds). Not a huge difference.

5. I did some raw conversions, photo manipulation, Liquify, Lighting Effects. All worked flawlessly and quickly.

6. I did some 3D stuff, including opening some existing designs I have and trying some new stuff. Unfortunately, With one of my modestly complex meshes I think there may be some new slowness I'm seeing specifically manifesting as a few seconds lag whenever I switch to different elements in the 3D panel and before the preview and all the other panels update. It seems to work once there, and I've been able to move things around at about the same speed as before - the frame rate for that is decent, and possibly a little better than before. Trouble is, I never objectlvely characterized the time between switching layers before with this design, so I'm not really sure whether it's acting differently than before. It's just that I noticed it, and that may mean that it wasn't there before. It's on the hairy edge of distractingly slow. Rendering seems to work fine, as before, no difference in speed (and none expected, as rendering is all CPU activity).

7. On an attempt to map an image to the "Hat" preset mesh, I got a preview of the result, but then when I tried to rotate the Current View Photoshop crashed with this error:

This may say the Catalyst 12.8 driver isn't as good as 12.6, as I have been able to do most anything I want with Photoshop 3D before without a crash like this, and (I think) without the delays.

I'll continue to use 12.8 for a while, and I'll follow up here with more info as I learn it, but I'd say for now that if you have Catalyst 12.6 and no specific problems to solve, you might want to stay with that version.

I can confirm that with Catalyst 12.6 there aren't several second delays when switching between elements in the 3D panel, and so far I haven't seen any recurrence of the crashes, after having done exactly the same things with the 3D tools that led to the crashes I saw with 12.8.

I suggest against upgrading to Catalyst 12.8.

If you upgrade to Catalyst 12.8 and see problems with 3D operations, uninstall the Catalyst Install Manager (which uninstalls all the software and drops you back to the drivers supplied with Windows), then reboot, then install the Catalyst 12.6 software.

Once I went back to Catalyst 12.6 I re-ran the benchmarks and got almost identical numbers as 12.8, so I'm thinking it was just a fluke (maybe something was running in the background) that I saw slightly improved speeds. Even Photoshop comes up at the same speed as with 12.8 as well.

My system has been supremely stable for the rest of the day back on 12.6.

After having contacted ATI, they suggested that rather than install Catalyst 12.8 as a direct upgrade to 12.6, I should instead uninstall the older driver first then install the new one.

Miraculously, this actually worked!

I now have what seems to be a stable system running Catalyst 12.8, and it seems to run Photoshop CS6 quite nicely. I haven't seen one fault in Photoshop since having done the 12.8 install - no crashes and no sluggish responses to what should be quick operations.

I suspect the Catalyst installer must be at the root of the problems I saw before, rather than the driver itself, referencing the MSI crash I saw during the attempt to install it. Completly removing the old version and rebooting, then installing the new version seems to have done the trick.

I'm modifying my earlier recommendation to avoid 12.8:

If you choose to upgrade to Catalyst 12.8, I suggest you do this:

Go into the Control Panel and do a Change operation on the AMD Catalyst Install Manager, then choose the Express Remove All AMD Components selection.

When it is done removing the current driver, reboot. This will run your system on the drivers supplied with Windows.

Install the Catalyst 12.8 drivers, and watch carefully for any failures during the installation process. If you do see failures, uninstall and start again. AMD recommends a driver sweeper program, but I don't trust those. On the other hand with my knowledge I'm equipped to ferret the remnants out myself - I know not everyone can do that.

After having contacted ATI, they suggested that rather than install Catalyst 12.8 as a direct upgrade to 12.6, I should instead uninstall the older driver first then install the new one.

I'm surprised you say that. I thought it was accepted procedure to always uninstall the existing video driver first. I thought some people even run a cleaner utility too, before installing the new driver.

I don't know why video drivers specifically should give so many problems. If the installation supports upgrade, then it should work just as well, or not at all. It makes me wonder if I should take as much care with all of my different driver updates.

It's things like this which give PCs a bad name. I've been working with PCs for 25 years, and know their inner workings pretty well; what chance does a relative beginner have with this sort of unpredictable behaviour?

thats suppose to be the job of the installer, but then again, it also depends on who wrote the installation script. so far I haven't had to uninstall first. But with the issues Noel described, it may be my first.

On the ATI site they recommend uninstalling the old driver first before updating to a newer one (they have a few video guides that include this information). They've had this up on the site for quite a while now, probably at least a couple of years. So I agree, I thought it was pretty strandard practice, although it's a shame ATI can't incorporate removing the old driver into their installer.

Anyway, thanks for testing this out Noel. I was considering updating to 12.8, but to be honest, I was hoping you might post something about it before I went ahead!

I'm surprised you say that. I thought it was accepted procedure to always uninstall the existing video driver first. I thought some people even run a cleaner utility too, before installing the new driver.

I don't know why video drivers specifically should give so many problems. If the installation supports upgrade, then it should work just as well, or not at all. It makes me wonder if I should take as much care with all of my different driver updates.

It's things like this which give PCs a bad name. I've been working with PCs for 25 years, and know their inner workings pretty well; what chance does a relative beginner have with this sort of unpredictable behaviour?

I agree with you on that last paragraph.

And what's interesting is that the symptoms of the faulty install are very much like the ones people who are not happy with the Photoshop CS6 release have been reporting here - instability and lag. It was an incredibly disappointing performance, and there's no obvious indication it's the display driver's fault (except for Faulting module atio6axx.dll in the event log), because Photoshop is what doesn't work very well AND other things that don't use the GPU seem to work pretty well.

I tend to try to use things as they are intended, and ATI's Catalyst package seems to be oriented toward "set it and forget it", including such things as automatic checks for updates. The most disappointing thing is that their installation process was solid for quite a while - I've been directly upgrading their drivers with the new versions they release literally for years without problems.

The first indications of problems with this version were that MsiExec.exe (the Microsoft installer) actually crashed during the upgrade install of 12.8:

Having been a telecommuter for years, then running my own business with a geographically separated team, I have developed a pretty good intuition about what's happening elsewhere, and I sense a change - a change in management or funding or culture or something - at AMD/ATI with regard to their GPU driver development in about the last year. Most notably, they've just recently changed from a monthly release cycle to something longer. Whatever is changing there, it doesn't seem to be for the better.

Having been a telecommuter for years, then running my own business with a geographically separated team, I have developed a pretty good intuition about what's happening elsewhere, and I sense a change - a change in management or funding or culture or something - at AMD/ATI with regard to their GPU driver development in about the last year. Most notably, they've just recently changed from a monthly release cycle to something longer. Whatever is changing there, it doesn't seem to be for the better.

Maybe it's time to see if the grass is greener on the other side of the fence again? Before my 5670, my last few graphics cards had been nVidia. I swapped allegiances because of endless nVidia driver problems. My last ATI card was a Rage3D. Well, I say "last"; I then bought a Radeon, but ended up swapping it for an nVidia card after it had a 'disagreement' with the rest of the computer.

I'm not involved with PC hardware nearly as much as I used to be, when I worked in system building. The last time I did product research, I got the impression that nVidia was good but over-priced and ATI was good value but under-powered.

No problems with CS6 and an Nvidia GTX560Ti card running the latest driver 301.42 (WHQL) and more recently the 304.79 beta driver. I had a load of problems with an ATI card and drivers some months ago and moved to Nvidia then. No problems since.

I have to admit, Yammer, the thought had crossed my mind as well... Like you, I switched brands from nVidia to ATI after serious driver problems in the time of Vista, and if driver issues are going to start to plague the ATI brand, the decision could rightly be revisited. It's just not something ATI can screw up without consequences!

I have seen enough folks, however, reporting nVidia driver problems recently that the grass may not be greener. I don't think I'm ready to jump ship just yet; in my case this business with 12.8 is one of only a VERY few recent problems I've had with ATI drivers. I hope it stays the exception. So far today, after having gone through this exercisethings are going great in my world with the latest drivers.

I had a very old ATI drivers so I though why not update. I think I had 10.9 installed. I updated to 12.2 tough the drivers seem to work well the Catalyst Control Center crashes nevet put anything on screen. So I updated to 12.4 thing are the same CCC crashes. Installed 12.8 drivers seem to work well ADM I have installed work as does Photoshop to the best of its ability. CCC.exe crashes. Any idea as to how I can get Catalyst Control Center operational? I did see a very old ATI entry in the control palem Programs and removed that and the reinstalled 12.8 CCC still crashes on me.. In the programs all I see is AMD Catalyst Install Manager and the two AMD demo Ladybug and Mecha I have a HD 5770.

In the windows start meme the a Catalyst Control Center shortcut for "C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\CCC.exe" as well as in the widows right click popup window. Window 7 Pro 64bit

I can only suggest uninstalling everything then reinstalling, JJ. That's what worked for me.

CCC in my case provides the ability for me to manage my color calibration, and it makes it easy to check versions, but otherwise I agree - it's not all that useful.

I haven't mentioned that, while I use CCC, there are a lot of things ATI installs that I do disable - I remove a couple of things from the Path, I make one registry tweak to avoid having bunches of meaningless events logged, and I hide the root level Start menu they insist in putting in. I also disable the System Tray icon, since it's easy to access the CCC by right-clicking the desktop.

The Catalyst 12.8 driver would not load my monitor calibration files (*.icm), so I rolled back to 12.6 which works fine. One thing I noticed is that uninstalling the 12.8 drivers (using the install manager) was very slow; it took 5 or 6 times longer than normal.

I recently bought a 7850, and I know Hudechrome on this forum uses a 7750. Both seem to be good cards and work pretty well on Windows 7. I don't know how well they work on Windows 8 yet, though... I have chosen to hold off upgrading to Windows 8; it doesn't offer any compelling reasons for me to upgrade at this time.

Earlier today, for my 7850, I installed the ATI Catalyst 12.11 beta drivers. Normally I don't install the beta releases, but in this particular case I had a pretty bad problem with the 12.10 release that was resulting in a lot of Photoshop crashes.

I'll give a cautious thumbs-up to 12.11... So far, in a few hours of fairly intense Photoshop work I haven't had a single glitch.

I did 12.8 . I have had no problems with installation or operations save the fact that OpenCL keeps unchecking itself, as it always has, no matter the driver. I am beginning to believe it is a HW problem but it would be ironic as the system is all AMD! (cpu, chipset and video.) OTOH, DXO uses it also and it never unchecks there.

I let the installer do all the work.

I've had three CS6 crashes just before installing 12.8, one of which was atio6axx.dll. So far, no crashes, with CS6 running continuously.

I ran liquify before responding and it runs fine.

I can't say that 12.8 is any better than 12.6, or worse (except for the new version of DXO which is buggy anyway!).

I am experiencing system behavior changes, subtle things like when CS6 firsts opens and that hasn't changed either. The most glaring is CS6 now takes 14 sec to open, and that's not after first booting the OS. It used to be 1/2 that, and that's also no different than 12.6.

I can only suggest uninstalling everything then reinstalling, JJ. That's what worked for me.

CCC in my case provides the ability for me to manage my color calibration, and it makes it easy to check versions, but otherwise I agree - it's not all that useful.

I haven't mentioned that, while I use CCC, there are a lot of things ATI installs that I do disable - I remove a couple of things from the Path, I make one registry tweak to avoid having bunches of meaningless events logged, and I hide the root level Start menu they insist in putting in. I also disable the System Tray icon, since it's easy to access the CCC by right-clicking the desktop.

-Noel

Remove, like what, specifically?

And, how does CCC figure in to calibration? I leave it strictly alone as it usually fouls things up.

Apparently the registry tweak to avert atikmdag events is no longer needed, so ignore that.

Since I need this system to be an sRGB reference system, I set the sRGB profile to be associated with the monitors then tweak the on monitor controls and video driver color settings until the monitor response for both monitors is as perfect as I can get it. I save that as a preset that CCC loads when it starts. If you're loading your profile the more traditional way you'll want to just leave that part of CCC alone.

I just finished 12.11 and wow! I'm back to a 7 sec load time for PS. Thanks for the tip. Now I hope that beta doesn't have a fatal bug somewhere! A sneak peek at Performance shows Open CL checked as well. I have to wonder though, why DxO isn't affected.

I looked at C:\Program Files (x86)\AMD APP\bin\x86_64;C:\Program Files (x86)\AMD APP\bin\x86 on my computer and only thex86_ 64 folder is present. Now, do you delete this folder, and if so, what is the outcome?

I can't imagine calibrating a monitor that way, especially as the profiler tool looks at a significant number of patches, something the eye would never be able to match.

I just leave the folders in place and remove the entries from the path. I wouldn't have touched the path but for the fact that something in the ATI folder affects my software builds in Visual Studio. Really, nothing should come before the system entries in the path.

I was going to move those AMD APP entries to the end of the path, but I couldn't find anything that didn't work without them entirely, and I figure leaner is better.

I'd rather not get into a discussion of the best way to ensure one's monitors produce the best color, nor have I told you everything I do. Suffice it to say I do what's right for me, and prior conversations on the subject have turned ugly, so I'd rather not go into it further.