The game works with `proton-5.13-2-rc1` https://github.com/ValveSoftware/Proton/issues/4360 https://github.com/ValveSoftware/Proton/releases/tag/proton-5.13-2-rc1
my (pending) protondb update: "-onethread" commandline option required to get the game even working. previously (under nvidia rtx 2080) the game was unplayable with just one thread enabled. I switched to amdgpu (radeon v...
for the records. point 2 above "when SteamVR is not running when launching the game it fails to start its own SteamVR" very likely is this bug: https://github.com/ValveSoftware/SteamVR-for-Linux/issues/209
proton-5.0.5 which fixed https://github.com/ValveSoftware/Proton/issues/3652 unfortunately didn't fix this bug, which seems to have a broken openvr initialization as well.
still not working. pretty sure it is either wine or vrclient_x64 related. with a custom proton build I found this difference from logs: with a normal game launch with vr enabled: `2322.700:0048:0049:trace:vrclient:winIVR...
it looks like the game forcefully tries to launch SteamVR, no matter if it is already open or not. 1) when it is already running correctly when launching the game it "exists with the UE Error requester" because it wasn't...