» Mon Oct 18, 2010 6:12 pm
amd released an interesting cap1 for 11.3 drivers today , which "resolves flikering seen with crossfire " ( for steam users)
Oh come on, you write it, but don't get it!? This CAP version is for the STEAM version of the game! You wrote you have the retail version... And wondering why it isn't working!? Wait, until the retail version CAP is out!
PS.: There's already a thread about the new CAP... Use the goddamn search engine!
Except for the fact that crossfire profiles work by the exe's name. Thus they're both "Crysis2.exe" As a longtime user of crossfire, I can honestly say there's never been a difference between the steam version and the retail version.
Also, read my above post where I said I got it to work, so clearly it DOES work.
@CatalystCreator wrote via twitter, that the Steam and the Retail versions of Crysis 2 behave different, thus different profiles are needed.
And yeah, Catalyst A.I. recognizes .exe names. Or the Game name reported from the .exe. That's why we have the problem, as the existing Crysis 2 profile was meant for an earlier game version. CryTek changed something and this messed all up.
I use CrossFire for quite some years, so I quite know what I'm talking about.
No excuse for you, not using the search engine! Everything has been said in the other threads!