Do the Catalyst Version numbers show in CCC? Like "12.4" as it should be? Some users have problems that the versioning number is missing, but the driver is installed correctly.
If so, you can edit the version number yourself in the registry! If you have this issue, I'll look the path up you need to edit.

what i dont get is how does a very specific driver 'not work' with the game & how does blizzard know that, what does that even mean? corruption? crashes? someone said the 8.97 beta leak worked fine with no error from the game....

but anwyay, you can just atiumdag.dll from 12.3, put it where diablo3.exe is, done... no rollback needed

EDIT: just noticed this only appeared in 12.4cap1, was not in 12.3cap1, also... not sure but... did someone make a typo?

what i dont get is how does a very specific driver 'not work' with the game & how does blizzard know that, what does that even mean? corruption? crashes? someone said the 8.97 beta leak worked fine with no error from the game....

but anwyay, you can just atiumdag.dll from 12.3, put it where diablo3.exe is, done... no rollback needed

Apparently this whole issue has been resolved. There was a post made by blizzard on bnet forums that there shouldn't be any issues. It was apparently a glitch and one of the reps was too quick to press to nuke button.

Apparently this whole issue has been resolved. There was a post made by blizzard on bnet forums that there shouldn't be any issues. It was apparently a glitch and one of the reps was too quick to press to nuke button.

Can you please give a link the that blue post so we can confirm please. Thanks

Do the Catalyst Version numbers show in CCC? Like "12.4" as it should be? Some users have problems that the versioning number is missing, but the driver is installed correctly.
If so, you can edit the version number yourself in the registry! If you have this issue, I'll look the path up you need to edit.