-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Playing games that require Proton compatibility layer, causes SteamVR to crash. #659
Comments
Still crashes on SteamVR Beta 2.2.3 EDIT: In some issues, installing Steam Native helped, but in this case they behave the same, Steam Runtime and Steam Native crash the second I open any VR game that needs proton. |
By some miracle, all of a sudden HL Alyx stopped working for me, with a "Unable to init VR runtime (102) VR client shared lib not found", I tried reinstalling SteamVR, Proton, Steam nothing worked. Then I noticed that it openes in Wine window, so I renamed my .wine to .wineold, and now was hit with Error: Installation path could not be located (110) also in Wine window. I tried a lot of things again, uninstalling proton and so on, nothing bugged, but then I tried to change Compatybility tool on HL Alyx to something else (I think from Proton 8.0.4 to Experimental), and there was a 500MB(?) update for HL Alyx, which fixed it?? Then I could chose whatever compatybility layer as I think some script setup everything as it should in Wine.
EDIT: The switching between my issue and 638 was not cause by the .wine folder but by Compatibility tool version. In short I have crashing on Proton Experimental (but the game correctly is able to grab the VR handle), and infinite loading on 8.0.4, but no crash. |
Hello, good news I finally uncovered what was happening, the newer updates of the games use OpenXR (Beat Saber, Ancient Dungeon), rolling to a version that was using OpenVR fixed all the issues ("legacy1.29.1_unity_ver2019.4.28f1 - pre unity upgrade build" for Beat Saber, and "oldversion - ea0.1.2.2 (the pre openxr update) version" for Ancient Dungeon VR). As I have found this information online, Valve is probably also aware of this, but as I do currently have Nvidia GPU (suposedly doesn't happen on the AMD GPUs), and experience this problem, maybe you would want some additional logs? Anyway I'm gonna update you on every stable release, and on every Nvidia driver upgrade, maybe it will change something. |
The behaviour is still the exact same, even though Nvidia driver and Linux kernel versions change, armed with knowledge that is supposedly doesn't happen on AMD cards I opened the issue on Nvidia 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 |
Describe the bug
When launching SteamVR games that were programmed for Windows and require Proton compatibility layer, cause SteamVR to crash, sometimes bringing the GPU driver with it, facilitating the need to restart.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Games started with the help of Proton compatibility layer would just work.
System Information (please complete the following information):
Screenshots
Additional context
The games start for the briefest of moments after which they crash SteamVR.
At first nothing but the VRWebHelper worked, then native Linux Steam games started working such as Half Life Alyx or SteamVR Home. Then some others started working for some reason such as Half Life 2 VR mod. Right now I see that the final frontier is getting VR games that go through Proton to work correctly, enabling Vulkan async reprojection, and then setting up compositor to have priority over games in the GPU queues.
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.
[See instructions]
The text was updated successfully, but these errors were encountered: