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

Vive tracking system flaws, if swings too fast, it will lose track


WGzeyu
 Share

Recommended Posts

I am sorry that my English is not good, so I am currently using Google Translate.
Currently I am using HTC Vive, as long as I play a very fast custom song in BeatSaber (more than Ex+), I will lose track quickly, Saber will fly away directly, or stop directly.
Then I tried not to play the game, and I quickly shook the handle and still lost the tracking.
And as long as I don't wave as fast, I never lose track.

I have a video below showing this situation:

https://www.youtube.com/watch?v=AMsBWkEDXao

As you can see from the video, the right hand is faster than the left hand, and it is also easier to encounter lost tracking. After the left and right hand handles are interchanged, it is still easier for the right hand to encounter loss tracking.

I joined a Beat Saber group, most of which are in the top 1000 in the world, and the level is close to me. Most of the HTC Vive users in them have also encountered the problem of loss tracking, and even some users have lost the tracking frequency as much as I am.

This seems to be related to the speed of the swing. Those who respond faster, swinging the handle earlier in advance, are less likely to lose track, because they don't need to swing too fast to keep up with the speed of the song.
And I may not respond so fast, I can play this high-speed custom song, it depends on my hand fast. So it seems that I am more likely to encounter lost tracking?

I have tested a lot of troubleshooting operations:

  • Adjust the positioner position to ensure that each handle can be kept visible to both base stations while playing BeatSaber. I have also tried a variety of different positioners.
  • There are no reflective objects in the house except the windows, so I pull the curtains and turn off the lights.
  • BC base station interchange, after the test problem remains, also tried to switch to AB mode using wired synchronization
  • Link box replacement to connect to different USB ports on the motherboard
  • Make sure all firmware is up to date
  • The SteamVR camera has never been turned on.
  • Re-complete the room setup and leave the handle face up on the ground and wait for him to automatically calibrate
  • Disable SteamVR Power Management
  • Reinstall USB driver
  • Reinstall SteamVR
  • Reset the handle and re-install the latest firmware for the positioner
  • Tried a variety of different postures to hold the handle
  • Update the graphics driver to the latest version
  • The 2.4GHz transmit power of the wireless router is adjusted to a minimum and moved to a location 2 meters away from the linkbox and play area; there are no other Bluetooth devices in the room.

Later, I even went to four VR experience stores and tried their 7 sets of HTC Vives. All of them will happen. As long as I wave too fast, I will lose track. They are all diagonally arranged in a double base station, and there is no glare and no reflection.

I am pretty sure that this situation is related to the speed of the swinging handle, because as long as the tracking is stopped and the wave is stopped, the tracking will be fully resumed in about two seconds. As long as you keep waving, you will almost never resume tracking.

After I learned the SteamVR console address, I observed the log after each loss tracking and found that every time I just swip the handle quickly, even if there is no missing tracking, "IMU went off scale." There will be some jitter in the handle position, but the position will be restored immediately, and no tracking will be lost. This frequency of occurrence is so high that each song can appear dozens of times.
And every time I quickly wave the handle in the BeatSaber to lose track, the log will show 

Resetting tracking: unlikely gravity 10.3 m/s/s

(If you do not stop the activity at this time and continue to wave, the log will continue to output

Resetting tracking: IMU misalignment unreasonably large (11, 3.7, 10) deg sigma 1.1

)
When I don't play the game every time, use my wrist to force the handle quickly, and after the wave is lost, the log will be displayed.

Resetting tracking: rotating at 4545.0 deg/s

A complete loss tracking log when playing BS is as follows:

Thu Oct 17 2019 15:59:17.647 - lighthouse: LHR-F743DB41 C: Resetting tracking: unlikely gravity 10.3 m/s/s
Thu Oct 17 2019 15:59:17.647 - lighthouse: LHR-F743DB41 C: Dropped 4 back-facing hits during the previous tracking session
Thu Oct 17 2019 15:59:17.647 - lighthouse: LHR-F743DB41 C: Saw 4 early IMU related panics, using factory IMU cal
Thu Oct 17 2019 15:59:17.998 - lighthouse: LHR-F743DB41 C: ----- BOOTSTRAPPED base E0919D0F (immediate) distance 2.87m base pitch ~26.9 deg roll ~-9.1 deg -----
Thu Oct 17 2019 15:59:18.055 - [Status Warning Added LHR-F743DB41 ???(3)] ????????0x0008?
Thu Oct 17 2019 15:59:18.094 - lighthouse: LHR-F743DB41 C: IMU went off scale.
Thu Oct 17 2019 15:59:19.664 - lighthouse: LHR-F743DB41 C: ----- CALIBRATED base E0919D0F at pitch 9.88 deg roll -14.47 deg -----
Thu Oct 17 2019 15:59:19.728 - lighthouse: LHR-F743DB41 C: Resetting tracking: IMU misalignment unreasonably large (-8.5, 1.2, -12) deg sigma 0.9
Thu Oct 17 2019 15:59:19.728 - lighthouse: LHR-F743DB41 C: Dropped 4 back-facing hits during the previous tracking session
Thu Oct 17 2019 15:59:19.728 - lighthouse: LHR-F743DB41 C: Saw 5 early IMU related panics, using factory IMU cal
Thu Oct 17 2019 15:59:19.796 - lighthouse: LHR-F743DB41 C: ----- BOOTSTRAPPED base E0919D0F (immediate) distance 3.21m velocity 1.35m/s base pitch ~26.9 deg roll ~-9.1 deg -----
Thu Oct 17 2019 15:59:20.054 - [Status Warning Removed LHR-F743DB41 ???(3)] ????????0x0008?
Thu Oct 17 2019 15:59:21.462 - lighthouse: LHR-F743DB41 C: ----- CALIBRATED base E0919D0F at pitch 24.50 deg roll -8.42 deg -----
Thu Oct 17 2019 15:59:22.978 - lighthouse: LHR-F743DB41 C: ----- SECONDARY base 9BC41F9D distance 2.56m -----
Thu Oct 17 2019 15:59:23.207 - lighthouse: LHR-F743DB41 C: ----- RELATIONSHIP bases E0919D0F <-> 9bc41f9d distance 3.15m, angle 141.18 deg -----

So, I can be 100% sure that this is not a problem that I have myself.

Detailed system reports, and more videos (I recorded a lot of videos simultaneously in the shooting angle + game perspective, and also uploaded SteamVR logs into the video to simultaneously record a video, and I also recorded videos in 7 VR experience stores) )
I uploaded it to Google Drive, One Drive and MEGA for sharing, and the files for each share link are the same.
https://drive.google.com/open?id=1OFlTnqYSAK20GDehxcxBX1AHceoXYINe
https://1drv.ms/u/s!AjwnhNq7-wCxpAoFnpIPEJ_xP_3d?e=s8qctT
https://mega.nz/#F!VPpkhA5J!KDiXPNl2eTae9_CpNEy9Hg

I want to know how this problem actually arises? Is it a software limitation or a hardware limitation?
And can this problem be solved?

Thank you in advance, and sorry for the long post!

SteamVR-2019-10-19-AM_11_17_51.txt msinfo.nfo

Link to comment
Share on other sites

I discussed this situation with some BeatSaber players. Some of them checked the information. It seems that it is probably because the tracking system has exceeded the limit of the moving distance per unit time. Is this the case?
Others say that people have reacted to this problem since June, but it has not yet reached the present. Perhaps there are not many users who can trigger this problem, and a large number of users trust the positioning effect too much, thinking that it is their own configuration problem, so there is no feedback. Is it because of this, the technical department thinks that small problems are not worthwhile when the restrictions are revised?

 

@Synthesis

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...