[BUG] Constant SteamVR Fail -203

[LiamDawe]

Describe the bug
I am facing an issue where SteamVR will just fail on me constantly, don't get even 5 minutes out of it before it just freezes up and dies on me.

To Reproduce
Steps to reproduce the behavior:
Use NVIDIA with Arch, try and play SteamVR and watch it fail?

Expected behavior
For it to work like it usually does?

System Information (please complete the following information):

• Distribution: Arch
• SteamVR version: Tested on beta 1.19.1 and also stable 1.18
• Steam client version: 1626127145 (July 12)
• Opted into Steam client beta?: Yes
• Graphics driver version: 470.42.01
• Gist for SteamVR System Information: https://gist.github.com/LiamDawe/b59c8756962f1e394aa74bdc27473abd see also the developer output https://gist.github.com/LiamDawe/3ee28c6dc8523f1a1d4044c126fd01b7

Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.

[LiamDawe]

Went back to NVIDIA 465.31 and no issues at all. So it's a problem somewhere caused by the 470 driver.

[kisak-valve]

Hello @LiamDawe, it might be interesting to test if nvidia 470.xx + #227 (comment) works around the issue you're seeing.

[dec05eba]

I have the same issue. I tested what @kisak-valve suggested and it works.

[edwin-v]

Had two crashes playing Groove Gunner today (-203).

First when I tried to go into the Steam system menu/library from the game. After killing SteamVR I can't start it again without a power cycle on the headset because it will only display garbage.

Second crash when I quit the game after playing it again.

My uninformed suspicion would point to the compositor crashing under certain circumstances in combination with async reprojection.

[Corben78]

From my recent experiences, I can confirm that enabled async reprojection can cause SteamVR failures to happen a lot more likely.

When playing GTFO in VR with async reprojection (on nVidia), I experience about 2-3 crashes in a 3h play session. The game with the VR mod is quite demanding, so async reprojection does help with performance without downscaling.
I tried now 2 ~3h sessions in GTFO VR without async reprojection and didn't experience a single crash (have to downscale for a good experience then though).

My suspicion is, that a SteamVR failure with async reprojection occurs more likely, when the game is more demanding. I didn't experience crashes with Beat Saber, Synth Riders or Pistol Whip even when async reprojection was enabeld, but those games are way less demanding and work perfectly without async reprojection too.

[jannis3005]

I'd have to disagree with that, I can't play more that a few minutes of Beatsaber with async reprojection without experiencing a crash, sometimes it does it even straight away during the first song. Turning it off, all is fine. I'm running it at 150% res on the index though, so it might be a touch more demanding than on default settings. Also, Mods might add to that. That said, beatsaber works flawlessly at 150% without async reprojection too.

[silelmot]

i cannot even start anything. before even home is started my pc freezes for a very short time and after that it points out error 203. hmd is black the whole time. it works flawlessly on windows and did before the nvidia driver update

[mpnordland]

I'm also experiencing increased SteamVR crashes with async reprojection enabled on Linux. I have a 100% reproducible test case.

I'm running a GTX 1070 with NVIDIA 470 driver with SteamVR Beta 1.19.6. With async reprojection I experience the already reported jitter and wobbliless of the overlay and chaperone. In addition, when I play VRChat, and visit the Vket 6 Carryol WindChorus world and walk up to the Nullmoto Universe booth, SteamVR (but not VRChat) will crash. Without async reprojection the framerate drops but Steam VR keeps running.

OS is Arch Linux.

[silelmot]

I just found out that on my 3-monitor-setup,when i disable all but one, steamvr just works.
With all 3 on i get an instant 203

[okawo80085]

With custom SteamVR drivers on Linux same thing happens, last time i tested it was an Ubuntu machine, no external monitors, and the behavior is just "great" :) you start SteamVR and it works fine and dandy for maybe 5-10 minutes, it then proceeds to die for no reason with -203, no errors from the driver, only an "unusual" sleep state before crash, if i remember correctly

[HadetTheUndying]

I just found out that on my 3-monitor-setup,when i disable all but one, steamvr just works.
With all 3 on i get an instant 203

This is an unrelated issue. This happens on AMD as well. What's happening here is specific to Nvidia 470

[quantumac]

I can confirm this irritating, seemingly random -203 error is still an issue with the following setup in SteamVR:

Ubuntu 20.04
NVIDIA driver 470.57.02
Geforce 1080
Valve Index

While I could go back to a previous driver version which doesn't support asynchronous reprojection, I would end up with the double-image stutters again... but that's why I upgraded to the 470 driver.

[quantumac]

If SteamVR developers need a highly (and quickly) reproducible case, try this:

1. Make sure your system is running the NVIDIA 470 driver which supports asynchronous reprojection.
2. Run "Waltz of the Wizard: Natural Magic" under Proton.
3. Dismiss the complaint about a json file if it appears.
4. Once at the starting point, go to the door called "Courtyard" and touch the circle on the door until you hear the door creaking open sound. If the "Courtyard" door does not appear the first time, re-run the game.
5. Once in the courtyard, move to the center of the stone magic circle and stand there. Swirling magic will appear to transport you to...
6. Oopsie! Error -203 rears its head. Headset goes blank. Audio from the game continues, but you're no longer in VR.

Rarely, this action actually works as intended, VR stays working and the -203 error does not appear, but for the vast majority of the time, it bugs out like clockwork. Very reproducible.

The -203 error seems to occur during transitions, but not always. I've seen the error also happen in titles like "X-Plane 11" (native), "Myst" (proton), "Half-Life: Alyx" (native), "Go for Launch: Mercury" (proton), "Google Earth VR" (proton).

[Orangestar12]

Pops up out of nowhere constantly during Elite Dangerous and Phasmophobia in Proton on 470 drivers as well, where both of these titles previously worked great. This is still occurring even after disabling asynchronous reprojection in the settings.

These seem to be the only relevant messages from the web console:

Fri Sep 10 2021 01:22:26.004081 - Failed Watchdog timeout in thread Render in WaitForPresent after 6.004832 seconds. Aborting.
Fri Sep 10 2021 01:22:26.061325 - IPC: recovering abandoned mutex 0x7f9af7e163a4
Fri Sep 10 2021 01:22:26.603525 - Excessive binding loads from steam (18668): crc=3209310505 lc=2 Reload=F res=2
Fri Sep 10 2021 01:22:26.603591 - ===== vive: state=4, NOT empty, uri=file:///home/orangestar/.local/share/Steam/steamapps/common/SteamVR/resources/config/legacy_bindings_generic_hmd.json
                                  [Snip: Previous 2 messages repeated 11 times]
Fri Sep 10 2021 01:22:34.676967 - Socket closed
Fri Sep 10 2021 01:22:34.677029 - Unable to read message from socket: 0
Fri Sep 10 2021 01:22:34.677067 - Process vrcompositor (45034) disconnected (Thread(0x0x7f3a200030d0/0x0x7f)
Fri Sep 10 2021 01:22:34.677104 - AppInfoManager.ProcessQuit processid=45034 eLaunchingApp=LaunchingApp_None
Fri Sep 10 2021 01:22:34.677119 - AppInfoManager.ProcessQuit: Clearing application openvr.component.vrcompositor PID was 45034
Fri Sep 10 2021 01:22:34.677137 - AppInfoManager.ProcessQuit: Clearing application openvr.component.vrcompositor PID because 45034 has exited
Fri Sep 10 2021 01:22:35.019778 - Excessive binding loads from steam (18668): crc=3209310505 lc=2 Reload=F res=2
Fri Sep 10 2021 01:22:35.019845 - ===== vive: state=4, NOT empty, uri=file:///home/orangestar/.local/share/Steam/steamapps/common/SteamVR/resources/config/legacy_bindings_generic_hmd.json
Fri Sep 10 2021 01:22:42.591620 - [System] Transition from 'SteamVRSystemState_Ready' to 'SteamVRSystemState_NotReady'.
Fri Sep 10 2021 01:22:42.684436 - Excessive binding loads from steam (18668): crc=3209310505 lc=2 Reload=F res=2
Fri Sep 10 2021 01:22:42.684500 - ===== vive: state=4, NOT empty, uri=file:///home/orangestar/.local/share/Steam/steamapps/common/SteamVR/resources/config/legacy_bindings_generic_hmd.json
Fri Sep 10 2021 01:22:43.671803 - Excessive binding loads from steam (18668): crc=3209310505 lc=2 Reload=F res=2
Fri Sep 10 2021 01:22:43.671883 - ===== vive: state=4, NOT empty, uri=file:///home/orangestar/.local/share/Steam/steamapps/common/SteamVR/resources/config/legacy_bindings_generic_hmd.json
Fri Sep 10 2021 01:22:43.825925 - [Status Alert] SteamVR Fail (-203)

After this, the headset goes dark and the monitor window displays the -203 error.
Ignore the "Excessive binding loads" messages, it seems to be a separate issue (#307)

Manjaro Linux
NVidia Driver 470.63.01
Geforce 1060
Original Vive
Steam client beta, version 1631237534
SteamVR Beta, version 1.19.7 (1629236071)
Here's my System Report

[kaiwasaki]

I am suffering from the same problem. Although I just acquired a valve index recently. It seems to me to some games tigger the 203 error faster than others. I can play Alyx fopr quite some time. If I try No Man's Sky VR I get 203 error almost instantly.

Here is my inxi Output:

System:    Host: kai-Z390 Kernel: 5.14.0-0-MANJARO x86_64 bits: 64 Desktop: Xfce 4.16.0 Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX Z390-F GAMING v: Rev 1.xx serial: 180937134403225 
           UEFI: American Megatrends v: 1602 date: 06/04/2020 
Memory:    RAM: total: 15.55 GiB used: 3.67 GiB (23.6%) 
           Array-1: capacity: 64 GiB slots: 4 EC: None 
           Device-1: ChannelA-DIMM1 size: No Module Installed 
           Device-2: ChannelA-DIMM2 size: 8 GiB speed: 3200 MT/s 
           Device-3: ChannelB-DIMM1 size: No Module Installed 
           Device-4: ChannelB-DIMM2 size: 8 GiB speed: 3200 MT/s 
CPU:       Info: 6-Core model: Intel Core i5-9600K bits: 64 type: MCP cache: L2: 9 MiB 
           Speed: 800 MHz min/max: 800/4600 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 846 5: 800 6: 800 
Graphics:  Device-1: NVIDIA TU106 [GeForce RTX 2070] driver: nvidia v: 470.63.01 
           Display: server: X.Org 1.20.13 driver: loaded: nvidia resolution: 1: 1920x1200~60Hz 2: 2560x1440 
           OpenGL: renderer: NVIDIA GeForce RTX 2070/PCIe/SSE2 v: 4.6.0 NVIDIA 470.63.01 
Audio:     Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel 
           Device-2: NVIDIA TU106 High Definition Audio driver: snd_hda_intel 
           Sound Server-1: ALSA v: k5.14.0-0-MANJARO running: yes 
           Sound Server-2: PipeWire v: 0.3.34 running: yes 
Info:      Processes: 317 Uptime: 53m Shell: Zsh inxi: 3.3.06 

[Synkstar]

It fixes this if you disable async re-projection as someone stated above. Async re-projection when it works makes it so it is more smooth when you have low fps. The Nvidia 470 driver recently implemented support for async re-projection so its either a problem with the driver or valves implementation of it. It crashes on Half life alyx and NEOS vr. So basically anything with it enabled for me.

Hello @LiamDawe, it might be interesting to test if nvidia 470.xx + #227 (comment) works around the issue you're seeing.

Edit: It seems to work for awhile with async reprojection. It is a lot smoother but ends up crashing after awhile and is kind of annoying.

[mSparks43]

This is more of an issue now that you can't build a kernel module for 465 drivers on 5.14 kernels.
SteamVR also locks up the whole machine requiring a hard reboot when it is closed.

It fixes this if you disable async re-projection as someone stated above.

How do I do that (#470 is without an application even running, and afaik you can only disable async on a per application basis)

[Orangestar12]

This is more of an issue now that you can't build a kernel module for 465 drivers on 5.14 kernels.

I don't know where you got that idea from. Building 465 drivers works fine for me on 5.14 using nvidia-all. If you haven't used that yet, give it a shot.

[mSparks43]

This is more of an issue now that you can't build a kernel module for 465 drivers on 5.14 kernels.

I don't know where you got that idea from. Building 465 drivers works fine for me on 5.14 using nvidia-all. If you haven't used that yet, give it a shot.

The kernel headers changed in such a way as to break both the nvidia installer, eg
https://www.nvidia.com/download/driverResults.aspx/171980/en-us

and kmod-nvidia from rpmfusion

rather not blow up my system with random guesses, 465 is end of life and SteamVR requires a hard system reboot to close it down on 470+.

Are you sure you didn't just fall back on llvmpipe?

EDIT:Some progress on this. switching to wayland, recompling stuff, enabling gdm and a couple of other things I forget improved the situation somewhat, but its not really in a usable state (legacy reprojection and async reprojection both now unusable on 470+) guess Im just SOL until this lot matures.

[Orangestar12]

I don't think I'd be getting the performance (or VR support) I'm getting on my computer with pure llvmpipe.

[quantumac]

FYI: SteamVR Fail (-203) error is still present with the latest SteamVR 1.20.4 beta update, which is a "build candidate for full release" according to the release notes.
GPU: NVIDIA GTX 1080
Driver: 470.74
OS: Ubuntu 20.04

[Frozenreflex]

Still an issue even with Async Reprojection disabled
Nvidia RTX 2060 Super, Driver 495, Linux Mint
Sat Nov 06 2021 18:01:21.838229 - Failed Watchdog timeout in thread Render in WaitForPresent after 5.572546 seconds. Aborting.
This is likely an issue with the game itself and not Proton.

[mSparks43]

Im back up and running after updating to nvidia driver 470.82
still get artifacts, but at least it works and well once an application starts.

the 495.44 on new feature branch is still really buggy.

So its an nvidia driver issue by the looks of it.
Cant open the settings page tho.

[dec05eba]

For me async reprojection completely freezes my computer for a few seconds until steamvr crashes and vr stops working. This happens 100% of the time. It happens immediately after steamvr launches.

[Synkstar]

I really wish nvidia would just open source their drivers. Like amd gpu users aren't having this issue. I know people using vr on Linux with amd cards perfectly fine. Sadly its still hard to get new gpus without getting it from a scalper. There is really no reason for nvidia to not open source them. So it is definitely a nvidia driver issue like @mSparks43 mentioned.

[ZarathustraDK]

Just adding to the pile. I also seem to get frequent freezes/crashes with looping sound when running demanding games (particularly VRChat and Blade & Sorcery) with asynchronous reprojection on. Seems like some process in the chain is overwhelmed because it always happen when there's "a lot going on" or upon loading into a new world. Maybe there has been an update trying to fix some of the other async bugs considering the crashes seem to happen under circumstances where asynchronous reprojection should kick in?

This is on the latest proton, Radeon 6800XT and Ryzen 5900X.

[quantumac]

The latest SteamVR release, 1.21.1, still has the -203 error issue.

I sure wish some friendly, helpful developers at Valve would take some time to address this reoccurring error. We customers would appreciate it quite a lot. I'd try my hand at fixing it myself but, hey... closed source. Can't do much without access to source code.

OS: Ubuntu 20.04 (Linux)
SteamVR: 1.21.1
NVIDIA driver: 470.82.00
GPU: GTX 1080

[earldbjr]

That would be wild. Both our rigs are using nvme.

[okawo80085]

My setup uses nvme ssds too, but that being the reason could only mean that the kernel ssd driver is miss behaving, which afaik is not the case.

Just to be safe though, i'm on kernel 5.13.0-25-generic.

[okawo80085]

Found a new way to consistently reproduce the -203 crash by the watchdog manager thread eval method, with nothing running at all, not even SteamVR Home, just plain compositor.

So Valve Index has this funny refresh rate setting, and turns out i had mine at 90hz this entire time, so i decided to switch to 144hz and wouldn't you know it, almost an instant crash... right after i connected my controllers.
Let me reiterate, there is no crash until i connect controllers, nothing seems wrong, tracking is smooth and all, but as soon as i turn on my controllers and they connect: boom, DE hangs for a bit and SteamVR crashes with -203 (caused by the same ThreadWatchdogManager::EvaluateWatchdogs() method every time, according to the stack trace). Furthermore reading into that method's assembly (also considering the exit signal) it looks like this particular crash is caused by an unhandled exception...

Upside is that bumping my refresh rate to 144hz almost completely fixed #21 for me.

coredump:

$ coredumpctl info
           PID: 46614 (vrcompositor)
           UID: 1000 (okawo)
           GID: 1000 (okawo)
        Signal: 6 (ABRT)
     Timestamp: Mon 2022-01-31 21:06:24 EET (13h ago)
  Command Line: /home/okawo/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor
    Executable: /home/okawo/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor
 Control Group: /user.slice/user-1000.slice/user@1000.service/gnome-launched-steam.desktop-8423.scope
          Unit: user@1000.service
     User Unit: gnome-launched-steam.desktop-8423.scope
         Slice: user-1000.slice
     Owner UID: 1000 (okawo)
       Boot ID: a3fa7b168ba5425fba65785a6395e24c
    Machine ID: 48b93e9f9d08410ab31494403c4441bc
      Hostname: okawo
       Storage: /var/lib/systemd/coredump/core.vrcompositor.1000.a3fa7b168ba5425fba65785a6395e24c.46614.1643655984000000000000.lz4
       Message: Process 46614 (vrcompositor) of user 1000 dumped core.
                
                Stack trace of thread 46669:
                #0  0x00007f85826e318b __GI_raise (libc.so.6 + 0x4618b)
                #1  0x00007f85826c2859 __GI_abort (libc.so.6 + 0x25859)
                #2  0x0000560dacfdf619 n/a (/home/okawo/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor + 0x4d619)
                #3  0x0000560dad0b5445 n/a (/home/okawo/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor + 0x123445)
                #4  0x0000560dad2b1bf0 n/a (/home/okawo/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor + 0x31fbf0)

Headset: Valve Index
Controllers: Vive Wands
SteamVR version: 1.21.6 [beta]
OS: Ubuntu 20.04.3 LTS
Kernel: 5.13.0-27-generic
GPU: RTX 3060
GPU driver: 495.46

[earldbjr]

Problem has occurred for me at both 90 and 144, for what it's worth.

[okawo80085]

Don't get me wrong it happens to me on all refresh rates too, but on 144hz it just happens way faster than usual.

[mSparks43]

Just moved to the new 510 Nvidia driver. First one since 470.86 which doesn't seem to have this issue.

[earldbjr]

Can confirm. Checked all the crash spots on phas with Nvidia 510 and neither of us could 203 over the course of an hour.

[LiamDawe]

Yup, unless someone says otherwise I think this is solved. It is for me now too.

[mato6666663]

You guys really brought my hopes up. I just installed 511 nvidia driver, but the game crashed again...

[earldbjr]

Crashed with a 203? What were you doing when it happened? What game?

[mato6666663]

Yes. Half life alyx. Just tried it now. The same behavior as always. When the crash occurs, I got the screen in my VR headset frozen, the sounds countinued though, and the mirrored picture of the game on my desktop screen was still moving as I moved my headset. To me, upgrading or downgrading the nvidia driver has never helped in this.

The error started coming after I changed my HDD for a newer SSD after a clean windows installation. Even after upgrading to windows 11, the problem persisted. :(

[kisak-valve]

Hello @mato6666663, it should be noted that issues in this issue tracker are specifically for the Linux variant of SteamVR. Issues with SteamVR on Windows should be reported over on https://steamcommunity.com/app/250820/discussions/3/ or maybe Steam Support for the larger SteamVR team to ponder.

[mato6666663]

My apologies. There doesn't seem to be another forum with the same issue that has so much feedback from other users experiencing the same error, so I thought I would drop in to contribute, as the error reported here has the same behavior as what I'm experiencing.

PS: my game crashed again. First, it showed error code -204, then it changed to -203.

[okawo80085]

I can not reproduce any of my prior crashes with the 510.39.01 nvidia driver either. 144hz device activation does not trigger a watchdog manager eval throw, Half-Life: Alyx save loads work flawlessly too; Beat Saber, Pistol Whip, Zenith MMO, all work fine as well.
Haven't tried VRChat yet though, i'll test it next time. Hopefully it also works without a hitch🤞.

[quantumac]

I tried manually installing the NVIDIA 510.39.01 and the 510.47.03 drivers. SteamVR HOME ran with them, but VRChat wasn't happy. Some DirectX library was missing. I tried uninstalling and reinstalling VRChat, but no difference. So I reverted to my backup. I guess I'll wait until the Ubuntu NVIDIA PPA repository maintainers provide support for 510.

[earldbjr]

Fwiw when I manually installed the 5.10 I had to search and destroy remnant files from previous drivers. Might be worth looking through apt and searching in the terminal. Causes all kinds of random problems sometimes.

[maxhille]

@quantumac the Ubuntu PPA at https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa now has the 510.47.03 driver.

I tried my very reliable method to produce the -203 error with the 510.47.03 driver and it still crashes for me. What I do is load up X-Plane (Vulkan) in VR with a very demanding scene (ToLiss A319, Orthos, detailed Airport). SteamVR will crash within max 5 seconds.

log snippet

Thu Feb 03 2022 22:37:54.142766 - Excessive binding loads from steam (20826): crc=4054094268 lc=6 Reload=F res=2
Thu Feb 03 2022 22:37:54.142822 - ===== indexhmd: state=4, NOT empty, uri=file:///home/mh/.steam/steamapps/common/SteamVR/resources/config/legacy_bindings_generic_hmd.json
Thu Feb 03 2022 22:37:54.142886 - ===== knuckles: state=4, NOT empty, uri=file:///home/mh/.steam/steamapps/common/SteamVR/drivers/indexcontroller/resources/input/legacy_bindings_index_controller.json
Thu Feb 03 2022 22:37:54.145474 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.174490 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.195372 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.236301 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.292563 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.343100 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.360839 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.392988 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.423195 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.442486 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.485392 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.540340 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.591679 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.610923 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.640340 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.673155 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.688421 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.735072 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.788182 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.837271 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.856313 - Excessive binding loads from steam (20826): crc=4054094268 lc=6 Reload=F res=2
Thu Feb 03 2022 22:37:54.856388 - ===== indexhmd: state=4, NOT empty, uri=file:///home/mh/.steam/steamapps/common/SteamVR/resources/config/legacy_bindings_generic_hmd.json
Thu Feb 03 2022 22:37:54.856475 - ===== knuckles: state=4, NOT empty, uri=file:///home/mh/.steam/steamapps/common/SteamVR/drivers/indexcontroller/resources/input/legacy_bindings_index_controller.json
Thu Feb 03 2022 22:37:54.860125 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.885352 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.920541 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.936134 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:54.983942 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.035064 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.085569 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.108503 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.135725 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.166733 - 0 - entering standby
Thu Feb 03 2022 22:37:55.170742 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.184474 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.232014 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.283714 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.294359 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.333490 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.356421 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.382667 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.418486 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.432908 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.481620 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.528710 - Excessive binding loads from steam (20826): crc=4054094268 lc=6 Reload=F res=2
Thu Feb 03 2022 22:37:55.528778 - ===== indexhmd: state=4, NOT empty, uri=file:///home/mh/.steam/steamapps/common/SteamVR/resources/config/legacy_bindings_generic_hmd.json
Thu Feb 03 2022 22:37:55.528860 - ===== knuckles: state=4, NOT empty, uri=file:///home/mh/.steam/steamapps/common/SteamVR/drivers/indexcontroller/resources/input/legacy_bindings_index_controller.json
Thu Feb 03 2022 22:37:55.531241 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.543641 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.581998 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.605485 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.631968 - Unable to find input 'z' in filter click_button_actions_legacy_18_user_hand_right_input_thumbstick
Thu Feb 03 2022 22:37:55.636884 - [Status Alert] SteamVR Fail (-203)

[amalon]

I just managed to hit -203 failure on paper beasts.
Previously it happened almost straight away unless switched to legacy reprojection mode, but still happened eventually.
This time (NVIDIA 510.47.03, archlinux) I switched back to default reprojection settings and it lasted 20mins, but still hit it at I think about the same point as with legacy reprojection before. SteamVR seemed to recover back to SteamVR home after closing paper beasts.
So I'm guessing only a subset of triggers of this issue (relating to async reprojection) have been resolved by the new driver.

[maxhille]

@kisak-valve (pinging you as you are the most recent committer on this repo):

This issue seems to be affecting a lot of people across lots of distros. This and that it is hard to say whether this is a SteamVR and/or Nvidia issue, maybe some insights from the SteamVR side would be great.

[ColdIce1605]

Affects me in NeosVR.(If that's of any note all my other VR games/apps run fine.

[Orangestar12]

More recent NVidia drivers have largely mitigated this problem for me, but I still get this crash during prolonged playtimes or more strenuous VR applications (such as the above-mentioned Neos VR - mostly when running it through Proton to use the KFC/NCR-enabled build.)

[Frozenreflex]

More recent NVidia drivers have largely mitigated this problem for me, but I still get this crash during prolonged playtimes or more strenuous VR applications (such as the above-mentioned Neos VR - mostly when running it through Proton to use the KFC/NCR-enabled build.)

I believe Neos is the cause of the issues and not Proton, is it the issue where the screen freezes and it'll randomly either crash or continue to be frozen and output unresponsive engine messages in the logs? If so, there are Windows users that have the issue as well.

[Orangestar12]

I believe Neos is the cause of the issues and not Proton, is it the issue where the screen freezes and it'll randomly either crash or continue to be frozen and output unresponsive engine messages in the logs? If so, there are Windows users that have the issue as well.

I would agree with this sentiment if I didn't experience the precise, exact same issue with Elite Dangerous and Pavlov VR, and didn't experience them on my Windows install. As far as I can tell, the issue is localized to SteamVR on Linux.

[Frozenreflex]

Replying to #452 (comment)

I've played Boneworks, H3VR, Skyrim VR (modded with Mod Organizer 2), No Man's Sky, Blade and Sorcery, Phasmophobia, The Wizards, The Wizards: Dark TImes, and Ancient Dungeon VR through Proton, and Garry's Mod VR and Half-Life: Alyx without, and have never had the issue. Only Neos has this for me.

[Orangestar12]

I'm unsure of how this all really mixes together, but could it be possible a fix for this could happen upstream now that the NVIDIA GPU kernel modules are open source?
https://github.com/NVIDIA/open-gpu-kernel-modules

[okawo80085]

Well, this issue is already hard to catch, but still present for some peeps. Nvidia open sourcing their driver will help a lot though, it'll take some time, but we are not fighting black boxes anymore!

[RinLovesYou]

Interesting tidbid, i run a windows 11 vm purely for vr at the moment because of this issue.

I got this exact crash on windows 11, it was related to their gpu scheduling feature in windows 11. After turning it off it never happened again. Might be related to gpu scheduling here too

Also: if you're thinking about debugging this, and want to reproduce it, the prime suspect games are VRChat, and ChilloutVR, in worlds with a lot of players. High load situations seem to force it forward

[erkexzcx]

Starting Beat Saber instantly crashes with -203, while other VR games run fine...

Arch Linux, 6.3.5-1-cachyos-bore, NVidia driver 530.41.03. Tried both betas of Steam as well as SteamVR - same behavior.

---

EDIT: I installed dual boot on my PC. Here are my remarks:

1. VR performance/stability/latency and everything else difference is like day & night. It's so good on Windows...
2. Installed Windows:
   2.1 BTRFS partition which is used by OS can be reduced on live system, using Gparted. This made things so much easier.
   2.2 Installed Windows on an unused space.
   2.3 Installed WinBtrfs. Now my HDD and separate SSD (for games) is visible in Windows without requiring to format them.
   2.4 Steam on both Windows and Linux can share the same library.

Guys, don't waste your time for VR on Linux. It has, does and will suck on Linux. It's been quite a few years and yet not much of a progress. Either sell it or use on Windows, no other way. Valve should stop advertising Linux as supported platform or dedicate some serious resources for this.

Considering Steam Deck success, it might be the beginning of Linux as a gaming platform, so things might get better in the future. :)

[Mon-Ouie]

Recently started getting this issue with a GTX 1080 and NVidia drivers 535.54.03-3 on Xorg. I hadn't encountered this issue in the past, but now it inevitably happens after a few minutes, sometimes even sooner.

Disabling async reprojection (opening up mirror view, debug commands, and toggling it off with shift+a) seems to completely resolve the issue (although obviously you'd prefer not to turn it off). Was able to stay one hour in VRChat and Beat Saber without crashing after trying this.