There's a firmware bug in CV1 firmware 1 that causes extra reports when the controllers are on. Possibly related is the corrupt reports where controller data has been written into the headset marker frame, also breaking the encryption. I have observed usually 2 but sometimes 3 identical frames in a row. When really tracking, the pose data is never actually constant, so these should be easy enough to detect.
Not filtering these duplicates out means derivatives like velocity become highly erratic.
There's a firmware bug in CV1 firmware 1 that causes extra reports when the controllers are on. Possibly related is the corrupt reports where controller data has been written into the headset marker frame, also breaking the encryption. I have observed usually 2 but sometimes 3 identical frames in a row. When really tracking, the pose data is never actually constant, so these should be easy enough to detect. Not filtering these duplicates out means derivatives like velocity become highly erratic.