ark Posted December 3, 2018 Share Posted December 3, 2018 I'm having a lot of IMU errors when making fast swings with a wired Vive pro(using the wireless adapter it gives me even more errors and bad tracking) when making fast swings up it also sometimes adjusts player hight or tilt the horizon things i've tried fresh windows 10 install fresh windows 7 install wired Vive(seems to give less errors but same tracking issues) 2 different Vive wireless kits updating all vr hardware different vive pro headset different pc different lighthouse position & angles normal steamVR and beta version covering windows and mirrors(should not relate to problem) different linkbox different games(same happens in steamVR home) different room(magnetic interference?) hard resetting controllers wired lighthouse link connection PC specs: Asus Maximus VII formula 4790k I7 Nvidia GTX Titan Xp 32gb DDR3 ram Laptop specs(second system i've tried, wired vive) GT75 Titan 8RG 8850H I7 GeForce GTX 1080 32GB DDR4 Not able to swap out the controller and lighthouses as i do not have a second pair of those The lighthouses are wallmounted with the included mounts and made sure they dont move when playing. The error only occures when making fast swings and started about 3 weeks ago Never dropped the controllers, lighthouses or both headsets. I've looked around in the other threads mentioning this error but have not found a fix yet. the log seem to point to the lighthouses when giving the IMU error (lighthouse: LHR-58C248DE/LHR-58C248DE) but since it only happens with quick controller movement maybe something is wrong with one of the controllers? This is the log when playing with the wireless adapter, wired looks almost the same, with less IMU errors but same tracking/hight adjustment problems Sun Dec 02 2018 23:42:19.656 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\Beat Saber\Beat Saber.exe (VRApplication_Scene) (Args: ) 2916 Sun Dec 02 2018 23:42:19.656 - Unable to create property container PC_700000b64 because it already existed Sun Dec 02 2018 23:42:19.656 - Unable to create property container for Beat Saber (2916). Maybe it's a reconnect? Sun Dec 02 2018 23:42:19.656 - Creating builtin app for C:\Program Files (x86)\Steam\steamapps\common\Beat Saber\Beat Saber.exe (VRApplication_Scene) Sun Dec 02 2018 23:42:19.658 - Unsetting system.generated.beat saber.exe PID because SetApplicationPid came in with a different key Sun Dec 02 2018 23:42:19.658 - Setting app steam.app.620980 PID to 2916 Sun Dec 02 2018 23:42:19.658 - Enabling legacy input for steam.app.620980 Sun Dec 02 2018 23:42:19.659 - App steam.app.620980 (vive_controller) loaded fallback binding file file:///C:/Program Files (x86)/Steam/steamapps/common/SteamVR/drivers/htc/resources/input/legacy_bindings_vive_controller.json Sun Dec 02 2018 23:42:19.659 - App steam.app.620980 (vive_pro) loaded fallback binding file file:///C:/Program Files (x86)/Steam/steamapps/common/SteamVR/resources/config/legacy_bindings_generic_hmd.json Sun Dec 02 2018 23:42:19.659 - Using existing HMD lighthouse.LHR-8CF8C123 Sun Dec 02 2018 23:42:19.659 - Received success response from vrserver connect Sun Dec 02 2018 23:42:19.660 - App key after connect message:steam.app.620980 Sun Dec 02 2018 23:42:19.660 - Enabling legacy input mode Sun Dec 02 2018 23:42:19.667 - External connection from 2916 Sun Dec 02 2018 23:42:19.667 - Received success response from vrcompositor connect Sun Dec 02 2018 23:42:19.667 - Initializing the limited version of CVRCompositorClient Sun Dec 02 2018 23:42:19.678 - Capturing Scene Focus Sun Dec 02 2018 23:42:20.256 - Disabling advanced image processing of scene textures. Only enabled on latest OSs. Sun Dec 02 2018 23:42:20.272 - Created shared texture 'Scene create D3D11, 0' 4598x2554 (1 mips) Sun Dec 02 2018 23:42:20.273 - Created shared texture 'Scene create D3D11, 0' 4598x2554 (1 mips) Sun Dec 02 2018 23:42:20.274 - Created shared texture 'Scene create D3D11, 0' 4598x2554 (1 mips) Sun Dec 02 2018 23:42:20.274 - Created shared texture 'Scene create D3D11, 1' 4598x2554 (1 mips) Sun Dec 02 2018 23:42:20.275 - Created shared texture 'Scene create D3D11, 1' 4598x2554 (1 mips) Sun Dec 02 2018 23:42:20.276 - Created shared texture 'Scene create D3D11, 1' 4598x2554 (1 mips) Sun Dec 02 2018 23:42:29.832 - lighthouse: LHR-8CF8C123: Updated IMU calibration: Accel bias change 0.05m/s/s Sun Dec 02 2018 23:42:29.832 - lighthouse: Updating tilt for D301C5D4: Old= 20.68, 4.07, 3.47157e-06 <- 0.10 deg -> new= 20.77, 4.12, 5.44135e-07 result=20.77, 4.12, 5.44135e-07 Sun Dec 02 2018 23:42:29.843 - lighthouse: Saved LighthouseDB rev 3441 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.json Sun Dec 02 2018 23:42:47.525 - lighthouse: LHR-58C248DE: Updated IMU calibration: Accel bias change 0.04m/s/s Sun Dec 02 2018 23:42:47.538 - lighthouse: Saved LighthouseDB rev 3442 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.json Sun Dec 02 2018 23:42:49.825 - PropertyContainer: High lock acquisition counters: sp:100001 yd:1 re:0 Sun Dec 02 2018 23:42:59.163 - lighthouse: LHR-143F6AE1: Updated IMU calibration: Accel bias change 0.04m/s/s Sun Dec 02 2018 23:42:59.163 - lighthouse: Updating tilt for D301C5D4: Old= 20.77, 4.12, 5.44135e-07 <- 0.47 deg -> new= 21.20, 3.94, 8.05077e-07 result=21.20, 3.94, 8.05077e-07 Sun Dec 02 2018 23:42:59.169 - lighthouse: Saved LighthouseDB rev 3443 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.json Sun Dec 02 2018 23:43:14.727 - PropertyContainer: High lock acquisition counters: sp:100001 yd:1 re:0 Sun Dec 02 2018 23:43:19.080 - AppTransition: Aborting external launch because of timeout after 0.00811768 seconds Sun Dec 02 2018 23:43:19.080 - Aborting launch of 'steam.app.620980' Sun Dec 02 2018 23:43:43.339 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:43:44.078 - lighthouse: LHR-143F6AE1 C: IMU went off scale. Sun Dec 02 2018 23:43:46.122 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:43:48.130 - lighthouse: LHR-143F6AE1 C: IMU went off scale. Sun Dec 02 2018 23:43:50.620 - lighthouse: LHR-143F6AE1 C: IMU went off scale. Sun Dec 02 2018 23:43:51.255 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:44:01.503 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:44:12.553 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:44:26.317 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:44:41.298 - lighthouse: LHR-143F6AE1 C: drop base S-1 s/n 2B261340 u20003 Sun Dec 02 2018 23:44:42.852 - lighthouse: LHR-143F6AE1 C: base S-1 s/n 00000000 u20007 Sun Dec 02 2018 23:44:52.471 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:44:52.475 - lighthouse: LHR-143F6AE1 C: IMU went off scale. Sun Dec 02 2018 23:44:56.574 - lighthouse: LHR-143F6AE1 C: IMU went off scale. Sun Dec 02 2018 23:44:56.574 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:45:02.189 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:45:03.240 - lighthouse: LHR-143F6AE1 C: IMU went off scale. Sun Dec 02 2018 23:45:05.551 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:45:06.867 - lighthouse: LHR-143F6AE1 C: IMU went off scale. Sun Dec 02 2018 23:45:10.587 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:45:10.866 - lighthouse: LHR-143F6AE1 C: IMU went off scale. Sun Dec 02 2018 23:45:12.548 - PropertyContainer: High lock acquisition counters: sp:100001 yd:1 re:0 Sun Dec 02 2018 23:45:12.758 - Adding focus flag SystemBehaviorFlag_SystemButtonDown Sun Dec 02 2018 23:45:12.758 - Detected screenshot action, telling Dashboard to take a screenshot Sun Dec 02 2018 23:45:12.946 - Removing focus flag SystemBehaviorFlag_SystemButtonDown Sun Dec 02 2018 23:45:13.703 - Adding focus flag SystemBehaviorFlag_SystemButtonDown Sun Dec 02 2018 23:45:13.703 - Detected screenshot action, telling Dashboard to take a screenshot Sun Dec 02 2018 23:45:13.781 - Removing focus flag SystemBehaviorFlag_SystemButtonDown Sun Dec 02 2018 23:45:14.369 - Adding focus flag SystemBehaviorFlag_SystemButtonDown Sun Dec 02 2018 23:45:14.369 - Detected screenshot action, telling Dashboard to take a screenshot Sun Dec 02 2018 23:45:14.458 - Removing focus flag SystemBehaviorFlag_SystemButtonDown Sun Dec 02 2018 23:45:15.435 - Adding focus flag SystemBehaviorFlag_SystemButtonDown Sun Dec 02 2018 23:45:15.436 - Detected screenshot action, telling Dashboard to take a screenshot Sun Dec 02 2018 23:45:15.480 - Removing focus flag SystemBehaviorFlag_SystemButtonDown Sun Dec 02 2018 23:45:15.560 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:45:20.913 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:45:30.964 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:45:35.698 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:45:37.270 - Adding focus flag SystemBehaviorFlag_SystemButtonDown Sun Dec 02 2018 23:45:37.270 - Detected screenshot action, telling Dashboard to take a screenshot Sun Dec 02 2018 23:45:37.336 - Removing focus flag SystemBehaviorFlag_SystemButtonDown Sun Dec 02 2018 23:45:37.646 - Adding focus flag SystemBehaviorFlag_SystemButtonDown Sun Dec 02 2018 23:45:37.646 - Detected screenshot action, telling Dashboard to take a screenshot Sun Dec 02 2018 23:45:37.680 - Removing focus flag SystemBehaviorFlag_SystemButtonDown Sun Dec 02 2018 23:45:37.773 - lighthouse: LHR-143F6AE1 C: IMU went off scale. Sun Dec 02 2018 23:45:41.971 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:45:49.194 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:45:52.539 - lighthouse: LHR-143F6AE1 C: IMU went off scale. Sun Dec 02 2018 23:45:54.874 - PropertyContainer: High lock acquisition counters: sp:100001 yd:1 re:0 Sun Dec 02 2018 23:45:56.483 - lighthouse: LHR-58C248DE C: IMU went off scale. Sun Dec 02 2018 23:45:57.483 - lighthouse: LHR-143F6AE1 C: IMU went off scale. Sun Dec 02 2018 23:46:00.929 - lighthouse: LHR-58C248DE C: IMU went off scale. Link to comment Share on other sites More sharing options...
Synthesis Posted December 3, 2018 Share Posted December 3, 2018 Does it seem like it only happens with a single controller? Try using only one at a time and testing to see if they're both showing the same errors and choppy tracking of if it's just one of them. If it's just one, it's probably the controller and we can set up an RMA for that.Thanks! -John C Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.