So far so good. The previous version would black screen then lock the computer (I could see a keyboard app in the keyboard screen still functioning for a few seconds) Didn't happen in games, just 2D apps.
I was running 2 x 6950's with the 6970 shader BIOS. I replaced them with a single Sapphire Tri-X R9 290. The 290 runs all the games I play at a much better fps. Crysis 3 runs great on highest settings.
Interesting, though I question the presentation as first impressions are, first impressions. The very first example screen capture are a best case Nvidia SLI and a worst case AMD XFR as seen when looking at screen captures further into the review.
I dont question their information, as I dont...
Yeah, Psycho is where I noticed it first, but a few other objects in the game are doing it too now. Just enough to be annoying. Not a big deal to run that setting on high instead of very high, I didn't notice that much of a difference between them. Just a little frustrating since my rig can...
I'm getting some graphical curruption with these drivers in Crysis 3. Narrowed it down to setting objects to very high. Backing the setting down to high seems to get rid of the issue.
There is another thread here saying Catalyst is reporting the wrong version number but the correct drivers are installed. Mine says 11.1 but I am running 12.4.
Blizzard posted a sticky, looks like the driver is supported, but they are recommending Radeon HD 2400, 2600, 2900, 3400, 3600 and 4500 graphics cards use 12.3
http://us.battle.net/d3/en/forum/topic/4876967911
Quote from another Forum (THW) Apparently the issue with 12.4 does not affect the newer cards i.e.. 5000, 6000, and 7000 series.
"One final note: we learned from a blue post on Battle.net that AMD's Catalyst 12.4 driver won't be supported in Diablo III. According to a follow-up response at PC...
GPU-Z reporting similar for me too. Correct driver version number, wrong Catalyst number. My guess is some obscure registry entry didn't update properly.
Interesting issue, downloaded and installed 12.4, CCC reports Catalyst Version 11.11 (which I was running before upgrading) Uninstalled 12.4, cleaned the drivers, reinstalled and CCC still reports 11.11
Both times there were no errors, the install reported everything successful. I checked the...
AMD drivers after 11.11 broke DVI data channel communication between my monitors and PC. My calibration software hardware calibrates the monitors. After 11.11 the software cant talk to the monitors, so that doesn't surprise me at all.
Thanks, I couldn't find anywhere on the AMD pages to report this problem. Going back to the previous version of the AMD video driver definitely solves the problem. But it would be nice to be able to run the latest supported drivers.
I don't use that particular software, but looking at the screen captures, I think Spectraview uses a similar screen. Are you using AMD's latest video drivers 12.1? If I remove 12.1 and reinstall 11.11, everything works again. I even tried their beta 12.2, that doesn't work either.
I would but after searching their web page, I haven't found anything other than hardware warranty repair contact info. I'm also curious if anyone else has had this issue and I posted this as something for folks to watch for.
The latest AMD video drivers (version 12) have broken the communication between my NEC Spectraview software and my monitors. I have to go back to version 11 to make it work. The software recognizes the monitors fine, but cant communicate with them over the DVI connection. I tried changing some...
No problems with flashed 6950's and drivers up to 11.11. But I dont buy games at initial release, I wait for the price to drop. Any problems are usually fixed by then. Tried 12.1 drivers, they broke my calibration software.
I unlocked 2 MSI Twin Frozr II's, people seem to have very good success rates still with the II version. I have heard recent success with the III version too.
Installed 12.1 preview. My LCD calibration software cant detect the LCD's anymore. Removed and reinstalled 11.11c all is fine. That sucks...
Hopefully that gets fixed in the final release, I was looking forward to custom profiles.