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

Log errors - tracking problems - what do they mean and how to fix?


DUST
 Share

Recommended Posts

So way back in the beginning was this:
https://community.viveport.com/t5/Technical-Support/Basestations-go-grey-in-steamvr/m-p/9540/highlight/true#M2363

 

Since then, I have remodelled the entire room and now have a 2.5 x 2.6 metre space to play in.
All obstructions other than the cieling fan have been removed.
Minimal reflective surfaces/covered. I dont believe I have the issue from earlier anymore however playing Ultrawings is impossible due to the same issue???

The controllers lose tracking for all but a second, however there are more log entries of concern.
I think what may be the cause and Im hoping someone can point in the right direction is the basestations possibly moving themselves slightly with their own vibration? I have them mounted using the supplied mounting brackets on the wall/shelf booked end.

See next post, right assumption I think, just wrong logs I first looked at. sorry. edited.

Link to comment
Share on other sites

re ran room setup, made sure everything was tight in terms of basestation mounts.
Jumped into ultrawings and the problem of the controller losing tracking for split seconds repeatedly began.

Sat Apr 07 2018 16:51:19.975 - Setting app openvr.tool.steamvr_room_setup PID to 9956Sat Apr 07 2018 16:51:19.975 - Using existing HMD lighthouse.LHR-868B62A7Sat Apr 07 2018 16:51:29.975 - 0 - entering standbySat Apr 07 2018 16:51:29.975 - 0 - entering standbySat Apr 07 2018 16:52:31.977 - lighthouse: LHR-FFEB5B45: Updated IMU calibration: Accel bias change 0.42m/s/sSat Apr 07 2018 16:52:31.977 - lighthouse: Updating tilt for 591F485E:  Old= 39.10, -4.64, 4.63701e-06 <- 0.25 deg -> new= 38.86, -4.73, 1.33644e-06   result=38.86, -4.73, 1.33644e-06Sat Apr 07 2018 16:52:31.990 - lighthouse: Saved LighthouseDB rev 1636 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:52:55.713 - lighthouse: LHR-FFEB5B45 C: IMU went off scale.Sat Apr 07 2018 16:52:55.725 - lighthouse: LHR-F7EF5940 C: IMU went off scale.Sat Apr 07 2018 16:53:04.322 - lighthouse: Saved LighthouseDB rev 1637 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:53:05.793 - Starting SteamVR Home launch because openvr.tool.steamvr_room_setup exited after 105.818198 seconds

What does: IMU went off scale. mean?
As you can see before room setup exited that happens.

And here is the issue during ultrawings I was looking in the wrong log for first post, sorry.

Sat Apr 07 2018 16:55:12.230 - Setting app steam.app.639130 PID to 3380Sat Apr 07 2018 16:55:12.230 - Using existing HMD lighthouse.LHR-868B62A7Sat Apr 07 2018 16:55:28.296 - lighthouse: Saved LighthouseDB rev 1640 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.251 - lighthouse: Saved LighthouseDB rev 1641 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.268 - lighthouse: Saved LighthouseDB rev 1642 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.280 - lighthouse: Saved LighthouseDB rev 1643 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.291 - lighthouse: Saved LighthouseDB rev 1644 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.302 - lighthouse: Saved LighthouseDB rev 1645 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.314 - lighthouse: Saved LighthouseDB rev 1646 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.324 - lighthouse: Saved LighthouseDB rev 1647 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.334 - lighthouse: Saved LighthouseDB rev 1648 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.347 - lighthouse: Saved LighthouseDB rev 1649 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.358 - lighthouse: Saved LighthouseDB rev 1650 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.369 - lighthouse: Saved LighthouseDB rev 1651 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.380 - lighthouse: Saved LighthouseDB rev 1652 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.391 - lighthouse: Saved LighthouseDB rev 1653 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.403 - lighthouse: Saved LighthouseDB rev 1654 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.414 - lighthouse: Saved LighthouseDB rev 1655 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.425 - lighthouse: Saved LighthouseDB rev 1656 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.436 - lighthouse: Saved LighthouseDB rev 1657 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:55:37.450 - lighthouse: Saved LighthouseDB rev 1658 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSat Apr 07 2018 16:56:06.348 - AppTransition: Aborting external launch because of timeout after 0.00189209 secondsSat Apr 07 2018 16:56:06.348 - Aborting launch of ''Sat Apr 07 2018 16:57:09.740 - lighthouse: LHR-F7EF5940 C: LighthouseDirect: Optical data at time 444.208765 < filter at 444.271419Sat Apr 07 2018 16:57:47.863 - lighthouse: LHR-FFEB5B45 C: LighthouseDirect: Optical data at time 482.500246 < filter at 482.589840Sat Apr 07 2018 16:58:42.715 - lighthouse: LHR-F7EF5940 C: Resetting tracking: unlikely gravity 10.3 m/s/sSat Apr 07 2018 16:58:42.715 - lighthouse: LHR-F7EF5940 C: Dropped 5831 back-facing hits, 1 non-clustered hits during the previous tracking sessionSat Apr 07 2018 16:58:42.772 - lighthouse: LHR-F7EF5940 C: ----- BOOTSTRAPPED base 591F485E (immediate) distance 2.19m velocity 0.06m/s recorded pitch ~38.9 deg roll ~-4.7 deg -----Sat Apr 07 2018 16:58:44.438 - lighthouse: LHR-F7EF5940 C: ----- CALIBRATED base 591F485E at pitch 39.26 deg roll -4.51 deg -----Sat Apr 07 2018 16:58:45.456 - lighthouse: LHR-F7EF5940 C: ----- SECONDARY base A9C7E2D4 distance 2.52m -----Sat Apr 07 2018 16:58:46.298 - lighthouse: LHR-F7EF5940 C: Resetting tracking: IMU misalignment unreasonably large (15, 0.33, -0.67) deg sigma 1.1Sat Apr 07 2018 16:58:46.372 - lighthouse: LHR-F7EF5940 C: ----- BOOTSTRAPPED base 591F485E (immediate) distance 2.20m velocity 0.07m/s recorded pitch ~38.9 deg roll ~-4.7 deg -----Sat Apr 07 2018 16:58:48.040 - lighthouse: LHR-F7EF5940 C: ----- CALIBRATED base 591F485E at pitch 39.30 deg roll -4.52 deg -----Sat Apr 07 2018 16:58:49.055 - lighthouse: LHR-F7EF5940 C: ----- SECONDARY base A9C7E2D4 distance 2.53m -----Sat Apr 07 2018 16:58:49.525 - lighthouse: LHR-F7EF5940 C: Resetting tracking: IMU misalignment unreasonably large (14, 4.1, 4) deg sigma 1.4Sat Apr 07 2018 16:58:49.573 - lighthouse: LHR-F7EF5940 C: ----- BOOTSTRAPPED base 591F485E (immediate) distance 2.21m velocity 0.02m/s recorded pitch ~38.9 deg roll ~-4.7 deg -----Sat Apr 07 2018 16:58:51.241 - lighthouse: LHR-F7EF5940 C: ----- CALIBRATED base 591F485E at pitch 39.27 deg roll -4.54 deg -----Sat Apr 07 2018 16:58:52.256 - lighthouse: LHR-F7EF5940 C: ----- SECONDARY base A9C7E2D4 distance 2.52m -----Sat Apr 07 2018 16:58:52.916 - lighthouse: LHR-F7EF5940 C: Resetting tracking: IMU misalignment unreasonably large (15, 2.3, 2.4) deg sigma 1.3Sat Apr 07 2018 16:58:52.972 - lighthouse: LHR-F7EF5940 C: ----- BOOTSTRAPPED base 591F485E (immediate) distance 2.20m velocity 0.01m/s recorded pitch ~38.9 deg roll ~-4.7 deg -----Sat Apr 07 2018 16:58:54.640 - lighthouse: LHR-F7EF5940 C: ----- CALIBRATED base 591F485E at pitch 39.29 deg roll -4.58 deg -----Sat Apr 07 2018 16:58:55.656 - lighthouse: LHR-F7EF5940 C: ----- SECONDARY base A9C7E2D4 distance 2.51m -----Sat Apr 07 2018 16:58:56.614 - lighthouse: LHR-F7EF5940 C: ----- RELATIONSHIP bases 591F485E <-> a9c7e2d4 distance 3.37m, angle 178.29 deg -----Sat Apr 07 2018 16:59:02.141 - lighthouse: LHR-FFEB5B45 C: LighthouseDirect: Optical data at time 556.802771 < filter at 556.862885Sat Apr 07 2018 16:59:12.736 - Closing pipe Ultrawings (3380) because it was broken from the other endSat Apr 07 2018 16:59:12.736 - Process Ultrawings (3380) disconnected (Thread(0x00000197A7A30EA0/0x000)Sat Apr 07 2018 16:59:12.988 - Starting SteamVR Home launch because steam.app.639130 exited after 240.757850 seconds

what to do?

Link to comment
Share on other sites

Here is a copy of some fallout 4 gameplay logs.
You can see I have no tracking reset issue at all like ultrawings. Nothing in the room has changed so what gives?

Sun Apr 08 2018 15:58:02.874 - Setting app steam.app.611660 PID to 10140Sun Apr 08 2018 15:58:05.477 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\Fallout 4 VR\Fallout4VR.exe (VRApplication_Scene) (Args: ) 10140 Sun Apr 08 2018 15:58:05.481 - Setting app steam.app.611660 PID to 10140Sun Apr 08 2018 15:58:05.481 - Using existing HMD lighthouse.LHR-868B62A7Sun Apr 08 2018 15:58:17.245 - lighthouse: LHR-F7EF5940 C: LighthouseDirect: Optical data at time 97.196163 < filter at 97.257600Sun Apr 08 2018 15:58:22.034 - lighthouse: LHR-F7EF5940 C: LighthouseDirect: Optical data at time 101.988993 < filter at 102.048075Sun Apr 08 2018 15:58:50.689 - lighthouse: LHR-FFEB5B45: Updated IMU calibration: Accel bias change 0.53m/s/sSun Apr 08 2018 15:58:50.699 - lighthouse: Saved LighthouseDB rev 2179 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSun Apr 08 2018 15:59:02.834 - AppTransition: Aborting external launch because of timeout after 3.05176e-05 secondsSun Apr 08 2018 15:59:02.834 - Aborting launch of ''Sun Apr 08 2018 15:59:23.385 - lighthouse: LHR-F7EF5940: Updated IMU calibration: Accel bias change 0.07m/s/sSun Apr 08 2018 15:59:23.385 - lighthouse: Updating tilt for 591F485E:  Old= 127.71, -10.06, 1.56914e-05 <- 1.58 deg -> new= 129.18, -11.09, 3.46159e-06   result=129.18, -11.09, 3.46159e-06Sun Apr 08 2018 15:59:23.385 - lighthouse: Best tilt from LHR-FFEB5B45 for base 591F485E pitch 129.18 roll -11.09 score 7.19Sun Apr 08 2018 15:59:23.385 - lighthouse: Setting universe tilt from 591F485E via transform to global: pitch 129.18 deg roll -11.09 degSun Apr 08 2018 15:59:23.391 - lighthouse: Saved LighthouseDB rev 2180 to C:\Program Files (x86)\Steam\config\lighthouse\lighthousedb.jsonSun Apr 08 2018 15:59:40.211 - lighthouse: LHR-FFEB5B45 C: LighthouseDirect: Optical data at time 269.019325 < filter at 269.108971Sun Apr 08 2018 15:59:54.112 - lighthouse: LHR-FFEB5B45 C: LighthouseDirect: Optical data at time 282.919218 < filter at 283.009408Sun Apr 08 2018 16:02:27.846 - lighthouse: LHR-FFEB5B45 C: LighthouseDirect: Optical data at time 436.684390 < filter at 436.744123Sun Apr 08 2018 16:04:15.198 - lighthouse: LHR-F7EF5940 C: LighthouseDirect: Optical data at time 455.146766 < filter at 455.199493Sun Apr 08 2018 16:06:29.887 - lighthouse: LHR-868B62A7 H: IMU went off scale.Sun Apr 08 2018 16:08:20.722 - lighthouse: LHR-FFEB5B45 C: LighthouseDirect: Optical data at time 789.549002 < filter at 789.617349Sun Apr 08 2018 16:09:41.223 - lighthouse: LHR-F7EF5940 C: LighthouseDirect: Optical data at time 781.168319 < filter at 781.230661Sun Apr 08 2018 16:10:11.390 - Closing pipe Fallout4VR (10140) because it was broken from the other end




Link to comment
Share on other sites

 

Thanks for posting those logs, but let's take a step back and look at the problem from a little further away.
1. When playing Ultrawings, you experience tracking problems. Can you be more specific? Is it only your controllers or HMD also? When you say you lose tracking, do you mean to say that the controllers get "stuck", vanish or float away? How often does it happen? Does it happen in certain areas more than others?
2. If I'm understanding correctly, when you're in Fallout 4 VR, you don't experience the same issues?

3. Can you post pictures of your play area?

Thank you,

-John C

Link to comment
Share on other sites

1. When playing Ultrawings, you experience tracking problems. Can you be more specific? Is it only your controllers or HMD also? When you say you lose tracking, do you mean to say that the controllers get "stuck", vanish or float away? How often does it happen? Does it happen in certain areas more than others?

As far as I can tell whilst in game, it is only the controllers. I do not notice any HMD issues. I can look around just fine irrespective of tracking resetting on the controllers.

 

I'll try to explain, otherwise find a way to get you some video.

 

When playing ultrawings, you press the trigger on whichever controller you use dominantly to hold the flight stick.

When the tracking resets, you let go of the stick. You can "Regrab" the stick but because it happens in quick succession as per the logs, you are constantly trying to regrab the stick.

 

I have only noticed the controller drift away upwards, very quickly, before resetting to where the controller is only a number of times. Majority of the time you have just let go of the stick for no reason. (is how you mostly notice)

Sitting on the floor in a beanbag, or sitting in the middle of the room in a chair makes no difference. Doesnt matter which direction I face - see pics.

 

2. If I'm understanding correctly, when you're in Fallout 4 VR, you don't experience the same issues?

Correct. or Space Pirate trainer, the lab, holopoint, undead development, serious sam etc all fine, no issue.

3. Can you post pictures of your play area?

 

 the foam padding on the floor makes no difference. Ive tried with it and without it. The monitors on the desk and the chassis are covered as well, lights off/on make no difference.

Anything remotely reflective has been covered(including my headphones - just in case), the fan has masking tape over it and socks LOL.

Basestations are below the height of the fan, sync cable is used.

Link to comment
Share on other sites

  • 3 years later...

Not sure why he never answered this, but IMU Off Scale means that the inertial measurement unit, which measures G-forces on a rapid basis, measured a g-force that was off-scale. This causes tracking of that controller stop for a couple seconds while the whole lighthouse setup re-calculates the position of the tracked device.

Link to comment
Share on other sites

Create an account or sign in to comment

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

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...