The game's launcher appears briefly (though it looks very barren) and then a fullscreen window appears. It's, however, even more barren than the launcher -- in fact, it's completely black! That way it seems to stay for an indefinite time, I've never seen it make any progress. Looking at the process in htop seems to tell a similar story as it does not appear to be doing much.
warn:module:load_dll Failed to load module L"C:\\Program Files (x86)\\Steam\\Steam2.dll"; status=c0000135 looks like a line of interest from the log (also mentioned at https://github.com/ValveSoftware/Proton/issues/346#issuecomment-415889306).
I got an interesting log from this one just now with Proton 4.2-3.
steam-263980.log
https://gist.github.com/lucifertdark/584c14275612e8e3c4a8070d428d8a02
Same issue for me with Proton 4.2-3, launcher opens but then the game only ends in a black fullscreen.
steam-263980.log
https://gist.github.com/NoXPhasma/a42e8cf9aea1453f39471f501c3ae6ad
Now playable with Proton 5.0-1, I'm getting artifacting along the sides of the screen and the pause menu keeps on getting activated when my xinput Logitech F310 controller is connected. RX 580, Mesa 19.3.3 ACO, Kernel 5.5.2.
Edit: run with PROTON_USE_WINED3D and the artifacting and gamepad issues are gone, but I'm experiencing some occasional stuttering on my end. My laptop with a A10 5750, HD 8650G same Kernel and Mesa version felt fine though.
@wantija Do you still get artefacts with Proton 5.0-6 RC3 (using DXVK)? I don't see anything odd any more. Also, I don't have any gamepads, do those work now with DXVK?
I can confirm that the game now starts with Proton 5.0-6-rc3 and it works fine so far. Except the gamepad, the game keeps opening the pause menu all the time, which makes it completely unplayable with a gamepad.
steam-263980.log
https://gist.github.com/NoXPhasma/e12b09b13ec9335677183625a014fed5
Can't check at the moment but my controller was a Logitech F310 in Xinput mode and had Xbox and generic controller support enabled in Steam. Later I can check with PS4, Xbone and Switch Pro controllers if that makes a difference.
I'm using the XBOX One S Controller and that behaviour happened with and without Steam Controller API enabled.