Equivalent of "motion to photon latency"? Measuring latency incurred by sensor hardware? #249
Description
In the older Oculus literature and demos (Tuscany house, etc.) there's mention of "M2P" or "motion-to-photon latency", which I believe is meant to include the duration from the instance of motion impulse, through the sensor hardware in the HMD, and all through the rendering pipeline and present until the photons are emitted from the HMD that correspond to that moment in time when the motion impulse occurred. In that case, I'm wondering if there's actually any way to get information about that part of the hardware latency through the API, or if there is a standard practice for calculating this kind of latency in terms of how OpenVR works.
As it stands, it's possible to query how long it's been since the last vsync, and the FrameTiming is filled with various trivia, but it seems like no information is recorded about when the motion/IMU data was actually registered. I guess that ideally, I wish that IMU data could be polled raw, and with a timestamp attached or something. Any thoughts on this?