Timewarp broken / asymmetric in 0.4.4 and 0.5

Problem is also there is direct mode.

What you're describing sounds like the occasional problem I saw pre-0.4.4 where the SDK's vsync would be on, but its frame timing is off resulting in a vertical tear somewhere. What you see on the left side of the tear will be slightly out of sync with whatever is on the right side of the tear, and is quite uncomfortable to look at. If that tear happens to be in the middle between the two eyes, you might not notice the tearing but you'll feel pretty bad as you look around. Whenever this happened, I would simply toggle SDK vsync off and then back on, and the frame timing would be correct once again.

Having said all that, you're taking about 0.4.4 and beyond so I'm not sure what the issue is.

Thanks for your input, but It is not screen tearing - I know the difference. If I close each eye and jiggle the headset, I can tell that motion is being predicted further in one eye and not the other. I've encountered plenty of screen tearing before so I know what that looks like as well.

Can you run the Oculus World demo and press space to bring up the stats?

If you take a screenshot of that, it may help indicate the issue.

Also, please include everything you can about your system specs, OS version, GPU driver version, etc.

This sounds like a camera ordering problem. Can you make sure the right eye camera's "depth" property is lower than the left eye camera's? The OVRCameraRig prefab should have been set up this way, but it appears to use depth = 0 for both eyes.

OK I think I found the problem. I created a completely blank project with none of my infrastructure code and it worked fine with time-warp. It is perhaps an amateur mistake on my part for assuming my infrastructure code would not interfere. After some more digging, I found the offender. I use my own positional tracker and do my own drift correction, so one of my scripts is continuously asking for head orientation. I was calling this function in 0.4.4 and 0.5:

OVRManager.display.GetEyePose(OVREye.Left);

However, this appears to have some sort of side effect that causes time-warp to break. There is nothing I could see in the OVR Unity code base to indicate this unfortunately, but I'm guessing the library assumes these to be called only once and sets an internal time marker for time warp. When I upgraded to the latest SDKs, I think I simply grabbed the first function that seemed to give orientation and forgot about it. I switched to calling this function:

OVRManager.display.GetHeadPose (predictionTime);

and things seem to be working now. Can someone from Oculus comment on whether this side effect was intended? I admit I have not been reading the SDK manuals cover to cover on each SDK upgrade.

Thanks for following up with the fix.

It should be safe to call OVRManager.display.GetEyePose from the Update method in your scripts. If you call it in LateUpdate or one of the later rendering callbacks, you could get undefined behavior where one eye comes from a different frame from the other. I've added this to the documentation.

Thanks for the clarification!