ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.41k stars 1.02k forks source link

En Garde! (1654660) #7025

Open DomiStyle opened 11 months ago

DomiStyle commented 11 months ago

Compatibility Report

System Information

I confirm:

steam-1654660_crash.log

Symptoms

The game (and Steam) crash at the start of chapter 3 when using the default DirectX 11 backend. DirectX 12 can be used as a workaround.

Reproduction

  1. Play the the game until you reach chapter 3
  2. Wait a few seconds at the beginning of chapter 3 (after the cutscene plays)
  3. Game crashes
Blisto91 commented 10 months ago

Hi there and thank you for the report. I have not been able to reproduce this so far either with my 7900xtx or my rdna2 iGPU. Do you know if it is tied to any special settings or such?

I assume this area shown below is the one that will crash in for you?

Screenshot ![image](https://github.com/ValveSoftware/Proton/assets/47954800/dea0de4e-3ceb-47eb-8adb-19b0c16183c6)
DomiStyle commented 10 months ago

Yes, the area is correct. Settings are all Ultra except anti-aliasing on FXAA and Motion blur is off.

After some more testing I figured out that the game has a memory leak with DX11. Not sure what I did to trigger this but it now happens on DX11 every time I start the game, even on the main menu. Played for a full hour before that with no issues. The timing just aligned perfectly with loading into the third chapter.

Took a video of it here:

https://github.com/ValveSoftware/Proton/assets/975131/66358e26-5e39-4549-959c-29aefb490e10

The game in DX11 fills up the entire 32GB of RAM in just a few seconds, on DX12 it runs without issues.

Blisto91 commented 10 months ago

@DomiStyle Hi there. I'm Back again. I have a suspicion it's probably this driver regression that was introduced with 23.1.6 https://gitlab.freedesktop.org/mesa/mesa/-/issues/9599 which can cause huge memory leaks in some games.

DomiStyle commented 10 months ago

Yes, that sounds just like it.

I was able to resolve it by switching from Fedora Steam to the Flatpak version, which uses a different Mesa version. The issue mentioned above doesn't happen there.

Thanks for looking into it, I finished En Garde with no other issue.