Skip to content

rift_s: Ignore the first 100 samples for the clock

Jan Schmidt requested to merge thaytan/monado:rift-s-clock-startup into main

After turning on the display, the Rift S sends a burst of stale data and it can lead to wildly incorrect clock estimates that then recover really slowly and cause SLAM tracking to lag horribly.

Throw away the first 100 samples, which seems to be enough (only the first 20 or so seem to be bad).

Also reduce the clock a2b cutoff frequency, for faster adaptation to changes.

Merge request reports