Thanks for reporting. It seems to be working for me. I do get a black screen, but clicking the mouse a few times gets me into the game. Probably an intro video that fails to play.

Yeah, that's normal. That is what I get with 5.09.
With 5.13-1, I don't even get that :(

@TheSHEEEP I'm also not seeing any difference between 5.0-9 and 5.13-1.

Could you try temporarily moving (or deleting) the prefix? Standard location is ~/.steam/steam/steamapps/compatdata/1102190. Just in case the game stores data in there, you can just rename that folder to 1102190.bak or something and try launching the game again on 5.13-1.

If that fails, please upload a log of it failing to work on 5.13-1.

Did that, but it unfortunately didn't change anything.
I attached the log.
steam-1102190.log

@TheSHEEEP There is a potential dxvk regression that we are investigating, and your log looks similar to a failure log related to that regression. Could you try temporarily disabling dxvk, either by adding PROTON_USE_WINED3D=1 %command% to the launch options or by "turning on" the option in user_settings.py?

Edited since I realized first request was unnecessary for now :)

Using PROTON_USE_WINED3D=1 %command% with 5.13-1 fixes the problem.
So with that, 5.13-1 runs the game just like 5.09 did.

It seems like I spoke too soon.
While the game does indeed launch, and I can get to the main screen, the actual game doesn't work entirely.

This is the "character selection" - it should not be black (and isn't in 5.09).
However, this is also black in 5.09 when using PROTON_USE_WINED3D=1 %command%.

So it seems like you might be right about the dxvk regression, but in addition to that, the game doesn't fully work with WINED3D, either. In neither proton version.

@TheSHEEEP Thank you for testing! I agree - sounds like wined3d just has other bugs not present with dxvk. Could you test an older dxvk version to narrow down where the regression is? (and to confirm that its dxvk).

You can easily test the dxvk version from Proton 5.0 by copying the files from that dist/../dxvk folder to the Proton 5.13 folder. The standard location is ~/.steam/steam/steamapps/common/Proton 5.0/dist/lib/wine/dxvk/* and .../Proton 5.0/dist/lib64/wine/dxvk/* You can just replace all of the files in the 5.13 dxvk folder with the ones from 5.0. After testing, simply delete the entire Proton 5.13/dist folder - it will automatically regenerate the original.

I did that, but it unfortunately did not resolve the issue.
It's the same as before, opening up an "empty" (just showing what was on the screen before) window without any input possibility.

I attached the log of that "changed" 5.13.

So whatever the problem, it is likely not (or not only) in those dxvk files.
steam-1102190.log

@TheSHEEEP Thanks for all the testing! I'll keep looking :)

I was also getting a crash when trying to launch Monster train, though my logs look a little different than the previous ones in this issue.

PROTON_USE_WINED3D=1 %command% to the launch options or by "turning on" the option in user_settings.py?

This worked for me.

Attaching my log files in case it's helpful. I'm using "Proton Experimental", on Ubuntu 22.04.2.

Player.log
error.log