protonscr

Death's Gambit: Afterlife

protonopen appid 356650Game compatibility - Unofficial
ValveSoftware/Proton#1148 · opened 2018-09-01 by JakeEhrlich · updated 2022-04-18 · 12 comments · github · game page · search this game
2 matching comments, n / p to jump
JJakeEhrlich 2018-09-01 github

Death's Gambit starts, runs, and seems stable but the performance I'm getting is extremely bad. My hardware is capable of playing much more intensive games and has successfully done so on proton games. The settings I run it on does not seem to affect performance. I'm unsure of how best to profile the game to see where the time is being spent.

System Information: https://gist.github.com/JakeEhrlich/3393913d9d16a569819a18fbd3c968f3

Kkisak-valve maintainer 2018-09-01 github

Hello @JakeEhrlich, please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

JJakeEhrlich 2018-09-01 github

Done

Kkisak-valve maintainer 2018-09-01 github

Can you switch to Proton 3.7-5 beta and please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

JJakeEhrlich 2018-09-01 github

That log is huge, like 4k lines huge. Do you want something more specific from it?

JJakeEhrlich 2018-09-01 github

(Also, I switched to Proton 3.7-5 beta and not see noticeable improvement)

JJakeEhrlich 2018-09-02 github

I see, this is for file upload.

steam-356650.log

Aat46 2020-04-03 github

The game minimize and maximize itself constantly every 1-2 seconds which makes it unplayable. It seems to run fine if I set my monitor refresh rate to 60 hz (xrandr -r 60) instead of the native 144 hz.
sysinfo
steam-356650.log (with 144 hz)

Ssonofevil 2022-04-13 github

Compatibility Report

  • Name of the game with compatibility issues: Death's Gambit: Afterlife
  • Steam AppID of the game: 356650

System Information

I confirm:

  • [ ] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

Symptoms

After transitioning to a new area, the game will sometimes load background sprites/textures incorrectly, leading to a glitched mess. This makes the game unplayable. The glitched graphics persist in that area until the game is restarted.

Example Screenshot
Proton Log (30mb when uncompressed due to extreme verbosity)

I believe the relevant section of the log is this (the same error appears multiple times in the log, this is the first occurance):
https://gist.github.com/sonofevil/6887a104a4032e7379d5e652cac5ba0a

Reproduction

  1. Start the game and start playing for some time.
  2. Enter a new area (screen transition).
Kkisak-valve maintainer 2022-04-13 github

Hello @sonofevil, it should be noted that you're using an Intel Haswell chipset. The Vulkan drivers for this generation do not provide a spec-compliant implementation and graphical artifacts and/or crashes are expected. The incomplete video drivers makes your system unsupported by Proton.

Ssonofevil 2022-04-13 github

I know, that's why I'm using a 5.4 kernel (later Kernel versions introduced new problems for Haswell chips). However, the game used to run correctly, and only started displaying the issue recently (presumably after a system upgrade). If anyone is knowledgeable about GL_OUT_OF_MEMORY and GL_INVALID_VALUE issues in wined3d, I would really appreciate some suggestions that might help me troubleshoot the issue further.

I tried asking in the Death's Gambit Discord, but they are ignoring my support request. Other than that the only place I can think of asking would be the Steam community forum for the game, but I usually do not get a helpful response in these forums.

Kkisak-valve maintainer 2022-04-13 github

You're using PROTON_USE_WINED3D=1 to tell Proton to use wine's DirectX to OpenGL render path. This runtime option is not considered supported. If you suspect this is a video driver regression, then you can report the issue to the mesa devs, otherwise, your best option is to reproduce the issue with vanilla wine and report the issue to wine's upstream issue tracker at winehq.

Ssonofevil 2022-04-13 github

Right, that's cos if I use PROTON_USE_WINED3D=0, this happens:
image

Update:
If I switch to PROTON_USE_D9VK=1, the game no longer crashes at start, but rather crashes once you enter a new area. The error says DxvkMemoryAllocator: Memory allocation failed. I've now tried a whole bunch of DXVK settings, but they didn't change anything.

Proton versions

Launch options