OpenVR-SpaceOverride aligns SLAM-tracked headsets (Pico, Galaxy XR and similar) with lighthouse-tracked devices, without the drift that plagues traditional playspace calibration. Instead of computing a one-time offset between two tracking systems that slowly slide apart, it uses a Vive tracker rigidly mounted to the headset: after calibration, the driver stops using the headset's own pose and builds it from the tracker instead.
This puts the headset and all your other lighthouse devices on the same tracking system, so there's nothing left to drift against. The SLAM tracking is still there underneath, you just get proper alignment on top of it.
Note
If you find bugs or issues, let me know over e-mail at nyabsi@sovellus.cc I will be responding to you when I have time. This software will receive updates on irregular basis but each update is guaranteed to improve the software in a way or another, thanks for using it even on it's current state.
Tip
OpenVR-SpaceOverride is not OpenVR-SpaceCalibrator nor a fork, it uses a completely novel technique starting from v9. Older vesions had code used from space cal to workaround a technical limitation which has been resolved.
- Lighthouse system (or other equivalent)
- Rigid Tracker (i.e., Vive Tracker 3.0 or equivalent)
- Headset with SLAM or other positional tracking system
| Streamer | Status | Notes |
|---|---|---|
| PICO Connect | ✅ Works | |
| Virtual Desktop | ✅ Works | |
| ALVR | ✅ Works | |
| Meta Quest Link | Unconfirmed, let me know, email: nyabsi@sovellus.cc | |
| Air Link | Unconfirmed, let me know, email: nyabsi@sovellus.cc | |
| Steam Link | ✅ Works | |
| Display Port powered SLAM devices | ✅ Works | Such as: Pimax, PSVR2, HP Reverb G2, etc. |
| VIVE Hub | ✅ Works | VIVE Focus Vision, via e-mail |
Expected behavior, not a bug.
Your controllers use the headset's inside-out tracking, which drifts relative to your lighthouse space, the driver corrects that drift and shifts back into place.
This is expected, there is issues with the VRChat IK system that is not obvious from first glance.
Usually Space Calibrator is not precise enough for these issues to show up, but with SpaceOverride you will see these issues.
Each Lighthouse HMD suffers from the same issues and this is unfortunately the reality we live in.
I am unable to solve these issues as they are not caused by SpaceOverride but I am working on potential workarounds.
This is not TrackingOverride. TrackingOverride simply substitutes one device's pose for another's, which leaves you to deal with the offset between the tracker and the headset yourself. SpaceOverride instead automatically calculates the proper offset between the mounted tracker and the headset during calibration, then continuously reconstructs the headset pose from the tracker using that offset. The result is an aligned, drift-free pose rather than a raw pose swap.
No. SpaceOverride does not conflict with Space Calibrator, you can have both installed. They solve the alignment problem differently, but having Space Calibrator present won't break the override.
Yes. The headset's display pipeline and the lighthouse tracker run on different clocks, so wireless streaming latency (and an unstable connection in general) can introduce a delay between your real head movement and the tracker-driven pose, which shows up as lag or swimming in your view. A solid Wi-Fi setup (or wired connection where possible) keeps this negligible.
No, all drift is induced by poor lighthouse performance, please ensure your lighthouse setup does not have interference.
You can use guide such as: Link
This project uses/used substancial parts of OpenVR Space Calibrator. Huge thanks to pushrax for their work, which this project used to build.
Commits up to and including 1cc0583 are MIT (see LICENSE.MIT). Everything after is AGPLv3 (see LICENSE).