this post was submitted on 27 Sep 2025
43 points (97.8% liked)
Linux Gaming
22789 readers
392 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
Resources
WWW:
- Linux Gaming wiki
- Gaming on Linux
- ProtonDB
- Lutris
- PCGamingWiki
- LibreGameWiki
- Boiling Steam
- Phoronix
- Linux VR Adventures
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Lutris (and so Umu launcher) runs the game just fine if I use GE-Proton. However there is no Steam connection there. If I select to run it via Steam runtime inside Lutris, I still get the same error. (I think that option just runs the game via Steam and nothing more?).
If there are auto-enabled flags like
PROTON_USE_DXVK=1, I might try to disable them. Though there are many of these.Oh my bad, I misread the first line. In that case, I would guess that Proton on Steam might be using a different version of the DirectX translation layer. I'm not sure which that is, since im not sure which directx version the game uses.
Very interesting that at least one person reported the same error happening on Windows.
Edit: My guess is that wine is using WINED3D, the directx 9 to opengl translation layer, while proton is using DXVK. Since the game reportedly has this error on windows, the issue might actually be that DXVK is doing the "correct" thing and crashing the same way it would on windows.
Did you verify that PROTON_USE_WINED3D=1 crashes with the exact same error and not a new one? Since you said the game works with vanilla wine, which defaults to wined3d, I would expect this to fix it.
No problem! Yeah, I saw that too. Though it's from 2013 and before even Windows 10 but since it happened on Windows at one point says it might not be all related to translation layers.
Game uses DirectX 9 since it has a d3d dll in the game files. But I have no idea how can I check what Proton uses.
whoops, edited my other comment since I hadn't noticed your reply yet.
Can you share the launch options you're using to set PROTON_USE_WINED3D=1, as well as verify the the crash gives the same error?
I found a few examples of the variable not working correctly for people. Could you share your proton version and the logs?
No problem! :)
Actually
PROTON_USE_WINED3D=1was one of the first things I have tried. Sadly it still gives the same error.Currently I'm using GE-Proton10-15. These are the logs: