Forum Discussion
Timewarp and client distortion rendering
Hello, I'm doing client (non-SDK) rendering with 0.4 and I'm having some issues with timewarp.
I've followed the examples in the docs wrt calling ovrHmd_BeginFrameTiming and ovrHmd_EndFrameTiming at the appropriate points, but the TimewarpPointSeconds member of the object returned by ovrHmd_BeginFrameTiming always seems to be 0.0.
From poking around a bit in the source code, I'm wondering whether I should be calling
ovrHmd_AddDistortionTimeMeasurement, either before or after I do the distortion render? That seems to be where TimewarpWaitDelta gets updated.
It also looks like elsewhere in the code the timewarp stuff might get hard coded to 0 if SDK rendering is off anyway.
Just wondering if this is the case or if I did something stupid along the way (wouldn't be the first time).
Although I'm updating timewarp matricies (which seems to come back with something non-identity) if I'm never waiting until the correct point to do the distortion render presumably it's going to be a bit off?
I've followed the examples in the docs wrt calling ovrHmd_BeginFrameTiming and ovrHmd_EndFrameTiming at the appropriate points, but the TimewarpPointSeconds member of the object returned by ovrHmd_BeginFrameTiming always seems to be 0.0.
From poking around a bit in the source code, I'm wondering whether I should be calling
ovrHmd_AddDistortionTimeMeasurement, either before or after I do the distortion render? That seems to be where TimewarpWaitDelta gets updated.
It also looks like elsewhere in the code the timewarp stuff might get hard coded to 0 if SDK rendering is off anyway.
Just wondering if this is the case or if I did something stupid along the way (wouldn't be the first time).
Although I'm updating timewarp matricies (which seems to come back with something non-identity) if I'm never waiting until the correct point to do the distortion render presumably it's going to be a bit off?
No RepliesBe the first to reply