SteamVR

SteamVR

Steamvr error 208 with Vive Pro
So, today, when i started steamvr it had error 208, but yesterday everything was ok. After reinstalation of GPU drivers, reconnecting vr set and reinstalling steamvr, it started to work again. I turned off steamvr and was minding my business, but when i decided to play some Radius, and started up steamvr, it was error 208 again. Any suggestions how to fix it? I don't think there is a problem with a cable, because when i use physical button on vr set to turn on steamvr, it's stating up.
< >
Showing 1-7 of 7 comments
Bob Loblaw Dec 10, 2024 @ 11:05pm 
Check SteamVR support wizard https://help.steampowered.com/en/wizard/HelpWithGame/?appid=250820

Prior causes/fixes of SteamVR Error 200, -203, 204, 208, 210, 215:
AMD GPU error 200, change bitrate ( https://steamcommunity.com/app/353380/discussions/11/4038102936180242093/ )
HMD plugged into motherboard instead of GPU
GPU drivers. Do a clean uninstall and install of the latest,
Use a different port on the GPU,
Plug in only 1 monitor, try different refresh rates on it.
Bad adapters on the video cable,
Use regedit to change window's Timeout Detection and Recovery (TdrLevel) of the GPU driver ( https://steamcommunity.com/app/250820/discussions/2/4692279782565391419/?tscn=1729147381 )
Linkbox issue (bypass it) ( https://steamcommunity.com/app/250820/discussions/0/4356743146672090646/?tscn=1711568860 )
Pet chewed your cable,
SteamVR overlays of any kind (ovr, etc),
Security software,
Auto-overclocking software (like Razer Cortex Auto Boost)
Enabling re-projection on WMR (try disabling it)
WMR needed SteamVR set to DX11 + restart ( https://steamcommunity.com/app/250820/discussions/0/4515506834330086955/?tscn=1723268870 )
Enabled Hardware-accelerated GPU scheduling (disable HAGS) ( https://steamcommunity.com/app/250820/discussions/2/3187992458108815903/?tscn=1708472861 )
Optimizations for windows games in GPU options (disable it) ( https://steamcommunity.com/app/250820/discussions/0/4293692546845646378/?tscn=1711311480 )
Laptop video port not directly controlled by GPU
Need to disable AMD integrated graphics in BIOS ( https://www.reddit.com/r/Vive/comments/15u862z/vive_pro_2_w_wireless_adapter_worked_perfectly/ )
unconfirmed: try running steam as admin
Thunderbolt port is not SteamVR compatible with i12 cpu or later ( https://www.reddit.com/r/Vive/comments/17v59wn/vive_pro_2_black_screen_error_210/ )
ref: intel gen
error 215 from windows internet set to public instead of private ( https://steamcommunity.com/app/250820/discussions/0/4036979713112601939/?tscn=1704207190 )
Originally posted by Bob Loblaw:
Check SteamVR support wizard https://help.steampowered.com/en/wizard/HelpWithGame/?appid=250820

Prior causes/fixes of SteamVR Error 200, -203, 204, 208, 210, 215:
AMD GPU error 200, change bitrate ( https://steamcommunity.com/app/353380/discussions/11/4038102936180242093/ )
HMD plugged into motherboard instead of GPU
GPU drivers. Do a clean uninstall and install of the latest,
Use a different port on the GPU,
Plug in only 1 monitor, try different refresh rates on it.
Bad adapters on the video cable,
Use regedit to change window's Timeout Detection and Recovery (TdrLevel) of the GPU driver ( https://steamcommunity.com/app/250820/discussions/2/4692279782565391419/?tscn=1729147381 )
Linkbox issue (bypass it) ( https://steamcommunity.com/app/250820/discussions/0/4356743146672090646/?tscn=1711568860 )
Pet chewed your cable,
SteamVR overlays of any kind (ovr, etc),
Security software,
Auto-overclocking software (like Razer Cortex Auto Boost)
Enabling re-projection on WMR (try disabling it)
WMR needed SteamVR set to DX11 + restart ( https://steamcommunity.com/app/250820/discussions/0/4515506834330086955/?tscn=1723268870 )
Enabled Hardware-accelerated GPU scheduling (disable HAGS) ( https://steamcommunity.com/app/250820/discussions/2/3187992458108815903/?tscn=1708472861 )
Optimizations for windows games in GPU options (disable it) ( https://steamcommunity.com/app/250820/discussions/0/4293692546845646378/?tscn=1711311480 )
Laptop video port not directly controlled by GPU
Need to disable AMD integrated graphics in BIOS ( https://www.reddit.com/r/Vive/comments/15u862z/vive_pro_2_w_wireless_adapter_worked_perfectly/ )
unconfirmed: try running steam as admin
Thunderbolt port is not SteamVR compatible with i12 cpu or later ( https://www.reddit.com/r/Vive/comments/17v59wn/vive_pro_2_black_screen_error_210/ )
ref: intel gen
error 215 from windows internet set to public instead of private ( https://steamcommunity.com/app/250820/discussions/0/4036979713112601939/?tscn=1704207190 )
Ok, it's working again, but i litteraly have no idea, how it got fixed. So, here's what happend:
I've returned home, stated up steam vr, there still was an error 208. I've decided, to connect my original vive, to see if it will work. I've pluged all cables and started up steam vr, and it was working, no errors. After that, i started to inspect cables of Vive Pro, to check if it's ok, but the only thing that i noticed, was a little bended part on the connector of cable that connects helmet to link box, here's how that looked:
https://drive.google.com/file/d/1qQ1BoyN4CVM9xzTvc8J7KmEBlvQm4Y5Y/view?usp=drive_link
So, after that, i decided to plug in Vive Pro again. I stared up steam vr again, and... IT'S WORKING AGAIN.
I'm honestly have zero ideas, how it was fixed, but, problem is solved, so, I'm happy. But I still have a couple of questions:
1)What the actual ♥♥♥♥ was that?
2)Was the cable the real cause of the problem?
3)Should I get the new cable?
Sepfox Dec 11, 2024 @ 10:12am 
Originally posted by SSgt. Tomoko Kuroki:
Originally posted by Bob Loblaw:
Check SteamVR support wizard https://help.steampowered.com/en/wizard/HelpWithGame/?appid=250820

Prior causes/fixes of SteamVR Error 200, -203, 204, 208, 210, 215:
AMD GPU error 200, change bitrate ( https://steamcommunity.com/app/353380/discussions/11/4038102936180242093/ )
HMD plugged into motherboard instead of GPU
GPU drivers. Do a clean uninstall and install of the latest,
Use a different port on the GPU,
Plug in only 1 monitor, try different refresh rates on it.
Bad adapters on the video cable,
Use regedit to change window's Timeout Detection and Recovery (TdrLevel) of the GPU driver ( https://steamcommunity.com/app/250820/discussions/2/4692279782565391419/?tscn=1729147381 )
Linkbox issue (bypass it) ( https://steamcommunity.com/app/250820/discussions/0/4356743146672090646/?tscn=1711568860 )
Pet chewed your cable,
SteamVR overlays of any kind (ovr, etc),
Security software,
Auto-overclocking software (like Razer Cortex Auto Boost)
Enabling re-projection on WMR (try disabling it)
WMR needed SteamVR set to DX11 + restart ( https://steamcommunity.com/app/250820/discussions/0/4515506834330086955/?tscn=1723268870 )
Enabled Hardware-accelerated GPU scheduling (disable HAGS) ( https://steamcommunity.com/app/250820/discussions/2/3187992458108815903/?tscn=1708472861 )
Optimizations for windows games in GPU options (disable it) ( https://steamcommunity.com/app/250820/discussions/0/4293692546845646378/?tscn=1711311480 )
Laptop video port not directly controlled by GPU
Need to disable AMD integrated graphics in BIOS ( https://www.reddit.com/r/Vive/comments/15u862z/vive_pro_2_w_wireless_adapter_worked_perfectly/ )
unconfirmed: try running steam as admin
Thunderbolt port is not SteamVR compatible with i12 cpu or later ( https://www.reddit.com/r/Vive/comments/17v59wn/vive_pro_2_black_screen_error_210/ )
ref: intel gen
error 215 from windows internet set to public instead of private ( https://steamcommunity.com/app/250820/discussions/0/4036979713112601939/?tscn=1704207190 )
Ok, it's working again, but i litteraly have no idea, how it got fixed. So, here's what happend:
I've returned home, stated up steam vr, there still was an error 208. I've decided, to connect my original vive, to see if it will work. I've pluged all cables and started up steam vr, and it was working, no errors. After that, i started to inspect cables of Vive Pro, to check if it's ok, but the only thing that i noticed, was a little bended part on the connector of cable that connects helmet to link box, here's how that looked:
https://drive.google.com/file/d/1qQ1BoyN4CVM9xzTvc8J7KmEBlvQm4Y5Y/view?usp=drive_link
So, after that, i decided to plug in Vive Pro again. I stared up steam vr again, and... IT'S WORKING AGAIN.
I'm honestly have zero ideas, how it was fixed, but, problem is solved, so, I'm happy. But I still have a couple of questions:
1)What the actual ♥♥♥♥ was that?
2)Was the cable the real cause of the problem?
3)Should I get the new cable?
Hard to say, honestly. SteamVR throws this error when it detects a error with the VR headset's display configuration. If you use a AMD GPU, try the latest driver or a version before that, since AMD secretly made changes to the code handling this for VR Headsets to fix a bug causing latency, however, all of this is completely undocumented on the driver changelogs. (This change happened with version 24.12.1)

I own a Vive Pro Eye myself (which is essentially the same headset fundamentally), and I have a few friends who run lens-modded Vive Pro 1's.

From my experience and from their experience, the cable *is* really fragile, and the two biggest points of failure are at the capacitor close to where the cable routes into the loop and then plugs into the headset, or at the part where it bends downwards from the Headset clip.

If a cable starts to cause issues, it's usually either the USB slowly fading out and losing bandwith (which means loss or cutouts of tracking, in my case eyetracking too, and loss of connection or bandwith for the device you have plugged into the headset's USB-C port, if any), or the display signal degrades heavily to the point of low framerates, artifacts etc. I would not fully rule the cable out, especially if you have bad bends on the cable clip.

If you can afford it, I would order a spare *NEW* cable anyway, just so you have one around to see if maybe it was indeed the cable, and if it ends up not being that, at least you'll have a spare cable lying around for a otherwise pretty fragile cable. HTC discounted the price of the cable ever since the Vive Pro 2 released, so while it's still expensive as a cable, it's much cheaper than what it used to be (I think ~60$)
Last edited by Sepfox; Dec 11, 2024 @ 10:13am
Originally posted by Sepfox:
Originally posted by SSgt. Tomoko Kuroki:
Ok, it's working again, but i litteraly have no idea, how it got fixed. So, here's what happend:
I've returned home, stated up steam vr, there still was an error 208. I've decided, to connect my original vive, to see if it will work. I've pluged all cables and started up steam vr, and it was working, no errors. After that, i started to inspect cables of Vive Pro, to check if it's ok, but the only thing that i noticed, was a little bended part on the connector of cable that connects helmet to link box, here's how that looked:
https://drive.google.com/file/d/1qQ1BoyN4CVM9xzTvc8J7KmEBlvQm4Y5Y/view?usp=drive_link
So, after that, i decided to plug in Vive Pro again. I stared up steam vr again, and... IT'S WORKING AGAIN.
I'm honestly have zero ideas, how it was fixed, but, problem is solved, so, I'm happy. But I still have a couple of questions:
1)What the actual ♥♥♥♥ was that?
2)Was the cable the real cause of the problem?
3)Should I get the new cable?
Hard to say, honestly. SteamVR throws this error when it detects a error with the VR headset's display configuration. If you use a AMD GPU, try the latest driver or a version before that, since AMD secretly made changes to the code handling this for VR Headsets to fix a bug causing latency, however, all of this is completely undocumented on the driver changelogs. (This change happened with version 24.12.1)

I own a Vive Pro Eye myself (which is essentially the same headset fundamentally), and I have a few friends who run lens-modded Vive Pro 1's.

From my experience and from their experience, the cable *is* really fragile, and the two biggest points of failure are at the capacitor close to where the cable routes into the loop and then plugs into the headset, or at the part where it bends downwards from the Headset clip.

If a cable starts to cause issues, it's usually either the USB slowly fading out and losing bandwith (which means loss or cutouts of tracking, in my case eyetracking too, and loss of connection or bandwith for the device you have plugged into the headset's USB-C port, if any), or the display signal degrades heavily to the point of low framerates, artifacts etc. I would not fully rule the cable out, especially if you have bad bends on the cable clip.

If you can afford it, I would order a spare *NEW* cable anyway, just so you have one around to see if maybe it was indeed the cable, and if it ends up not being that, at least you'll have a spare cable lying around for a otherwise pretty fragile cable. HTC discounted the price of the cable ever since the Vive Pro 2 released, so while it's still expensive as a cable, it's much cheaper than what it used to be (I think ~60$)
Driver issue? Hmm, maybe it is the source of a problem, since i upgraded to RX6600 this summer. Anyway, that's a good point, having a spare cable definetly wouldn't harm, i already found a guy selling one at a good price, think i will buy it next week
Sepfox Dec 13, 2024 @ 9:11am 
If you gave it a try, let us know if tinkering with the driver or changing the cable helped you out! :3
SSgt. Tomoko Kuroki Dec 21, 2024 @ 12:40am 
Originally posted by Sepfox:
If you gave it a try, let us know if tinkering with the driver or changing the cable helped you out! :3
Update: So, problems was indeed caused by the cable. This whole week, while i was waiting for a new cable was a dissaster, in order to use vr, i had to restart steam vr about 7 or 8 times, on a first start, it would boot up, but displays wouldn't show anything, just a black screens, on a second try it steam vr had 208 error, on a third try it would start up, but had contant pink lagspikes, and so on. Yesterday, the new cable arrived, i pluged it in and decided start up steam vr several time, to test it. All 5 booting ups of steam vr was successful, so i left to work. When i came back, i hop on to my friends in vrchat and spend the whole night there, everything was working just perfect. So, yeah, problem was caused by a cable from headset to linkbox, and this is logical, considering that this Vive Pro is second-hand
Sepfox Dec 21, 2024 @ 3:35am 
Originally posted by SSgt. Tomoko Kuroki:
Originally posted by Sepfox:
If you gave it a try, let us know if tinkering with the driver or changing the cable helped you out! :3
Update: So, problems was indeed caused by the cable. This whole week, while i was waiting for a new cable was a dissaster, in order to use vr, i had to restart steam vr about 7 or 8 times, on a first start, it would boot up, but displays wouldn't show anything, just a black screens, on a second try it steam vr had 208 error, on a third try it would start up, but had contant pink lagspikes, and so on. Yesterday, the new cable arrived, i pluged it in and decided start up steam vr several time, to test it. All 5 booting ups of steam vr was successful, so i left to work. When i came back, i hop on to my friends in vrchat and spend the whole night there, everything was working just perfect. So, yeah, problem was caused by a cable from headset to linkbox, and this is logical, considering that this Vive Pro is second-hand
Glad you got it fixed!

And yeah, the cable is the culprit most of the times if USB/display cuts out on the VP1/VPE/VP2. Hope I helped you out :3
< >
Showing 1-7 of 7 comments
Per page: 1530 50

Date Posted: Dec 10, 2024 @ 1:47pm
Posts: 7