Games stop working with Proton 6.3-4

[frudolph77]

Compatibility Report

• Dorfromantik
• Steam AppID of the game: 1455840

and also

• Townscaper
• Steam AppID of the game: 1291340

System Information

• GPU: Intel(R) UHD Graphics 620 (WHL GT2)
• Driver/LLVM version: 3.0 Mesa 20.0.8
• Kernel version: 5.4.0-73-generic
• Link to full system information report as https://gist.github.com/frudolph77/2fdfff10708560b2b4003438d804b22c
• Proton version: 6.3-4

I confirm:

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

Logs of Dorfromantik (1455840):

Log of game with working Proton 6.3-2
steam-1455840_Proton_6.3-2.log.gz

Log of game with broken Proton 6.3-4
steam-1455840_Proton_6.3-4.log.gz

Symptoms

Game simply stops running with Proton 6.3-4, has been running fine with 6.3-3/6.3-2 and 5.13-6

Reproduction

Just switch between Proton 6.3-4 and previous 6.3 Versions
I've had an older steam installation available, on an other box, and took the Proton Version from there to verify that the game runs fine with older versions.
I think there is a problem with the wine update on May, 13th

[kisak-valve]

Hello @frudolph77, your system information is telling us you do not have any Vulkan drivers installed. Please double check that you have mesa-vulkan-drivers installed with apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386 and install those packages if they are missing.

[frudolph77]

Installed mesa-vulkan-drivers as suggested but does not make any difference.
I see the loading screen, display went black, and game crashes instantly.

Versions prior 6.3-4 are working fine, without these drivers.

[mofftech]

I basically have the same problem. I can't launch Steam/Among us with Proton Experimental or 6.3-4. I seem to have mesa-vulkan-drivers / mesa-vulkan-drivers:i386 installed. See attached, which includes the Crash log output.

Another game "The Last Day of June" does run fine. I am not sure
crash_log.txt
what to do, but at least I can globally roll back the proton driver to run Among Us. I don't think I can control the Proton driver per-app.

[frudolph77]

Is there any chance to rollback to Proton 6.3-3 within steam?

[mofftech]

I don't think so (or I don't know how).

"Steam -> Settings -> Steam Play" offers me Experimental, 6.3-4, 5.13-6, 5.0-10 and a variety of earlier versions.

The log comes from Experimental.

5.13-6 works for Among US but doesn't work for The Last Day of June, so I have to revert to 5.13-6 when I want Among Us.

[arrowgent]

there is no way to rollback versions
once steam updates the DB, the previous files are gone from their server
https://steamdb.info/app/1580130/depots/

it would be possible to recompile from source and put those files over the existing files
but im definately not going to spend time compiling proton

[alasky17]

@mofftech Could you attach your system specs? Also, there is a way to set a proton version for an individual game - right click on the game in Steam and look for the setting under properties -> compatibility :)

[frostworx]

Minor version bumps overwrite the previous versions. I occasionally save proton versions into an extra folder to have it still available in stl when I want to test something and indeed I also stored Proton 6.3.3, but don't have any of the mentioned games to test.

[aeikum]

@mofftech @frudolph77 I noticed both of you are using wined3d instead of DXVK. You may be able to work around this by removing the option to use wined3d. In any case, I can reproduce the failure, and we'll look into fixing it. Thanks for reporting.

[mofftech]

@alasky17 - I see that I can control proton versions as you suggest, thank you.

@aeikum - With the workaround of the Proton version I don't need to try DXVK (I am not sure how yet, need to research it). My question is whether I should normally prefer this DXVK over wined3d?

[mofftech]

Forgot to add for @alasky17 - here is what I'm running in summary. Full details are attached.

AMD Ryzen 9 3950X 16-Core Processor
Motherboard MEG X570 UNIFY
RTX 3070 gpu
64GB Corsair running at 3600
devices.txt

[aeikum]

DXVK is used by default. Do you have PROTON_USE_WINED3D set somewhere, like in the game's launch options or your user_settings.py file?

[frudolph77]

@mofftech @frudolph77 I noticed both of you are using wined3d instead of DXVK. You may be able to work around this by removing the option to use wined3d. In any case, I can reproduce the failure, and we'll look into fixing it. Thanks for reporting.

Unfortunately this is not possible, otherwise Dorfromantik won't run, as you can see in ProtonDB.

Townscaper seems to run fine with 6.3-4 when removing PROTON_USE_WINED3D=1, at least it's starting.
I've only tried Dorfromantik after installing mesa-vulkan-drivers

[mofftech]

I'm leaving a note for people trying to find workarounds. I don't suppose it informs the bug itself much.

I installed Steam and bought the game on another laptop (Debian/Buster). It was an older laptop, but not antique, with Intel graphic. I got DirectX errors (not related to this bug) when the game launched:

Failed to initialize graphics.
Make sure you have DirectX 11 installed, have up to date
drivers for your graphics card and have not disabled
3D acceleration in display settings.
InitializeEngineGraphics failed

Then I changed the game specific settings (Among Us -> Properties -> General -> Launch Options):

PROTON_USE_WINED3D=1 %command%

Then I hit the specific bug in this report (issues/4824), so I implemented the workaround of changing the Proton version for the game.

Among Us -> Properties -> Compatibility -> check "Force...", select Proton 5.13-6).

Interestingly, today I installed Steam on another Ubuntu PC (yes, a third system) that had an NVIDIA card installed. The only non-default setting is the global Steam -> Settings -> Steam Play -> Check "Enable Stream Play for all other titles" with Proton Experimental. The game booted without complaint.

I presume that this worked due to DXVK being default. On the laptop system with the Intel graphics, I was forced to set PROTON_USE_WINED3D=1 to escape the DirectX issue, requiring as a result the Proton version fallback.

[mofftech]

@aeikum - You are correct in your earlier comment. On my first system (the one that caused me to find this issue) I have PROTON_USE_WINED3D=1 in the Launch Options and for the life of me I cannot remember why I set that.

PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command% PROTON_LOG=1 %command%

Do I only need to put %command% once at the end of the entire string?

On my original system (that caused me to find this bug) I removed that entire string from the Launch Options and set the Proton Version back to the system default (Experimental). The game booted fine.

I think that I must have originally (on first install) followed some random howto from the Internet that told me to set the PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command% bit. The PROTON_LOG=1 I set while I was trying to troubleshoot.

So it looks like users won't see this unless they need to override to wine3d. Likely they will need to do this if they encounter the DirectX issue I saw on the laptop/intel system. Or to mitigate whatever issue @frudolph77 has for Dorfromantik.

Thanks again for everyone's help. I hope that I was able to help back for others struggling to understand how to get going.