Closed PiMaker closed 1 month ago
this happens when a Quest enters out-of-bounds passthrough mode or standby for example, in which case it's almost always cleaner to keep the current calibration alive instead of calibrating towards a zero location
this happens when a Quest enters out-of-bounds passthrough mode or standby for example, in which case it's almost always cleaner to keep the current calibration alive instead of calibrating towards a zero location