http://bugs.winehq.org/show_bug.cgi?id=29998
--- Comment #6 from Christian christian.frank@gmx.de 2012-02-26 09:23:01 CST --- Crysis 2 V 1.9, Settings: high
Wine Settings: - GLSL:enabled - Videomemorysize: 1024 - Windowed, 1680x1050
1.3.19: OK 1.3.20: Crysis 2 has huge graphical issues when loading checkpoint 1.3.21: Crysis 2 crashes or has huge graphical issues when loading checkpoint 1.3.23: Crysis 2 crashes or has huge graphical issues when loading checkpoint 1.3.25: Crysis 2 crashes when loading checkpoint 1.3.27: Crysis 2 crashes or has huge graphical issues when loading checkpoint 1.3.30: Crysis 2 has huge graphical issues when loading checkpoint 1.4.rc4: Crysis 2 has huge graphical issues when loading checkpoint (mostly black screen with hud is displayed)
All the time when the game crashes i get this:
Backtrace when crashing:
Backtrace: =>0 0x0bc0de5a in d3dx9_42 (+0xdde5a) (0x0c02db90) 1 0x0bc0e070 in d3dx9_42 (+0xde06f) (0x0c02dba8) 2 0x0b726337 in cryrenderd3d9 (+0xb6336) (0x452eca30) 3 0x00000000 (0x0bb389e8) 4 0x0bc12b37 in d3dx9_42 (+0xe2b36) (0x0bc0ab74)
For your info, to rule out any bugs in d3dx i used native d3dx9* dlls with overrides in my test..
So, the loading of Crysis 2 checkpoints broke in Wine 1.3.20 . Should i really do a bisect of such an old Wine version ?
Wouldn't it make more sense to provide some debug output of the issue in the current 1.4 rc's ?
And one important thing again:
All those bad issues only happen when you try to resume a checkpoint after closing the game. If you start the game, then start a campaign, it works great.Even exiting to the menu and then resuming a checkpoint works fine. But resuming a checkpoint after closing the game leads to all those issues.
Many thanks, Christian