Jump to content

Recommended Posts

Firstly, sorry for posting yet another "help me, my Vive isn't working!" post. I've probably looked through hundreds of others over the last day or so and know it can bloat the subreddit.

I went to use my Vive yesterday after a couple of months of inactivity. My room setup has changed slightly since then, so I went through the room-scale setup without issues and booted up SkyrimVR. I didn't have any display to the headset itself (although I could see in the desktop mirror that the title screen was loaded). Figuring it was some weird glitch with the wireless adapter, I restarted SteamVR. It was at this point that I started to notice other issues. For some reason, my base stations do not remain connected for more than a couple seconds at a time. When first booting up SteamVR, everything will show connected as expected, and although there is still no display output to the Vive itself, I can see from the desktop mirror that it is actually tracking the headset and even controllers properly. After 5-10 seconds though, I hear the Windows disconnect sound and the base station icons become grayed out in SteamVR.

What's odd is that I don't receive any error messages or warnings otherwise. Nothing about sync issues, nothing about headset detection issues, nothing. It also happens even if the headset isn't moved at all, which leads me to believe its not the result of a faulty wire. The only message that consistently pops up just states that SteamVR is searching for the headset, and to ensure that it is in-view of the base stations. When looking in Window's "Bluetooth & Other Devices" window, with just the Vive Wireless app open and connected, I can see devices called "HTC Vive", "HMD/CTRL USB Drivers", and "Lighthouse FPGA RX". After opening SteamVR and waiting about 10 seconds, the "Lighthouse FPGA RX" entry disappears and the HTC Vive entry will get a status of "Driver Error" before disappearing as well. The HTC Vive entry will often reappear and then disappear after a couple of seconds again. Unfortunately, I haven't been able to determine what is specifically meant by "Driver Error", as Windows does not provide any further information.

The following is what I've tried thus far:

  • Testing on various Nvidia drivers (current, drivers from August 2019, and drivers from mid-2017).

  • Disable HEPT

  • Disable XMP

  • Multiple clean reinstalls of SteamVR.

  • Deletion and revalidation of openvr files.

  • Clean reinstall of displaylink drivers.

  • Tested with original link box and cables.

  • Tested with different computer in different environmental setting.

  • Test both base stations on their own in the A-channel.

  • Test on beta branch.

  • Update of Windows

  • Disable Vive camera

  • Reset SteamVR USB devices in SteamVR developer settings

  • Disable power management in SteamVR developer settings

At this point I think most people would assume their equipment is toast and move on, but there are too many inconsistencies for me to really accept that. At first, I assumed it was the wireless adapter, but the Vive Wireless app never loses connection with the adapter or otherwise shows any warnings or errors, and the issue also persists even with cables and a link box. I then assumed it was the headset, but within that initial 10 second window it still tracks perfectly fine, as do the controllers. Given that the issue persisted across different computers (one of which had never installed anything VR related before my test), I'm assuming that the issue is either with my base stations hardware/firmware or some sneaky software bug/option that persisted across computers. The base stations have never been under any kind of stress - never dropped, not in direct light, etc. They are in the same exact orientation they've always been in. They also show all IR lights/smears as they should and consistently have the green status indicator. They do not feel warm to the touch at all. Within that 10 second window, SteamVR seems to think the base stations are up to date.

The main evidence suggesting that the Vive itself is toast is the lack of display output to the headset itself even in that small window. Usually, when turning the Vive on the screen would flash with a ton of green/red pixels for a second before actually turning on. After many hours of troubleshooting, this has only happened a couple of times so it seems that for the most part the Vive isn't even getting to the point of turning the display on. The Vive also hasn't been under any stress since I last used it (not in direct light, literally hasn't been touched). I'm also sure that there are no reflective surfaces in the room, and the issue also isn't natural light.

The fact that the Vive does track for a small amount of time when first opening SteamVR suggests to me that the equipment isn't toast, at least not completely. I do have the log files, but haven't been able to personally make any sense of them so if I can supply those or a system report just let me know.

Thanks everyone.

Link to post
Share on other sites
Posted (edited)
12 hours ago, PatriciaOtero1512 said:

Firstly, sorry for posting yet another "help me, my Vive isn't working!" post. I've probably looked through hundreds of others over the last day or so and know it can bloat the subreddit.

I went to use my Vive yesterday after a couple of months of inactivity. My room setup has changed slightly since then, so I went through the room-scale setup without issues and booted up SkyrimVR. I didn't have any display to the headset itself (although I could see in the desktop mirror that the title screen was loaded). Figuring it was some weird glitch with the wireless adapter, I restarted SteamVR. It was at this point that I started to notice other issues. For some reason, my base stations do not remain connected for more than a couple seconds at a time. When first booting up SteamVR, everything will show connected as expected, and although there is still no display output to the Vive itself, I can see from the desktop mirror that it is actually tracking the headset and even controllers properly. After 5-10 seconds though, I hear the Windows disconnect sound and the base station icons become grayed out in SteamVR.

What's odd is that I don't receive any error messages or warnings otherwise. Nothing about sync issues, nothing about headset detection issues, nothing. It also happens even if the headset isn't moved at all, which leads me to believe its not the result of a faulty wire. The only message that consistently pops up just states that SteamVR is searching for the headset, and to ensure that it is in-view of the base stations. When looking in Window's "Bluetooth & Other Devices" window, with just the Vive Wireless app open and connected, I can see devices called "HTC Vive", "HMD/CTRL USB Drivers", and "Lighthouse FPGA RX". After opening SteamVR and waiting about 10 seconds, the "Lighthouse FPGA RX" entry disappears and the HTC Vive entry will get a status of "Driver Error" before disappearing as well. The HTC Vive entry will often reappear and then disappear after a couple of seconds again. Unfortunately, I haven't been able to determine what is specifically meant by "Driver Error", as Windows does not provide any further information.

The following is what I've tried thus far:

  • Testing on various Nvidia drivers (current, drivers from August 2019, and drivers from mid-2017).

  • Disable HEPT

  • Disable XMP

  • Multiple clean reinstalls of SteamVR.

  • Deletion and revalidation of openvr files.

  • Clean reinstall of displaylink drivers.

  • Tested with original link box and cables.

  • Tested with different computer in different environmental setting.

  • Test both base stations on their own in the A-channel.

  • Test on beta branch.

  • Update of Windows

  • Disable Vive camera

  • Reset SteamVR USB devices in SteamVR developer settings

  • Disable power management in SteamVR developer settings

At this point I think most people would assume their equipment is toast and move on, but there are too many inconsistencies for me to really accept that. At first, I assumed it was the wireless adapter, but the Vive Wireless app never loses connection with the adapter or otherwise shows any warnings or errors, and the issue also persists even with cables and a link box. I then assumed  www.paymydoctor.com it was the headset, but within that initial 10 second window it still tracks perfectly fine, as do the controllers. Given that the issue persisted across different computers (one of which had never installed anything VR related before my test), I'm assuming that the issue is either with my base stations hardware/firmware or some sneaky software bug/option that persisted across computers. The base stations have never been under any kind of stress - never dropped, not in direct light, etc. They are in the same exact orientation they've always been in. They also show all IR lights/smears as they should and consistently have the green status indicator. They do not feel warm to the touch at all. Within that 10 second window, SteamVR seems to think the base stations are up to date.

The main evidence suggesting that the Vive itself is toast is the lack of display output to the headset itself even in that small window. Usually, when turning the Vive on the screen would flash with a ton of green/red pixels for a second before actually turning on. After many hours of troubleshooting, this has only happened a couple of times so it seems that for the most part the Vive isn't even getting to the point of turning the display on. The Vive also hasn't been under any stress since I last used it (not in direct light, literally hasn't been touched). I'm also sure that there are no reflective surfaces in the room, and the issue also isn't natural light.

The fact that the Vive does track for a small amount of time when first opening SteamVR suggests to me that the equipment isn't toast, at least not completely. I do have the log files, but haven't been able to personally make any sense of them so if I can supply those or a system report just let me know.

Thanks everyone.

Any update here???

Edited by PatriciaOtero1512
Link to post
Share on other sites

Please sign in to comment

You need to be a member in order to leave a comment

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...