Scale and offset is not taken into account

hyblocker commented 4 months ago

Some tracking systems are less accurate than other ones. On some headsets, the tracking origin is not necessarily what is reported as (0, 0), and furthermore, one unit may not necessarily correspond to one unit in another tracking system.

OpenvR-SpaceCalibrator offers a way to set a calibration's scale, however the scale difference is not estimate during calibration. Furthermore, there is no way to take the origin into account when adjusting the scale of trackers.

Requirements:

Implement an offset in addition to the existing scale factor.
Possibly, make scale a 3-element vector rather than a 1-element vector, but we'll need to see after testing with people's setups.
Deduce the scale and offset during calibration, and save it. It's probably easy to do, by comparing two poses with one another we should be able to estimate a magnitude, and compare this magnitude between playspaces to obtain a scale factor.

UwUo-oUwU commented 2 months ago

Can I opt in for the testing? I use a Pico 4, it has this issue & it is certainly not drift, for context; Using normal calibration, after calibrating elsewhere, if I were to head to my bed & lay down, it will be "off" per se, but when going back to where I calibrated, everything is correct. When set visible, I can see the tracker on the headset "move off scale" & come back to "zero" where I calibrated moving between the two points. I hope this information helps.

hyblocker commented 2 months ago

currently I don't have an eta for when I'll have a proof of concept of this ready; im still working out the maths ill have to implement for this

hyblocker / OpenVR-SpaceCalibrator

Scale and offset is not taken into account #8