search

pushrax / OpenVR-SpaceCalibrator

Use tracked VR devices from one company with any other.
MIT License
669 stars 111 forks source link

Big feature for MixedVR #85

Closed monstermac77 closed 2 years ago

monstermac77 commented 2 years ago

@bdunderscore has resolved #30, which would help a very large community on https://www.reddit.com/r/MixedVR/ who is using HP Reverb G2s or Quests along with Index controllers. If not merged, I believe @bdunderscore should widely publicize this fork on /r/MixedVR and other channels so the larger VR community is aware.

pushrax commented 2 years ago

I talked with @bdunderscore about this recently. They will be handling some maintainership of this project going forward, which involves merging this change.

monstermac77 commented 2 years ago

Fantastic. I also see now that they've already created a pull request, so I'll close this. Only thing I'd push for is once the merge is made that this be widely publicized. I'm not as active in the Mixed VR community as I once was so hopefully someone else will do so.

bdunderscore commented 2 years ago

I've got a couple more things I want to try out over the next couple weeks to make things a bit smoother before I merge everything in and call it settled. In no particular order:

  1. Improve correction of small offsets. Currently my branch only applies corrections if the new solution is significantly better (4x better by estimated RMS error), and does so quickly enough that it's noticeable. For larger offsets the rapid correction is desirable, but for small offsets it might be better to apply the corrections earlier, but spread the correction over a longer period in time. This requires some more changes to the driver to handle multiple correction speeds.
  2. Provide a faster correction when your playspace jumps based on assuming the relative position of the HMD and tracker does not change.
  3. Provide more useful debug output - in particular, log when corrections are made, instead of just giving a point-in-time view into what it's thinking about. This will be needed to debug 1 and 2 above.
  4. Look into other options for hiding the tracker data from applications - can we emulate the tracker actually being turned off?