SlimeVR-Server
SlimeVR-Server copied to clipboard
Drift compensation should take minutes instead of resets
The "last x resets" UI paradigm is not ideal. It allows a few overly short yaw resets to have undue influence on the average drift, causing erroneous compensation values.
Better might be "last x minutes", where the SlimeVR Server stores a record of all yaw resets performed in the listed time period and averages them.
quick successive resets are not taken into account because there’s a 50sec timer between resets
what if someoe does a yaw reset, realizes they were posed the wrong way, and tries again? i think the latest reset should override the previous recording if it was within 50 seconds ago
what if someoe does a yaw reset, realizes they were posed the wrong way, and tries again? i think the latest reset should override the previous recording if it was within 50 seconds ago
That’s actually what it does
https://github.com/SlimeVR/SlimeVR-Server/blob/e8afb49685854d636905c7d545b7832060e89dc3/server/core/src/main/java/dev/slimevr/tracking/trackers/TrackerResetsHandler.kt#L489