You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-25Lines changed: 2 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,10 +122,9 @@ will either cause SteamVR to lose connection to the device or will compete for b
122
122
123
123
Calibration is the process which establishes where the lighthouses are set up in relation to the tracked objects. The
124
124
first time you run libsurvive, it can take up to ten seconds to communicate with the lighthouses and figure out where
125
-
they are. During this time you should not move the devices.
125
+
they are.
126
126
127
-
Calibration should work with any device, but the HMD gives the best results due to it's size and number of sensors. If
128
-
the HMD and other controllers are present at startup, it will automatically prioritize using the data from the HMD.
127
+
Calibration will continuously integrate objects data so long as they are momentarily stationary. Due to this, you might notice lighthouses shift slighty while it gets a good lock. Subsequent runs should shift much less.
129
128
130
129
Once you do this one time, it is saved in `config.json` in `XDG_CONFIG_HOME/libsurvive`. If you delete this file, it will simply
131
130
recalibrate; but it is faster to use the `--force-calibrate` flag. Some drivers change the name of this file -- notably recordings will instead use `<event_file>.json`.
@@ -139,28 +138,6 @@ calibrate.
139
138
available. If one of the calibrated lighthouses are moved, you either have to redo calibration by deleting the config.json
140
139
file or passing `--force-calibrate` into any of the libsurvive tools.**
141
140
142
-
Version 1 systems will have an output that looks roughly like:
[For reference, here is an older recording of how a properly running calibration looks like](https://haagch.frickel.club/Peek%202018-02-21%2023-23.webm).
155
-
156
-
Version 2 systems will have output that looks something like:
157
-
```
158
-
Info: Attempting to solve for 0 with 30 meas
159
-
Info: Attempting to solve for 1 with 21 meas
160
-
Info: Solved for 0 with error of 0.005446/0.000000
161
-
Info: Solved for 1 with error of 0.005446/0.000000
162
-
Info: Using LH 0 (d99e7eac) as reference lighthouse
0 commit comments