[Bug 29998] New: Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

Bug #: 29998
           Summary: Crysis 2 (>1.0) huge graphical issues after loading a
                    savegame
           Product: Wine
           Version: 1.4-rc5
          Platform: x86-64
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: directx-d3d
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
    Classification: Unclassified

Created attachment 39060
  --> http://bugs.winehq.org/attachment.cgi?id=39060
Crysis 2 log

Hi,

if you try to use a saved game in Crysis 2 which is patched to a higher level
than 1.0, you will have huge graphical issues. Either you get a black scree
with only the hud displayed, or completely broken graphics, or a whiet screen
etc..

This does only happen if you use a savegame or if you want to replay a mission.

If you start the campaign from the beginning, the game will look fine.
This behaviour happens with tons of wine version i have testet, so doesnt seem
to be a regression right now.

CryEngine 3 is planned to be used in other upcoming games and is somehow a
engine which really pushes d3d9 to its limits.I think it would make a lot of
sense to get this issue fixed .

Many thanks,
Christian

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #1 from Christian  2012-02-25 01:55:10 CST ---
Sorry for forgetting this:

My hardware

Intel Core 2 Due E8200
4GM RAm
Geforce GTX 560 Ti-> Nvidie 295.20 (driver doesnt matter)

The logs i attached is with:

GLSL disabled
AlwaysOffscreen enabled

But changing those 2 settings doesnt solve the issue.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #2 from Vitaliy Margolen  2012-02-25 11:07:38 CST ---
You probably ignored this message:
The GLSL shader backend has been disabled. You get to keep all the pieces if it
breaks.

Enable it and retry, or this bug will be closed as invalid

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #3 from Christian  2012-02-25 15:00:14 CST ---
(In reply to comment #2)
> You probably ignored this message:
> The GLSL shader backend has been disabled. You get to keep all the pieces if it
> breaks.
>
> Enable it and retry, or this bug will be closed as invalid

Hi Vitaliy,

as i already mentioned in my second post, enabling glsl did not solve this
isse.
But i now tested crysis 2 newest patch level against wine 1.3.19 (this was a
wine version in which someone reported gold for crysis 2) and it works with
this wine version. I tested with the same settings in wint 1.4 rc 4 and it does
not work.

So, there is a regression which seems to break crysis 2 in wine.

Any things i can do to help solving this issue ?
Any debug logs needed ?

Cu,
christian

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

joaopa  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #4 from joaopa  2012-02-25 15:06:40 CST ---
http://wiki.winehq.org/RegressionTesting

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #5 from Christian  2012-02-26 03:09:25 CST ---
(In reply to comment #4)
> http://wiki.winehq.org/RegressionTesting

thanks. this will take some time. I will need to check first which wine version
broke it. Then i will use bisect to find the commit.

I will only take a look at the graphical issues when using a saved checkpoint,
cause in addition i noticed that in the older wine version the game tends to
lock from time to time.i also noticed graphical issues in 1.3.19 when using a
higher resolution and disabling vsync in game.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #6 from Christian  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

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #7 from Christian  2012-02-28 12:29:42 CST ---
can someone tell me if the bisect is still usefull for such an old version or
should i provide detailed d3d logs for that issue instead ?

many thanks,
christian

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

Jerome Leclanche  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #8 from Jerome Leclanche  2012-02-28 12:34:19 CST ---
(In reply to comment #7)
If it's a regression, a bisect is extremely useful.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #9 from Christian  2012-03-01 14:14:25 CST ---
e6ab3832b20707108f8611a32ae61085ee4f76d8 is the first bad commit
commit e6ab3832b20707108f8611a32ae61085ee4f76d8
Author: Henri Verbeet 
Date:   Tue May 10 21:18:44 2011 +0200

wined3d: Set SFLAG_DYNLOCK for lockable render targets.

:040000 040000 70131d5160415ccd5c9c16336291218dd95182b2
4b40acec2ec090c26fa464d73a9adb7e1be97992 M    dlls

this seems to be causing the issues with all the graphics.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

Jerome Leclanche  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
    Regression SHA1|                            |e6ab3832b20707108f8611a32ae
                   |                            |61085ee4f76d8

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

Stefan Dösinger  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #10 from Stefan Dösinger  2012-03-01 14:24:09 CST ---
Can you attach a +d3d,+d3d_surface log? Compress it with bzip2 or lrzip if it
is too big.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #11 from Christian  2012-03-01 14:26:16 CST ---
Created attachment 39148
  --> http://bugs.winehq.org/attachment.cgi?id=39148
picture showing the issue

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #12 from Christian  2012-03-01 15:01:17 CST ---
Created attachment 39149
  --> http://bugs.winehq.org/attachment.cgi?id=39149
part 1 of d3d debug log (used split)

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #13 from Christian  2012-03-01 15:05:51 CST ---
Created attachment 39150
  --> http://bugs.winehq.org/attachment.cgi?id=39150
part 2 of d3d debug log (used split)

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #14 from Christian  2012-03-01 15:09:20 CST ---
Created attachment 39151
  --> http://bugs.winehq.org/attachment.cgi?id=39151
part 3 of d3d debug log (used split), was lrzip

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #15 from Christian  2012-03-01 15:11:15 CST ---
Created attachment 39152
  --> http://bugs.winehq.org/attachment.cgi?id=39152
part 4 of d3d debug log (used split), was lrzip

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #16 from Christian  2012-03-01 15:13:33 CST ---
Created attachment 39153
  --> http://bugs.winehq.org/attachment.cgi?id=39153
part 4 of d3d debug log (used split), was lrz5 (last part)p

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #17 from Christian  2012-03-01 15:37:31 CST ---
Created attachment 39154
  --> http://bugs.winehq.org/attachment.cgi?id=39154
2 pictures showing issue in 1.4 rc4

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #18 from Christian  2012-03-01 16:22:55 CST ---
Doing a git revert of that commit fixed the issues in the current git !

git revert e6ab3832b20707108f8611a32ae610

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #19 from Christian  2012-03-03 02:18:15 CST ---
well, this is strange.

My issues are reporducable fixed now if i use a resolution of 1680x1050.

I still run into strange graphical issues when using 1920x1080. But those
graphical issues look different. Moving around the mouse ingame leads to
differnt grpahical issue (wrong colors etc..).

Could this be another bug ?

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #20 from Christian  2012-03-04 05:00:35 CST ---
can someone set this bug to confirmed ?

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #21 from Vitaliy Margolen  2012-03-04 09:30:52 CST ---
(In reply to comment #20)
No, you are the only person having issue.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #22 from Christian  2012-03-04 10:46:08 CST ---
Vitaly, i HIGHLY doubt that. Also the maintainer of the crysis 2 app db entry
has issues with loading games in newer wine versions.

Should i contact him so that he is aware that i opened a bug for this so he can
attach his experience ?

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #23 from Rico  2012-03-05 01:18:51 CST ---
Please add the bug to the appdb (to all apps you know that trigger the bug,
e.g. the different crysis 2 versions), this way all people will see it, if they
have a look on that appdb page and not only the maintainer will know about the
bug.

Is there a demo with the same problem?

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #24 from Christian  2012-03-06 13:10:38 CST ---
there is a demo for the game but iirc it was released when the game was
released so it likely is game version 1.0

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

Alex  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #25 from Alex  2012-03-08 12:29:53 CST ---
Well, I registered myself to say that I have the same issue ...  (because
apparently, to Vitaly, if you don't post here, you don't have issues)

the graphical issues was present in Crysis 1.x and the way was patching
dlls/wined3d/buffer.c forcing double buffering ... it worked back then ( I'll
call this http://bugs.winehq.org/show_bug.cgi?id=18799#c37 )

In Crysis 2 that was the only way to play, but again, if you exit the game and
resume ... well, it will just freeze after the loading screen, no matter what.

In any case this bug ticket has a lot of information.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

Jerome Leclanche  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1

--- Comment #26 from Jerome Leclanche  2012-03-08 12:40:11 CST ---
confirming

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #27 from Alex  2012-03-08 12:45:55 CST ---

In any case, I'll try some of the stuff called in here (like the revert), in
any case you found the same version that used to offend Crysis 1.x back in the
day.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #28 from Alex  2012-03-10 01:24:49 CST ---
Well, I'll add that I removed audio support, and resuming now works  ...

I'm using openSuSe (Tumbleweed), which uses by default the usual setup of
routing alsa > pulseaudio. with that, game won't resume (or will, under some
strange voodoo circumstances )

with alsa, graphics gets all messed up and audio stops working immediately
after a loaded game.

And without audio (either by disabling it or by disabling mmdevapi) game always
resume.

So, it appears that here it's not a graphical issue (didn't even try without
the double buffering patch)

Sorry for the noise, but I though this information could be useful to someone

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

Jerome Leclanche  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
                   |                            |t

--- Comment #29 from Jerome Leclanche  2012-03-10 05:29:03 CST ---
cc joerg

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #30 from Christian  2012-03-10 06:24:03 CST ---
Guys,

i now can confirm the disabling mmdevapi in the winecfg really has the effect
that you can load the game with plain wine and don't have any graphical issues.

This is super strange.
It still also works for me with mmdevapi enabled after reverting the git patch.

No idea what a patch for d3d has in common with mmdevapi.

@Alex: The double buffering patch is not needed for Crysis 2. And fyi and
noticed that this patch hurts perf in some of my other games.

Can someone give an advice how to further debug this issue ?

Cu,
Christian

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #31 from Alex  2012-03-10 21:57:08 CST ---
Christian, have you read this?
https://secure.mycrysis.com/forums/viewtopic.php?f=40&t=32062&start=...

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #32 from Alex  2012-03-10 21:58:11 CST ---
The sound issue seems to be a Windows problem too and a cracker fixed it before
Crytek (for 1.9) .. can you confirm it works?

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #33 from Stefan Dösinger  2012-03-11 04:18:26 CDT ---
It is possible that there's a memory corruption somewhere, either because of a
game bug, or because of a Wine bug. The d3d patch does change the memory
management of surfaces a bit, so it could be enough to tilt the behavior.

I think you tried to disable GL_ARB_pixel_buffer_objects in directx.c, and it
did not fix the game. This factoid makes more sense if this bug is a random
memory corruption instead of a real bug with PBOs.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #34 from Christian  2012-03-11 08:04:32 CDT ---
Hi Alex,

no,the cracked version of the exe does not change things for me.
The problem they are a talking about in the forum link started with patch1.9.
The problems with wine already started in patch 1.1.

Right now, this issue can get fixed by reverting a git commit.
Stefan, can you check if this could get reverted for newer wine versions ?

The frequent in game crashes give me much more headaches than this issue right
now cause i have no idea howto debug the other bug issues.

@Stefan: Any tips for that also ?

Bug: http://bugs.winehq.org/show_bug.cgi?id=30111

Cu,
Christian

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #35 from Stefan Dösinger  2012-03-11 17:30:31 CDT ---
We don't revert commits or apply patches that happen to fix something if we
don't understand exactly what is going on. This probably means that Henri,
Matteo or I have to debug this issue to better understand it.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

Henri Verbeet  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
    Regression SHA1|e6ab3832b20707108f8611a32ae |
                   |61085ee4f76d8               |

--- Comment #36 from Henri Verbeet  2012-04-04 07:33:41 CDT ---
I'm removing the regression SHA1 for now because it isn't all that clear this
is really a regression. In particular the fact that disabling mmdevapi seems to
help is suspicious and probably indicates some kind of memory corruption. In
the general case running the game under something like Valgrind would have been
useful, but for something as heavy as Crysis 2 that's probably not realistic.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

Jörg Höhle  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|[e-mail] |
                   |t                           |

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

Linards  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #37 from Linards  2012-05-13 04:14:39 CDT ---
Also note this link:
http://www.mycrysis.com/forums/viewtopic.php?f=40&t=32062&start=150

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #38 from [e-mail] 2012-07-11 08:14:41 CDT ---
For anyone who's having weird graphical problems, I also had red stuff all over
my screen and crashes until I followed a workaround I found here:

https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/969359

sudo mv /usr/lib/gnome-settings-daemon-3.0/keyboard.gnome-settings-plugin
/usr/lib/gnome-settings-daemon-3.0/keyboard.gnome-settings-plugin.ori

sudo pkill -9 gnome-settings-daemon

This works around an apparent bug to do with the keybord, that causes high
consumption of CPU, and blinking keybaord lights (numlock in my case)...

NOTE: that applying this workaround will disable certain features related to
the keyboard as outlined in the bug post.

Also removing my directx winetricks dll overrides seems to have helped. :0\

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

rocko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #39 from rocko  2012-08-04 23:56:52 CDT ---
I also have the graphical glitches issue (often I get just a black screen with
sometimes the gun drawn and sometimes the HUD, but other times some parts of
the screen get drawn). This is with wine-1.5.10-67-g866a207 and nvidia 304.32,
running Crysis2 in a 1600x900 window. It used to work fine at some point in the
past with earlier wine/nvidia versions.

As mentioned in earlier comments, adding mmdevapi to the list of library
overrides in winecfg and then disabling it fixes the issue for me.

Curiously, before I disabled mmdevapi, the glitches also stopped happening when
I ran with WINEDEBUG=+d3d. The screen refresh was a lot slower, of course. So
could it be a timing issue?

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #40 from rocko  2012-08-05 00:21:55 CDT ---
I can also fix the graphic glitches and have mmapidev enabled (since mmdevapi
is needed for audio to work, of course) if I do:

force_s3tc_enable=true

before running Crysis2.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

Adam Bolte  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #41 from Adam Bolte  2012-12-10 01:52:10 CST ---
I'll just add that I too can work around this by lowering my resolution.
Normally I run at 1920x1080, but lowering it to 1280x720 allows me to load save
games fine most of the time.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

http://bugs.winehq.org/show_bug.cgi?id=29998

K1773R  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

https://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #42 from Austin English  ---
This is your friendly reminder  that there has been no bug activity for over
700 days. Is this still an issue in current (1.7.36 or newer) wine?

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

https://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #43 from Adam Bolte  ---
I just looked into it. Crysis 2 no longer works under Wine without first
working around bug #35718 (and ideally bug #33723). Those patches no longer
apply cleanly, however I did manage to get something built that did not have
the problems those patches aim to address.

The result was that I didn't not see any screen corruption at all. However,
Crysis 2 ran *very* slow and I experienced a few crashes in the brief time I
tried to test it (at both high and low resolutions). I'm not sure if the
slowness and crashes were a result of the patches, a Wine regression, or
perhaps even this bug showing itself up in a different way. I did experience
crashes around the same areas where I used to be able to most easily reproduce
the graphical corruption issues, so I guess anything is possible.

Maybe we can only add #35718 to "Depends on" field for now.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

https://bugs.winehq.org/show_bug.cgi?id=29998

Stefan Dösinger  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|[e-mail]      |[e-mail]

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

https://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #44 from Christian  ---
(In reply to Austin English from comment #42)
> This is your friendly reminder  that there has been no bug activity for over
> 700 days. Is this still an issue in current (1.7.36 or newer) wine?

It works fine for me now with wine staging 2.20. The game is loading fine, i
think the bug can be closed.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

https://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #45 from Austin English  ---
(In reply to Christian from comment #44)
> (In reply to Austin English from comment #42)
> > This is your friendly reminder  that there has been no bug activity for over
> > 700 days. Is this still an issue in current (1.7.36 or newer) wine?
>
> It works fine for me now with wine staging 2.20. The game is loading fine, i
> think the bug can be closed.

While helpful, we don't know if it's fixed in wine it staging, and if staging,
what patch fixes it.(In reply to Christian from comment #0)
> Created attachment 39060 [details]
> Crysis 2 log
>
> Hi,
>
> if you try to use a saved game in Crysis 2 which is patched to a higher
> level than 1.0, you will have huge graphical issues. Either you get a black
> scree with only the hud displayed, or completely broken graphics, or a whiet
> screen etc..
>
> This does only happen if you use a savegame or if you want to replay a
> mission.
>
> If you start the campaign from the beginning, the game will look fine.
> This behaviour happens with tons of wine version i have testet, so doesnt
> seem to be a regression right now.
>
> CryEngine 3 is planned to be used in other upcoming games and is somehow a
> engine which really pushes d3d9 to its limits.I think it would make a lot of
> sense to get this issue fixed .
>
> Many thanks,
> Christian

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

https://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #46 from joaopa  ---
Does the bug still occur with vanilla wine-4.9?

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

https://bugs.winehq.org/show_bug.cgi?id=29998

--- Comment #47 from Adam Bolte  ---
I've just spent tonight trying to reproduce this bug with Wine 4.9 on Steam
(Crysis 2 Maximum Edition) using a fresh wineprefix. I couldn't - the game was
stable, and nothing stopped me from being able to play it.

I quit the game and reloaded my save a couple of times but AFAICT the game
could be considered Platinum as I didn't see any bugs at all (aside from being
unable to login since the servers were shut down years ago).

Ran using an AMD Fury X at 2560x1440 on Debian with Mesa 19.0.1 with everything
at the highest detail settings available (although high-resolution textures
couldn't be selected for some reason). I think this bug can be closed.

Unrelated note for anyone else interested in giving this game a go; it ran
perfectly under Proton 4.2-5 as well.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=29998

exposight  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #48 from exposight  ---
Also not happened to see this bug in wine 4.20, this never happened for
multiple savegames load for different levels.

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=29998

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #49 from Austin English  ---
Reported fixed (years ago).

[Bug 29998] Crysis 2 (>1.0) huge graphical issues after loading a savegame

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=29998

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #50 from Alexandre Julliard  ---
Closing bugs fixed in 7.20.