Oculus CV1 IMU latency problem

[VDavid003]

Oculus CV1 IMU latency problem

[thaytan]

That kind of message ([WW] Exposure timestamp 2396847104 was more than 1.5 IMU samples earlier than IMU ts 2396857332 by 10228 µS) implies that OpenHMD didn't get scheduled in time and missed USB traffic. Make sure you're building in release mode (cd build; meson -Dbuildtype=release) to get compiler optimisations and see if that helps?

In general I don't see the lag or choppiness.

It seems like the difference increases until it reaches around 19000 µS then it jumps down and climbs up again.

19.2ms is the duration of 1 camera exposure, so that makes sense that it would be an upper limit on lateness.

[VDavid003]

I did build in release. but I noticed now that after unplugging the HMD from USB and plugging it back in, the latency got much better. (but still noticable) It's been plugged in for a long time (probably months), since I don't really unplug it and on Windows it worked fine.

[thaytan]

That's.. interesting. I can't think of any reason why that would happen. If it happens again it might be interesting to record a USB trace with wireshark