roywish546 Posted June 19, 2018 Share Posted June 19, 2018 I've been using my vive for slightly over a year now and only until now did it start having problems. I was literally using it yesterday without any issues and didn't touch or break anything overnight. The issue: Turning on SteamVR shows that headset and lighthouses are all connected, but nothing is tracking. Both the HMD and lighthouse icons are solid green, however the HMD flashes for a bit and then goes grey, the lighthouse icons follow shortly after. I've attached a screen recording of what happens Troubleshooting Steps Taken: Reupdating firmware Replugging cables Reinstalling USB devices from developer tab Moving USB from 3.0 to 2.0 and then back Restarting SteamVR Reinstalling SteamVR Restarting Computer Swapping out the HDMI from the HMD to the link box with a working HDMI (also tested the original 3-in-1 HDMI with a monitor and it seems to work fine) Verified that the lighthouses had green light, had B/C on them, all the lasers (15 clustered, and 2 less bright ones on the side and bottom of the cluster) were on Interesting Notes: When I was testing the plugging and unplugging of cables, when I unplug the HDMI, the system seems to work, with the exception of being able to see through the headset. However, all the devices seems to be maintain being green. Another interesting note is that when the devices go grey, you can hear the sound for a USB being removed, not sure if this has any importance. vrserver.txt dump: https://pastebin.com/mG6yjTmH After lots of refreshing, right as the icons go grey, the following messages appear: Tue Jun 19 2018 02:07:41.871 - lighthouse: Lighthouse HMD HID device errorTue Jun 19 2018 02:07:42.070 - lighthouse: Lighthouse IMU HID device errorTue Jun 19 2018 02:07:42.070 - lighthouse: Lighthouse IMU HID device errorTue Jun 19 2018 02:07:42.070 - lighthouse: Lighthouse IMU HID device errorTue Jun 19 2018 02:07:42.070 - lighthouse: Lighthouse Optical HID device error Another message of note that appears frequently in the vrserver.txt Tue Jun 19 2018 02:07:27.292 - lighthouse: LHR-831A737A H: Trying to start tracking from base BAD41914: Available samples not sufficient for booting (hits: 1+2) System: GeForce GTX970, Windows 10 64bit Please help :( I don't know how to further debug this, but this suggests to me that something about the HDMI cable is messing with the ability to detect lighthouses, which makes no sense. Link to comment Share on other sites More sharing options...
HackPerception Posted June 19, 2018 Share Posted June 19, 2018 , thank you for the report. Unfortunately, the data provided doesn't point to a specific cause and you've run through alot of the troubleshooting steps that we typically recommend. Here are a few thoughts: Did windows install update 1803 overnight? That update is messy. Is there the possibly that condensation built up on the HMD overnight? Are you in a room with static discharge issues? While you removed the USB devices via Steam; you can ensure that they're fully nuked by using USBDEVView. It however may be unfesasible given how the devices seem to connect/disconnect. Does the behavior occur when you isolate it to one basestation? Have you tried removing all other USB devices? Have you tried bypassing the linkbox's HDMI and USB leads by plugging these directly into the PC (while keeping power flowing through the linkbox) This could be EMI. Are there any new sources of EM in your space? IR blasters, depth cameras, roombas, ect... Link to comment Share on other sites More sharing options...
roywish546 Posted June 20, 2018 Author Share Posted June 20, 2018 Hi David, Thanks for the response. Here are the answers to your question Windows update 1803 did install, but not overnight, it was installed 16 days ago according to my computer I dry the HMD after every use and usually store it in a space that's room temperature. This has lasted me through last summer as well without problem. No condensation has occured on any other surfaces within the space such as glass or windows.There should be no static discharge issues, it's in an open space that doesn't easily come into contact with objects that would generate static electricity. I also have never gotten shocked in the space. Using USBDEVView, after nuking the USB devices, there were "43 item(s)", after replugging the USB device in and letting things install, there were "59 item(s)" suggesting that 16 items installed (one of which says "HTC Vive" as an "USB Input Device", there's also ones like "Watchman Dongle", "Lighthouse FPGA RX", etc. and a bunch fo ones I'm not sure about) I'm assuming this means that it nuked properly. I tried setting both base stations to "A" separately and seeing if either worked. Neither did. I removed all other devices (except the mouse since I needed it to restart SteamVR) with no luck. Full disclosure, there was an xbox one controller and a keyboard. I did a bypass (Using the vive's HDMI/USB and plugging into the PC), same thing. Did a full bypass (also plugged the power directly into the headset and not using the link box at all), no effect. I have no added any new electrical items to the play space overnight. I typically leave the area alone other than as a open play area. More stuff I tried: So I kept the mirror display open as I unplugged the HDMI between the HMD and the link box. It seems to be working just fine and detecting everything. After reconnecting it and waiting about 40s, the problem reoccurs again. Deleting the following files and attempign room setup again to no avail. (And now I have to reset up room scale again but I can't since the vive doesn't work lol)a. C:\Program Files (x86)\Steam\steamapps\common\SteamVR\resources\settings\default.vrsettingsb. C:\Program Files (x86)\Steam\config\steamvr.vrsettingsc. C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.json Here's the full system report from me trying to turn it off and on Link to comment Share on other sites More sharing options...
SpoonOfDoom Posted July 6, 2018 Share Posted July 6, 2018 I'm having the same problem since last sunday, or at least a very similar one. Have you made any progress towards a solution? I have followed the same troubleshooting steps, but without success so far. One thing I can add for my case: I think it is caused by or at least related to the Bluetooth driver. It worked fine in the afternoon, but after a play session I browsed through the settings and found that you could enable Bluetooth to power manage and update the base stations. Having just painstakingly taken them off the wall and updated the firmware via cable before playing, I thought that was a great idea and enabled it, and when prompted, installed the Bluetooth driver. Since then, I have the behaviour described by . The HMD works fine for roughly 20 seconds (sometimes a few more, sometimes a few less), then fails. After that, the base stations also aren't recognized until HMD reboot. No Windows or NVIDIA updates or any other significant system changes between working and non-working. I don't know if this was mentioned above, but I've noticed that the LED on the headset turns red, which according to Google means "physical hardware or driver error". I have tried disabling Bluetooth again, as well as removing the Bluetooth device from my devices in Windows along with removing its driver, but it just gets reinstalled when I connect the Vive Hardware again. I tried to do a Windows restoration to a point before installing the driver, but for some reason that fails, so I can't say if that would make a difference. I'll take my work laptop home over the weekend so I can test if the Vive still works with another machine, and will update with the results. II haven't been able to make out what the problem is from the logs, but I have noticed that the disconnect always seems to happen immediatlely after a block of AudioDeviceChange messages in vrmonitor.txt (I watched the windows clock and noted the display mirror going grey at 00:50:26): Fri Jul 06 2018 00:50:25.313 - AUDIO: AudioDeviceChangeNotice (noting refresh): 2, device = {0.0.0.00000000}.{eec84ba9-c312-45ef-b9c6-1ed024e6654f}Fri Jul 06 2018 00:50:25.313 - AUDIO: OnDeviceStateChanged: DEVICE_STATE_NOTPRESENT (0x00000004), device = {0.0.0.00000000}.{eec84ba9-c312-45ef-b9c6-1ed024e6654f}Fri Jul 06 2018 00:50:25.313 - AUDIO: AudioDeviceChangeNotice (noting refresh): 4, device = {0.0.0.00000000}.{239461d8-185b-4273-86e7-d3826668216c}Fri Jul 06 2018 00:50:25.313 - AUDIO: OnDefaultDeviceChanged: flow = eRender, role = eCommunications, device = {0.0.0.00000000}.{239461d8-185b-4273-86e7-d3826668216c}Fri Jul 06 2018 00:50:25.325 - AUDIO: AudioDeviceChangeNotice (noting refresh): 2, device = {0.0.1.00000000}.{2cf779c5-d343-4271-afd3-f8346555385a}Fri Jul 06 2018 00:50:25.325 - AUDIO: OnDeviceStateChanged: DEVICE_STATE_NOTPRESENT (0x00000004), device = {0.0.1.00000000}.{2cf779c5-d343-4271-afd3-f8346555385a}Fri Jul 06 2018 00:50:25.325 - AUDIO: AudioDeviceChangeNotice (noting refresh): 4, device = Fri Jul 06 2018 00:50:25.325 - AUDIO: OnDefaultDeviceChanged: flow = eCapture, role = eConsole, device = Fri Jul 06 2018 00:50:25.326 - AUDIO: AudioDeviceChangeNotice (noting refresh): 4, device = Fri Jul 06 2018 00:50:25.326 - AUDIO: OnDefaultDeviceChanged: flow = eCapture, role = eMultimedia, device = Fri Jul 06 2018 00:50:25.326 - AUDIO: AudioDeviceChangeNotice (noting refresh): 4, device = Fri Jul 06 2018 00:50:25.326 - AUDIO: OnDefaultDeviceChanged: flow = eCapture, role = eCommunications, device = Fri Jul 06 2018 00:50:25.326 - AUDIO: AudioDeviceChangeNotice (noting refresh): 4, device = Fri Jul 06 2018 00:50:25.326 - AUDIO: OnDefaultDeviceChanged: flow = eCapture, role = eCommunications, device = Fri Jul 06 2018 00:50:27.444 - [status Warning Added LHR-A7E03A97 Headset(0)] Tracking Device has no pose (0x0008)Fri Jul 06 2018 00:50:27.444 - [status Warning Added LHB-7643B68C Base(1)] Tracking Device has no pose (0x0008)Fri Jul 06 2018 00:50:27.444 - [status Warning Added LHB-ACE8966F Base(2)] Tracking Device has no pose (0x0008)Fri Jul 06 2018 00:50:27.444 - [system] Transition from 'Ready' to 'Not Ready'.Fri Jul 06 2018 00:50:27.448 - [status Alert] Headset not tracking After noticing this, I have tried various audio setting combinations (change audio device on VR start to Vive audio, do not change it, etc.), but it doesn't seem to make a difference. My vrserver.txt excerpt from around that time: Fri Jul 06 2018 00:50:03.931 - Processing message VRMsg_Connect from Steam (6960) took 0.00549 secondsFri Jul 06 2018 00:50:03.960 - [settings] Save Json Settings to C:\Program Files (x86)\Steam\config\steamvr.vrsettingsFri Jul 06 2018 00:50:04.008 - Driver did not provide input profile for device 100000001Fri Jul 06 2018 00:50:04.009 - RendermodelManager: Reading data from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\resources\rendermodels\lh_basestation_vive\lh_basestation_vive.jsonFri Jul 06 2018 00:50:04.009 - Driver did not provide input profile for device 100000002Fri Jul 06 2018 00:50:05.551 - lighthouse: LHR-A7E03A97 H: ----- CALIBRATED base 7643B68C at pitch 21.13 deg roll 1.29 deg -----Fri Jul 06 2018 00:50:05.551 - lighthouse: Updating tilt for 7643B68C: Old= 20.99, 1.28, 1.96354e-06 <- 0.14 deg -> new= 21.13, 1.29, 2.97197e-06 result=21.13, 1.29, 2.97197e-06Fri Jul 06 2018 00:50:05.551 - lighthouse: Best tilt from LHR-A7E03A97 for base 7643B68C pitch 21.13 roll 1.29 score 2.81Fri Jul 06 2018 00:50:05.551 - lighthouse: BootstrapFinished setting tilt base to 7643B68CFri Jul 06 2018 00:50:05.551 - lighthouse: Selected existing universe 1507644976 (7643B68C is primary)Fri Jul 06 2018 00:50:05.551 - lighthouse: Setting universe tilt from 7643B68C via transform to global: pitch 21.13 deg roll 1.29 degFri Jul 06 2018 00:50:05.556 - lighthouse: Saved LighthouseDB rev 208 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonFri Jul 06 2018 00:50:06.568 - lighthouse: LHR-A7E03A97 H: ----- SECONDARY base ACE8966F distance 2.52m -----Fri Jul 06 2018 00:50:07.434 - lighthouse: LHR-A7E03A97 H: ----- RELATIONSHIP bases 7643B68C <-> ace8966f distance 3.21m, angle 178.21 deg -----Fri Jul 06 2018 00:50:07.435 - lighthouse: Moving base ACE8966F 13mm and 0.2 deg because of relationship with 7643B68C, which is closer to the originFri Jul 06 2018 00:50:07.435 - lighthouse: Updating tilt for ACE8966F: Old= 24.99, 35.90, 3.10256e-05 <- 0.15 deg -> new= 25.13, 35.80, 3.28948e-05 result=25.13, 35.80, 3.28948e-05Fri Jul 06 2018 00:50:07.441 - lighthouse: Saved LighthouseDB rev 209 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonFri Jul 06 2018 00:50:25.107 - lighthouse: Lighthouse HMD HID device errorFri Jul 06 2018 00:50:25.286 - lighthouse: Lighthouse IMU HID device errorFri Jul 06 2018 00:50:27.300 - lighthouse: LHR-A7E03A97 H: Resetting tracking: no optical samples for 2056msFri Jul 06 2018 00:50:27.300 - lighthouse: LHR-A7E03A97 H: Dropped 786 back-facing hits during the previous tracking sessionFri Jul 06 2018 00:50:27.300 - lighthouse: Stopped tracking with universe 1507644976Fri Jul 06 2018 00:50:27.803 - lighthouse: Lighthouse IMU HID device errorFri Jul 06 2018 00:50:27.803 - lighthouse: Lighthouse Optical HID device errorFri Jul 06 2018 00:50:27.810 - lighthouse: Lighthouse IMU HID device errorFri Jul 06 2018 00:50:35.600 - 0 - entering standby Is there anything else I can do to figure out what is going wrong here? For example, is there a way to see what exact error is causing the LED on the HMD to turn red? Link to comment Share on other sites More sharing options...
roywish546 Posted July 6, 2018 Author Share Posted July 6, 2018 Hi , I have not had additional progress towards a solution and have deemed it a hardware issue and have sent it in for repairs. I brought my headset to a local Microsoft store where they kindly let me test out combinations of my cable and headset with theirs. My cables worked with their headset no problem. My headset did not work with their cables. At that point I figured it's definitely a headset issue. Link to comment Share on other sites More sharing options...
SpoonOfDoom Posted July 6, 2018 Share Posted July 6, 2018 Thanks for the update. I hope that's not the case for mine, because I think I'm just out of warranty by a couple months or so. Link to comment Share on other sites More sharing options...
roywish546 Posted July 6, 2018 Author Share Posted July 6, 2018 Ha tell me about it, mine broke at 13 month 13 days, this is a conspiracy or something :P Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.