Build 59210, Crossfire (ATI) and Crysis.exe incompatible?

[Richey79]

Hi all,

Firstly, 1.04 vanilla works great for me when I rename Arma2.exe to Crysis.exe. Catalyst then doesn't strobe when I play any mission set earlier than 10am and later than 4pm.

When I did exactly the same, renaming Arma2's Beta.exe in the Beta folder as Crysis.exe and run, the whole lighting system screws up and everything has massive blown highlights, rendering the game unplayable. I'm using one HD4870 and one HD4870 x2 in Crossfire (I know ATI don't recommend this combo, but it works fine).

Anyone else experienced this? -I realise it's more ATI's responsibility to make sure that Arma2.exe actually triggers a Crossfire profile that works, but I'm worried that patch 1.05 might leave Crossfire users with no fully usable profiles at all.

Cheers,

[kklownboy]

I just tested with Crysis.exe on XP64, Its no different than Arma2.exe, lighting wise. But when i do use Crysis.exe i loose my CFX, and its been that way since the 9.8s, and it only uses CFX with Crysis.exe if i use the -winxp flag ( yeah even on XP64...)I havent had the strobe since 9.8 Cats, with the arma2.exe. Same for the 9.9s. I do use HDR at 32. Also for me looking at the sun/reflective objects around 10am and 4pm can be more intense ect.
PS; its the same on V64 for me too. no diff in the light, and crysis.exe breaks CF unless i use -winxp. But arma2.exe is just fine, actually better.
A pair of 4870x2's

[Dwarden]

you tried uninstall beta first and reinstall latest ? also it may be related to CF having issues with Render Frames Ahead values (you need fidle with that)