AMD Catalyst™ 11.5b hotfix for CF issues in Brink and Witcher 2

[dark2099]

AMD has released an updated hotfix, mostly for Crossfire probs in Brink and Witcher 2 (which should be added to the CAP's in the next couple of days too). All the info is provided on AMDs site, so I won't bother repeating it.

http://support.amd.com/us/kbarticles/Pages/AMDCatalyst115ahotfix.aspx

11.5

11.5b hotfix

 

[AltecV1]

in witcher 2 it gave me 1 extra frame

 

[RejZoR]

Installing it for the sake of getting rid of GSOD's. Hopefully...

EDIT:
Had Cat 11.5a installed and when installing these, installer says that Driver is the same version as the one i already have. Hm?

 

[FierceRed]

As I've been waiting for this and actually have a decent CF setup unlike posts above, I'll install and comment on these in about 5~6 hours. Got an appointment to make in 3.

If someone beats me to it though, that's cool too since I won't be using FRAPS or any kind of FPS measurement (does Witcher 2 even have one??). Just a squint at the screen, run through the forest, first impression type of evaluation.

As it only "enables scaling" and doesn't mention any optimization or improvement, I'm not too hopeful the changes will be static across the 58X0/69X0 series. Should be interesting to compare the scaling between CF setups of both generations...

 

[FierceRed]

Wow, would you believe I just got in? What a crazy ass 48 hours.

Anyway, since there was a patch for Witcher 2 performance for the game itself, I suppose any gains from this hotfix are now moot or combined with the performance from the game and now indistinguishable. I'm using Steam, not Retail, so I can't/won't downgrade for a mere FPS comparison.

Improvements are being noticed across the board though, so no worries there. Practically everyone not on the cheapo GPU route are seeing improvements, while those definitely on the cheapo route are crying that they're still not buttery smooth. One thing that I'm sure is getting a lot of news coverage though is the HUGE BLINDING LIGHT SOURCE issue that was probably introduced with 11.5b and is totally AMDs fault. Oh yup, CatalystCreator is all sorts of confirming it, just checked.

So yeah, enjoy the improvements and shake your fist at AMD for letting that "Oh look, the Sun! Lets stare at it!" issue pass QC. And when they protest they're working on it and doing the best they can, shake harder.

I almost get the impression they didn't do anything specifically for Witcher 2, they just told the drivers to behave as if it were some other game/engine where CF scaled in the past and hoped for the best. Now we all have to wait for 11.5c (if we're lucky since 11.6 mid June is close enough from a business perspective) to clean up the mess.

Won't make me stop playing Witcher 2 though.