Oculus Pose prediction and hardware latency testing support has landed in the 2016-02-24 Firefox Nightly. The effect will only be seen by Windows users with Oculus 0.8 runtime or newer. Existing WebVR content will take advantage of this automatically, without any modifications.
The HMD pose and frame numbers submitted with each frame were not consistently associated with the frame that the sensors were sampled on. This update corrects this, enabling the Oculus HUD to show accurate latency information. Providing the accurate pose information to the Oculus runtime also results in a perceived lower latency and smoother HMD tracking.
Pose prediction has also been implemented behind a preference, which is disabled by default for now. Pose prediction offsets the effects of latency by returning a predicted future HMD pose instead of the instantaneous HMD pose. The prediction is dependent on the accurate measurement of latency, through the hardware latency tester. Through use of the latency tester, we have identified a reduction of frame latency uniformity when using e10s (Multi-process). I recommend that you disable the multi-process in about:preferences / general before enabling pose prediction until we have improved the latency uniformity.
If you wish to try pose prediction early, set the
dom.vr.poseprediction.enable preference to
Additionally, setting the
layout.frame_rate preference to match the framerate of your hardware is recommended. This should be set to
75 for Oculus DK2 and
90 for Oculus CV1.
Some exciting updates for WebVR are coming soon, stay tuned!