Compatibility Report

Agreed, proton now simply fails to launch the vast majority of VR games properly, I've gotten Moss and Half Life 2 VR to work, but Half Life 2 VR's controls are completely broken.

In order to eliminate as many variables as possible, I wrote a couple of test programs using the OpenVR and OpenXR APIs which simply initialize the API, wait 10 seconds, and then shut down:
openvr_test.cpp.txt
openxr_test.cpp.txt

1. If I build and run these natively on Linux, they work fine as expected.
2. If I build and run these natively on Windows, they work fine as expected.
3. If I take those Windows executables and try to run them via Proton on Linux:
   a. The OpenVR test works as expected.
   b. The OpenXR test demonstrates the same behavior as described in the initial report (stack overflow loading openxr_loader.so, followed by repeated "VR state wait timeout"). The test never prints any of the markers later than "preinit".

Edit: adding logs
OpenVR log (400M): steam-11463073133859176448.log.gz
OpenXR log (600M): steam-10877733739262115840.log.gz

I'm having the same issue, where OpenXR-based VR works in Proton 7.0-6 but not in Proton 8.0-1 or later.

I've only tested with VRChat (issue started when they switched to Unity 2022, I believe this is as unity2022 started doing some OpenXR stuff rather than OpenVR only) and No Man's Sky, but they both have the same characteristic printing to the Proton log: VR state wait timeout (retrying).

I've attempted to bisect Proton between those tags but haven't been able to do so due to build issues. The diff (incl submodules) is 3176468 lines so it's impractical for me to dig further.

System Information

• GPU: Nvidia RTX 3080 Ti
• Video driver version: nvidia-open 545.29.06
• Kernel version: 6.6.8.zen1
• Link to full system information report as Gist: https://gist.github.com/Seercat3160/0c3c76e5b865b40afc00d94bb01e8a00
  • In there you'll see reference to the fact that I'm launching Steam via prime-run: this is as my standard setup is Hyprland running on my iGPU and games run on my dGPU. However, I assure you that the issue in question still appears when I use the nvidia card as the primary GPU and run everything without PRIME.

LogOutput.log
I think I'm having the same issue, in particular when trying to run Lethal Company with the VR mod. Attached is my most recent logs from an attempt just moments ago. Is there any version of Unity's OpenXR plugin that works with the latest SteamVR / beta, and with Proton 8? I might fork the VR mod myself if changing the version of OpenXR plugin used by the mod can get it to work.

Tried the test programs again with new versions of everything.
Client: Steam Beta Client 1706155871
SteamVR: beta Version 2.3.4 (1706131326)
Graphics: nvidia 545.29.06
Kernel: 6.6.9-arch1-1

Results are the same as all other Proton 8 experiments with the following Proton installations.

Proton 8.0-5c

Proton: 1705700124 proton-8.0-5c
SteamGameId: 10877733739262115840
Command: ['/mnt/win/Users/Peter/Downloads/vrtest/oxr_test/main.exe']
Options: {'forcelgadd'}
depot: 0.20231211.70175
pressure-vessel: 0.20231208.0 scout
scripts: 0.20231208.0
sniper: 0.20231211.70175 sniper 0.20231211.70175
Kernel: Linux 6.6.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 02 Jan 2024 02:28:28 +0000 x86_64
Language: LC_ALL None, LC_MESSAGES None, LC_CTYPE None
Effective WINEDEBUG: +timestamp,+pid,+tid,+seh,+unwind,+threadname,+debugstr,+loaddll,+mscoree

Proton Experimental 8.0-20240111c

Proton: 1705004294 experimental-8.0-20240111c
SteamGameId: 10877733739262115840
Command: ['/mnt/win/Users/Peter/Downloads/vrtest/oxr_test/main.exe']
Options: {'forcelgadd'}
depot: 0.20231211.70175
pressure-vessel: 0.20231208.0 scout
scripts: 0.20231208.0
sniper: 0.20231211.70175 sniper 0.20231211.70175
Kernel: Linux 6.6.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 02 Jan 2024 02:28:28 +0000 x86_64
Language: LC_ALL None, LC_MESSAGES None, LC_CTYPE None
User settings WINEDEBUG: +timestamp,+pid,+tid,+seh,+unwind,+threadname,+debugstr,+loaddll,+mscoree,+vrclient
Effective WINEDEBUG: +timestamp,+pid,+tid,+seh,+unwind,+threadname,+debugstr,+loaddll,+mscoree,+vrclient

Replying to https://github.com/ValveSoftware/Proton/issues/7228#issuecomment-1911214557

I suspect this might be a different issue. In the log you provided, the game seems to at least get past the OpenXR initialization; on lines 26+, I see Initialized OpenXR Runtime, and then it successfully requests the OpenXR version: OpenXR runtime being used: SteamVR/OpenXR (2.3.4). Just based on the errors, it seems like something related to input rather than the initial setup.

Looking at the mod's code, I think this is the line equivalent to my test program:
https://github.com/DaXcess/LCVR/blob/f16127bb49aa947556c362d19379250c08ca122a/LCVR/Plugin.cs#L313

@terminal-case, could you set the game's launch options to PROTON_LOG=1 %command% and check the resulting steam-<numbers>.log in your home dir? If you see "VR state wait timeout" after a while, then it's probably the same, but if not, you might have better luck opening a new issue.

I suspect this may be some bug in Nvidia driver so I opened an issue on their forums. https://forums.developer.nvidia.com/t/entire-graphics-stack-crashes-when-opening-a-steamvr-application-through-proton-compatiblity-layer-that-targets-openxr-rtx-3060-550-76-cuda-12-4/291155

I was recently making a patch for Proton 8.26 and noticed that a stack overflow happened in libopenxr_loader.so every time I tried to open an OpenXR application in Proton. The exact error message for me was free(): invalid pointer followed by a log spam related to stack unwinding and eventually a stack overflow. My workaround was to compile libopenxr_loaded.so without optimizations. This may or may not be related, but sounds very similar to the stack overflow problem described in this issue.