Jump to content
Happy Holidays! Limited Staff Responses: 1/20 - 1/31 ×

Headset Track Loss


nehumanuscrede

Recommended Posts

This one has got me stumped.

 

Upon the launch of any VR title, the application will work as expected for 2-3 minutes before the headset will " white out " and go into track loss according to the Steam VR monitor.   My fix for this is to shut down Steam VR ( which will also shut down the running VR title ) then, simply relaunch the title. 

 

After the second launch of the title in question, the system will perform flawlessly for as long as I wish to play it. ( have gone several hours without a single hiccup afterwards )

 

The issue only manifests itself during the initial launch and is reproducable every time the VR system is fired up for the first time, so this puzzles the hell out of me. 

 

 

Now, this may just be a coincidence, but after reviewing the vrserver logs, the loss of track typically happens within 1-3 minutes after the system updates the lighthousedb.json file.  Eg: 

 

Wed Jan 04 2017 18:34:50.934 - lighthouse: Saved LighthouseDB rev 869 to D:\Steam\config\lighthouse\lighthousedb.json
Wed Jan 04 2017 18:35:07.258 - lighthouse: LHR-5F8DBC09 H: SendOnPoseChange took 0.805801ms
Wed Jan 04 2017 18:35:24.100 - lighthouse: LHR-5F8DBC09 H: SendOnPoseChange took 0.552742ms
Wed Jan 04 2017 18:36:00.967 - lighthouse: LHR-5F8DBC09 H: Resetting tracking: no optical samples for 2015ms
Wed Jan 04 2017 18:36:00.967 - lighthouse: Stopped tracking with universe 1480121868
Wed Jan 04 2017 18:36:06.067 - lighthouse: LHR-5F8DBC09 H: No IMU data in past 5 seconds
Wed Jan 04 2017 18:36:06.067 - lighthouse: LHR-5F8DBC09 H: No optical frames in past 5 seconds

 

 

At which point I have to shutdown SteamVR and reset the entire thing.  Afterwards, however, it runs just fine. 

 

The only other oddities I've noted in the logs that I would potentially consider strange are:

 

Sat Jan 07 2017 14:15:14.873 - lighthouse: LHR-5F8DBC09 H: Trying to start tracking from base 446B0378: Available samples not sufficient for booting (hits: 2+1)

 

and


Sat Jan 07 2017 15:23:40.738 - lighthouse: LHR-5F8DBC09 H: Dropped 2977 back-facing hits, 10 non-clustered hits during the previous tracking session

 

 

Thoughts ?

Link to comment
Share on other sites

  • Replies 25
  • Created
  • Last Reply

  did you guys find a fix for this? I've just truned my Vive on again for the first time since being away over the holidays, updated both of my base station's & headset's firmwareand started seeing this issue too ("This headset is connected but not tracking" ~ 1-3 minutes after SteamVR boots up, with "Resetting tracking: no optical samples for 2022ms" in the vrserver logs).

 

I've tried the SteamVR beta, every combination of uninstall / reinstall of Steam, unplug / replug all cabling, machine reboots, disabled MS power management, removed all Steam USB Devices etc.  Still no luck. 

 

Would be great to get this fixed, have a very expensive brick sitting on my desk for the moment :(

 

Cheers,

D

 

PS: Here's my full vrserver.txt (can send full System Report too):

 

vrserver.txt Sat Jan 14 2017 15:01:43.350Sat Jan 14 2017 15:01:43.350 - ================================================================================================Sat Jan 14 2017 15:01:43.350 - ================================================================================================Sat Jan 14 2017 15:01:43.352 - VR server (v0) starting up with config=C:\Program Files (x86)\Steam\configSat Jan 14 2017 15:01:43.357 - [settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\resources\settings\default.vrsettingsSat Jan 14 2017 15:01:43.358 - [settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\resources\settings\default.vrsettingsSat Jan 14 2017 15:01:43.359 - [settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\null\resources\settings\default.vrsettingsSat Jan 14 2017 15:01:43.360 - [settings] Load Json Settings from C:\Program Files (x86)\Steam\config\steamvr.vrsettingsSat Jan 14 2017 15:01:43.360 - Unable to read app config file from C:\Program Files (x86)\Steam\config\appconfig.json. No applications will be availableSat Jan 14 2017 15:01:43.364 - Load Json firmware manifest from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\firmware\manifest.vrfirmwareSat Jan 14 2017 15:01:43.438 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\tools\bin\win32\vrmonitor.exe (VRApplication_VRMonitor) (Args: ) 8704 Sat Jan 14 2017 15:01:43.438 - Setting app system.generated.vrmonitor.exe PID to 8704Sat Jan 14 2017 15:01:43.454 - lighthouse: Attached HID Devices:Sat Jan 14 2017 15:01:43.454 - lighthouse:     28DE, 2101: s/n 6588B6B8AC: Watchman Dongle (max-input-report -1)Sat Jan 14 2017 15:01:43.454 - lighthouse:     28DE, 2101: s/n A04CA63F4F: Watchman Dongle (max-input-report -1)Sat Jan 14 2017 15:01:43.454 - lighthouse:     28DE, 2000: s/n LHR-858F751D: HID (max-input-report 0)Sat Jan 14 2017 15:01:43.455 - lighthouse:     28DE, 2000: s/n LHR-858F751D: Lighthouse FPGA RX (max-input-report 1)Sat Jan 14 2017 15:01:43.455 - lighthouse:     BB4, 2C87: s/n 206C3959534D: HTC Vive (max-input-report -1)Sat Jan 14 2017 15:01:43.455 - lighthouse:     D8C, 12: s/n \\?\hid#vid_0d8c&pid_0012&mi_03#9&10ff662b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}: USB Audio Device (max-input-report 3)Sat Jan 14 2017 15:01:43.456 - lighthouse: HID opened: VID 28de PID 2000 serial LHR-858F751D seq 1 | if 0Sat Jan 14 2017 15:01:43.457 - lighthouse: Attempting HID Open IMU: 6588B6B8ACSat Jan 14 2017 15:01:43.460 - lighthouse: HID opened: VID 28de PID 2101 serial 6588B6B8AC seq 1 | if -1Sat Jan 14 2017 15:01:43.460 - lighthouse: Lighthouse IMU HID openedSat Jan 14 2017 15:01:43.478 - lighthouse: LHR-858F751D: Read config of 3497 bytes from [vid:28de, pid:2000] (LHR-858F751D) and inflated to 16640 bytesSat Jan 14 2017 15:01:43.480 - lighthouse: HID opened: VID 28de PID 2000 serial LHR-858F751D seq 1 | if 0Sat Jan 14 2017 15:01:43.483 - lighthouse: HMD Model: HTC ViveSat Jan 14 2017 15:01:43.483 - lighthouse: Unable to read Lighthouse DB from file C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Jan 14 2017 15:01:43.484 - lighthouse: LHR-858F751D H: Source: tdm disambiguator -- Preferred basestation 00000000Sat Jan 14 2017 15:01:43.484 - lighthouse: Enumerating displays...Sat Jan 14 2017 15:01:43.492 - lighthouse: MONITOR\ACI28A3\{4d36e96e-e325-11ce-bfc1-08002be10318}\0002: 0, 0, 3840, 2160Sat Jan 14 2017 15:01:43.493 - lighthouse: <hidden>: 0, 0, 2160, 1200Sat Jan 14 2017 15:01:43.493 - lighthouse: Loaded Chromatic Correction Factors RED (-0.024, 0.050, -0.028, -0.006) BLUE (0.025, -0.058, 0.037, 0.008) x 0.750Sat Jan 14 2017 15:01:43.493 - lighthouse: LHR-858F751D: Attached device ID not set.  No controller input available.Sat Jan 14 2017 15:01:43.666 - lighthouse: Attempting HID Open IMU: A04CA63F4FSat Jan 14 2017 15:01:43.669 - lighthouse: HID opened: VID 28de PID 2101 serial A04CA63F4F seq 1 | if -1Sat Jan 14 2017 15:01:43.669 - lighthouse: Lighthouse IMU HID openedSat Jan 14 2017 15:01:43.878 - lighthouse: TrackedCamera: OpenCamera()Sat Jan 14 2017 15:01:43.878 - lighthouse: TrackedCamera: Expecting drivers at 'C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\bin\win64'Sat Jan 14 2017 15:01:43.880 - lighthouse: Attempting HID Open IMU: LHR-858F751DSat Jan 14 2017 15:01:43.881 - lighthouse: HID opened: VID 28de PID 2000 serial LHR-858F751D seq 1 | if 0Sat Jan 14 2017 15:01:43.881 - lighthouse: Lighthouse IMU HID openedSat Jan 14 2017 15:01:43.882 - lighthouse: LHR-858F751D: Firmware Version 1462663157 steamservices@firmware-win32 2016-05-08 FPGA 1.6/0/0Sat Jan 14 2017 15:01:43.882 - lighthouse: LHR-858F751D: Successfully fetched gyro/accelerometer range modes from the device. GyroRangeMode:1 AccelRangeMode:1Sat Jan 14 2017 15:01:43.883 - lighthouse: Attempting HID Open Optical: LHR-858F751DSat Jan 14 2017 15:01:43.884 - lighthouse: HID opened: VID 28de PID 2000 serial LHR-858F751D seq 2 | if 1Sat Jan 14 2017 15:01:43.884 - lighthouse: Lighthouse Optical HID openedSat Jan 14 2017 15:01:43.925 - lighthouse: TrackedCamera: Found Camera at USB VID:0BB4, USB PID:2C87Sat Jan 14 2017 15:01:43.941 - lighthouse: InitTrackedCamera(): Opened tracked camera on (LHR-858F751D). Compatibility Mode:0. Version: 02.05.017 Date: 2016.Jul.19Sat Jan 14 2017 15:01:43.941 - lighthouse: InitTrackedCamera(): Disabling camera on (LHR-858F751D) due to vr settings. Camera services restricted.Sat Jan 14 2017 15:01:43.941 -   driver lighthouse implements interfaces IVRSettings_002 ITrackedDeviceServerDriver_004 IVRDisplayComponent_002 IVRDriverDirectModeComponent_002 IVRControllerComponent_001 IVRCameraComponent_002 IServerTrackedDeviceProvider_003 IClientTrackedDeviceProvider_005 Sat Jan 14 2017 15:01:43.941 - Loaded server driver lighthouse (IServerTrackedDeviceProvider_003) from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\bin\win64\driver_lighthouse.dllSat Jan 14 2017 15:01:43.941 - Active HMD set to lighthouse.LHR-858F751DSat Jan 14 2017 15:01:43.941 - lighthouse: RecommendedRenderTargetSize: 1512, 1680 (viewport 1080, 1200 scaled by 1.40)Sat Jan 14 2017 15:01:43.941 - Guessing frequency of current display mode because SDL failed usSat Jan 14 2017 15:01:43.941 - lighthouse: Returning NotYetAvailable for EdidVendorIDSat Jan 14 2017 15:01:43.942 - lighthouse: Attempting HID Open HMD: Sat Jan 14 2017 15:01:43.942 - Processing message VRMsg_Connect from vrmonitor (8704) took 0.504 secondsSat Jan 14 2017 15:01:43.942 - DXGI thread failed to get SDL display indexSat Jan 14 2017 15:01:43.943 - lighthouse: HID opened: VID 0bb4 PID 2c87 serial 206C3959534D seq 1 | if -1Sat Jan 14 2017 15:01:43.943 - lighthouse: Lighthouse HMD HID openedSat Jan 14 2017 15:01:43.943 - lighthouse: HmdDeviceConnect( 53794, 43521, 3146256, 19 )Sat Jan 14 2017 15:01:43.943 - lighthouse: HID opened: VID 28de PID 2000 serial LHR-858F751D seq 1 | if 0Sat Jan 14 2017 15:01:43.953 - lighthouse: LHR-858F751D H: basestation transmission profile (ootx) selected, max basestations: 2Sat Jan 14 2017 15:01:43.958 - lighthouse: Reading C:\Program Files (x86)\Steam\config\lighthouse\lhr-858f751d\userdata\Green_46GA164E001632_mura_analyzes.mc from deviceSat Jan 14 2017 15:01:44.081 - lighthouse: LHR-858F751D H: tdm sync acquiredSat Jan 14 2017 15:01:44.086 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win32\vrcompositor.exe (VRApplication_Background) (Args: ) 8228 Sat Jan 14 2017 15:01:44.086 - Setting app system.generated.vrcompositor.exe PID to 8228Sat Jan 14 2017 15:01:44.086 - Using existing HMD lighthouse.LHR-858F751DSat Jan 14 2017 15:01:44.095 - lighthouse: Returning EdidVendorID D222Sat Jan 14 2017 15:01:46.602 - lighthouse: Returning EdidVendorID D222Sat Jan 14 2017 15:01:46.602 - [settings] Save Json Settings to C:\Program Files (x86)\Steam\config\steamvr.vrsettingsSat Jan 14 2017 15:01:46.810 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\tools\bin\win32\vrdashboard.exe (VRApplication_Overlay) (Args: ) 12692 Sat Jan 14 2017 15:01:46.810 - Setting app system.generated.vrdashboard.exe PID to 12692Sat Jan 14 2017 15:01:46.810 - VRDashboard watchdog enabled for pid:12692Sat Jan 14 2017 15:01:46.810 - Using existing HMD lighthouse.LHR-858F751DSat Jan 14 2017 15:01:46.813 - lighthouse: Returning EdidVendorID D222Sat Jan 14 2017 15:01:47.072 - lighthouse:  Base C6957546 recordedSat Jan 14 2017 15:01:47.072 - lighthouse:  Base 517E63B2 recordedSat Jan 14 2017 15:01:47.078 - lighthouse: Saved LighthouseDB rev 1 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Jan 14 2017 15:01:47.391 - New Connect message from C:\Program Files (x86)\Steam\steam.exe (VRApplication_Overlay) (Args: ) 10804 Sat Jan 14 2017 15:01:47.391 - Setting app system.generated.steam.exe PID to 10804Sat Jan 14 2017 15:01:47.391 - Using existing HMD lighthouse.LHR-858F751DSat Jan 14 2017 15:01:47.395 - lighthouse: Returning EdidVendorID D222Sat Jan 14 2017 15:01:47.404 - C:\Program Files (x86)\Steam\config\steamapps.vrmanifest - No applications in manifestSat Jan 14 2017 15:01:47.638 - lighthouse: LHR-858F751D H: ----- BOOTSTRAPPED base C6957546 (closest) distance 2.24m velocity 0.01m/s base pitch ~29.9 deg roll ~0.0 deg -----Sat Jan 14 2017 15:01:49.380 - lighthouse: LHR-858F751D H: ----- CALIBRATED base C6957546 at pitch 29.19 deg roll 1.01 deg -----Sat Jan 14 2017 15:01:49.380 - lighthouse: Updating tilt for C6957546.1. Old= 0.00, 0.00, 39.4784 <- 29.20 deg -> new= 29.19, 1.01, 3.81921e-006   result=29.19, 1.01, 3.81921e-006Sat Jan 14 2017 15:01:49.380 - lighthouse: BootstrapFinished setting tilt base to C6957546Sat Jan 14 2017 15:01:49.380 - lighthouse: Creating new universe 1484359303 because there were no compatible existing universesSat Jan 14 2017 15:01:49.380 - lighthouse: Setting C6957546 as the origin of universe 1484359303Sat Jan 14 2017 15:01:49.380 - lighthouse: Setting tilt from C6957546 as new origin: pitch 29.19 deg roll 1.01 degSat Jan 14 2017 15:01:49.390 - lighthouse: Saved LighthouseDB rev 2 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Jan 14 2017 15:01:49.713 - Setting app openvr.tool.steamvr_room_setup PID to 12772Sat Jan 14 2017 15:01:49.713 - Processing message VRMsg_LaunchApplication from vrmonitor (8704) took 0.0573 secondsSat Jan 14 2017 15:01:50.404 - lighthouse: LHR-858F751D H: ----- SECONDARY base 517E63B2 distance 2.36m -----Sat Jan 14 2017 15:01:50.605 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\tools\steamvr_room_setup\win64\steamvr_room_setup.exe (VRApplication_Scene) (Args: -popupwindow) 12772 Sat Jan 14 2017 15:01:50.605 - Setting app openvr.tool.steamvr_room_setup PID to 12772Sat Jan 14 2017 15:01:50.605 - Using existing HMD lighthouse.LHR-858F751DSat Jan 14 2017 15:01:50.608 - lighthouse: Returning EdidVendorID D222Sat Jan 14 2017 15:01:50.763 - lighthouse: LHR-858F751D H: ----- RELATIONSHIP bases C6957546 <-> 517e63b2 distance 2.77m, angle 170.00 deg -----Sat Jan 14 2017 15:01:50.763 - lighthouse: Base 517E63B2 is learning to get to global from C6957546 because of direct observationSat Jan 14 2017 15:01:50.763 - lighthouse: Updating tilt for 517E63B2.1. Old= 0.00, 0.00, 39.4784 <- 30.04 deg -> new= 29.96, -2.18, 3.71737e-005   result=29.96, -2.18, 3.71737e-005Sat Jan 14 2017 15:01:50.771 - lighthouse: Saved LighthouseDB rev 3 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Jan 14 2017 15:01:52.639 - lighthouse: LHR-858F751D H: SendOnPoseChange took 0.898729msSat Jan 14 2017 15:02:03.638 - lighthouse: 6588B6B8AC: Successfully fetched gyro/accelerometer range modes from the device. GyroRangeMode:3 AccelRangeMode:2Sat Jan 14 2017 15:02:03.659 - lighthouse: LHR-FF67B943: Connected to receiver 6588B6B8ACSat Jan 14 2017 15:02:03.671 - lighthouse: 6588B6B8AC: Firmware Version 1465809478 htcvrsoftware@firmware-win32 2016-06-13 FPGA 1.6/0/0 VRC 1465809477 Radio 1466630404Sat Jan 14 2017 15:02:04.079 - lighthouse: 6588B6B8AC: Read config of 1938 bytes from [vid:28de, pid:2101] (6588B6B8AC) and inflated to 8207 bytesSat Jan 14 2017 15:02:04.081 - lighthouse: LHR-FF67B943 C: Source: tdm disambiguator -- Preferred basestation 00000000Sat Jan 14 2017 15:02:04.154 - lighthouse: A04CA63F4F: Successfully fetched gyro/accelerometer range modes from the device. GyroRangeMode:3 AccelRangeMode:2Sat Jan 14 2017 15:02:04.199 - lighthouse: Returning EdidVendorID D222Sat Jan 14 2017 15:02:04.206 - lighthouse: LHR-FF67FB46: Connected to receiver A04CA63F4FSat Jan 14 2017 15:02:04.218 - lighthouse: A04CA63F4F: Firmware Version 1465809478 htcvrsoftware@firmware-win32 2016-06-13 FPGA 1.6/0/0 VRC 1465809477 Radio 1466630404Sat Jan 14 2017 15:02:04.494 - lighthouse: LHR-FF67B943 C: basestation transmission profile (ootx) selected, max basestations: 2Sat Jan 14 2017 15:02:04.620 - lighthouse: LHR-FF67B943 C: tdm sync acquiredSat Jan 14 2017 15:02:04.646 - lighthouse: A04CA63F4F: Read config of 1930 bytes from [vid:28de, pid:2101] (A04CA63F4F) and inflated to 8207 bytesSat Jan 14 2017 15:02:04.648 - lighthouse: LHR-FF67FB46 C: Source: tdm disambiguator -- Preferred basestation 00000000Sat Jan 14 2017 15:02:05.061 - lighthouse: LHR-FF67FB46 C: basestation transmission profile (ootx) selected, max basestations: 2Sat Jan 14 2017 15:02:05.188 - lighthouse: LHR-FF67FB46 C: tdm sync acquiredSat Jan 14 2017 15:02:07.675 - lighthouse: LHR-FF67B943 C: ----- BOOTSTRAPPED base C6957546 (immediate) distance 1.75m velocity 0.77m/s recorded pitch ~29.2 deg roll ~1.0 deg -----Sat Jan 14 2017 15:02:07.772 - lighthouse: LHR-FF67FB46 C: ----- BOOTSTRAPPED base C6957546 (immediate) distance 1.98m velocity 0.57m/s recorded pitch ~29.2 deg roll ~1.0 deg -----Sat Jan 14 2017 15:02:09.338 - lighthouse: LHR-FF67B943 C: ----- CALIBRATED base C6957546 at pitch 29.01 deg roll 0.83 deg -----Sat Jan 14 2017 15:02:09.338 - lighthouse: Updating tilt for C6957546.1. Old= 29.19, 1.01, 3.81921e-006 <- 0.25 deg -> new= 29.01, 0.83, 1.73123e-006   result=29.01, 0.83, 1.73123e-006Sat Jan 14 2017 15:02:09.437 - lighthouse: LHR-FF67FB46 C: ----- CALIBRATED base C6957546 at pitch 29.09 deg roll 1.29 deg -----Sat Jan 14 2017 15:02:09.437 - lighthouse: Updating tilt for C6957546.1. Old= 29.01, 0.83, 1.73123e-006 <- 0.45 deg -> new= 29.09, 1.29, 1.59531e-006   result=29.09, 1.29, 1.59531e-006Sat Jan 14 2017 15:02:10.755 - lighthouse: LHR-FF67B943 C: ----- SECONDARY base 517E63B2 distance 2.48m -----Sat Jan 14 2017 15:02:10.957 - lighthouse: LHR-FF67FB46 C: ----- SECONDARY base 517E63B2 distance 2.64m -----Sat Jan 14 2017 15:02:11.186 - lighthouse: LHR-FF67B943 C: ----- RELATIONSHIP bases C6957546 <-> 517e63b2 distance 2.80m, angle 169.61 deg -----Sat Jan 14 2017 15:02:11.322 - lighthouse: LHR-FF67FB46 C: ----- RELATIONSHIP bases C6957546 <-> 517e63b2 distance 2.82m, angle 169.57 deg -----Sat Jan 14 2017 15:02:11.345 - lighthouse: Reading C:\Program Files (x86)\Steam\config\lighthouse\lhr-858f751d\userdata\Green_46HA164E007250_mura_analyzes.mc from deviceSat Jan 14 2017 15:02:11.684 - 0 - entering standbySat Jan 14 2017 15:02:25.432 - 0 - leaving standbySat Jan 14 2017 15:02:44.212 - lighthouse: LHR-FF67FB46 C: Resetting tracking: no optical samples for 2022msSat Jan 14 2017 15:02:44.212 - lighthouse: LHR-FF67FB46 C: Dropped 315 back-facing hits during the previous tracking sessionSat Jan 14 2017 15:02:44.214 - lighthouse: LHR-FF67B943 C: Resetting tracking: no optical samples for 2041msSat Jan 14 2017 15:02:44.214 - lighthouse: LHR-FF67B943 C: Dropped 689 back-facing hits, 1 non-clustered hits during the previous tracking sessionSat Jan 14 2017 15:02:44.216 - lighthouse: LHR-858F751D H: Resetting tracking: no optical samples for 2016msSat Jan 14 2017 15:02:44.216 - lighthouse: LHR-858F751D H: Dropped 2480 back-facing hits during the previous tracking sessionSat Jan 14 2017 15:02:44.216 - lighthouse: Stopped tracking with universe 1484359303Sat Jan 14 2017 15:02:49.330 - lighthouse: LHR-FF67FB46 C: No IMU data in past 5 secondsSat Jan 14 2017 15:02:49.330 - lighthouse: LHR-FF67FB46 C: No optical frames in past 5 secondsSat Jan 14 2017 15:02:49.332 - lighthouse: LHR-FF67B943 C: No IMU data in past 5 secondsSat Jan 14 2017 15:02:49.332 - lighthouse: LHR-FF67B943 C: No optical frames in past 5 secondsSat Jan 14 2017 15:02:49.335 - lighthouse: LHR-858F751D H: No IMU data in past 5 secondsSat Jan 14 2017 15:02:49.335 - lighthouse: LHR-858F751D H: No optical frames in past 5 secondsSat Jan 14 2017 15:02:57.450 - 0 - entering standbySat Jan 14 2017 15:03:49.439 - lighthouse: Returning EdidVendorID D222
Link to comment
Share on other sites

As of this writing, the issue at hand is still present. 

 

At first, I thought it might be a reflective surfaces issue within my office as there are quite a bit of them.  However, considering the problem resolves with a simple relaunch of SteamVR, I'm disinclined to consider that as a possible variable. 

 

It also gives me pause to consider it may be a hardware issue for the same reasons. 

 

As a workaround for you, when you see the track-loss kick in, try shutting down SteamVR and simply relaunching the title you're trying to play.  Mine only does it initially and the relaunch will allow me to play until I get tired and shut it off without further issue. 

 

Next on the list is the reinstall of Steam itself.  Will let you know if anything comes of it. 

 

Link to comment
Share on other sites

New Vive owner here, exact same issue - loss of headset tracking randomly and frequiently.  Sometimes it will work flawlessly for several hours and other times will go to the white screen in the headset and indicate a loss of headset tracking on the VR window.  Have adjusted/moved the base stations, tried different USB ports (not sure if the USB even comes into play with this issue).

 

Please help track down this issue.

Link to comment
Share on other sites

Ok, update.

 

Reinstalling Steam sounds so simple.  Until you have to take into account the move of nearly half a terabyte of game data :|  THAT took a bit of time, but I got it done.

 

Pulled Steam off the system and reinstalled it.  No good.  The problem showed up less than a minute after launching a title and, like always, a reboot of SteamVR and relaunch of the title seems to fix it. 

 

Next on the list, I will be purchasing either light stands or floor poles to mount the room sensors on.  The idea is a better angle / position that I can adjust vs the wall mounts.  This may take some time as I don't have a local camera store that will carry such things so, to my favorite online camera store I go ! ( B&H )

 

Will let you know if it resolves anything or not. 

Link to comment
Share on other sites

Update.

 

I pulled one of the lighthouse sensors off of it's wall mount and stuck it on top of one of my camera tripods for testing purposes.  The tripod sits on the desk to my left and elevates the base station to approximately seven feet.  This effectively moved the base-stations closer to one another by about five feet. 

 

Since this move,  I have not seen a white-out condition within the headset. 

 

Tested it last night and this morning.  Will let you know if anything changes or if the system stays stable. 

 

What is interesting to note is even in the original mounted positions, the base stations appeared to be operating normally.  Both Green sync lights were active and no obvious issues were seen. 

 

 

Link to comment
Share on other sites

I have had some success lately as well.  I did several things (see below) and am not sure if one of those things was the single thing that fixed the issue or if is a combination.

 

1.  I slightly tilted one of the base stations down.

2.  I reset my room scale play area.

3. I have found that the cords must be plugged into the computer BEFORE starting the comuter.  If I plug the system into the computer after startup it behaves very flaky.

 

So far everything is working flawlessly!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...