Originally posted by: Cookie Monster
Originally posted by: elmer92413
Took a few clicks for me to get through to the site. Interesting graphical bug. I bet Nvidia tried to improve performance in Crysis by doing that, not realizing that would happen.
That could be one of the reasons. "over optimizing".
Or cheating?
You can decide.
169.04 is a beta driver... Let them tweak a little. If it makes it into WHQL, especially after this expose, I would consider it cheating though.
On a side note, I wasn't able to reproduce the results that EB had by renaming the executable. I didn't see a difference in fps or visual quality - the reflections in the water looked correct with the executable named Crysis.exe and Crysix.exe... I'm running Crysis in DX9 though, and I don't have everything ticked up to High. Does anyone know which setting(s) in particular would be affected by this? Is this only a DX10 thing?
Edit... In answer to my own question...
I tried it out in DX10, and sure enough I could see the reflections getting stretched when the executable wasn't renamed. It looks pretty bad actually because they stretch and then snap back every half second repeatedly. Performance showed a difference also:
Crysis.exe DX10 1680x1050 all settings High except Shadow quality = Medium and Post Processing quality = Low 4xAA/16xAF: Play Time: 94.17s, Average FPS:
21.24
Crysix.exe DX10 1680x1050 all settings High except Shadow quality = Medium and Post Processing quality = Low 4xAA/16xAF: Play Time: 124.37s, Average FPS:
16.08
Disappointing to say the least. Let's hope this isn't an issue in the WHQL drivers or the ones for the final retail game.