0.4.3 ovrHmd_GetEyePoses usage
In SDK 0.4.3 ovrHmd_GetEyePose() got replaced by ovrHmd_GetEyePoses().
I like the way it now includes the necessary IPD translation. This was not very obvious in the previous version and is now handled automatically.
What I don't understand, though, is why the 0.4.3 API now suggests retrieving both eye poses at the same time.
0.4.2 encouraged to call ovrHmd_GetEyePose() seperately for each eye, right before you start culling/drawing each eye in order to get the eye pose as close to the point in time per-eye rendering as possible.
ovrHmd_GetEyePoses() suggests retrieving both poses at the same time, probably at the start of each frame. This moves the second eye pose 'further away' from the optimal pose you could use.
Is this intended? What are the recommendations for when to call ovrHmd_GetEyePoses() and use ist results?
I like the way it now includes the necessary IPD translation. This was not very obvious in the previous version and is now handled automatically.
What I don't understand, though, is why the 0.4.3 API now suggests retrieving both eye poses at the same time.
0.4.2 encouraged to call ovrHmd_GetEyePose() seperately for each eye, right before you start culling/drawing each eye in order to get the eye pose as close to the point in time per-eye rendering as possible.
ovrHmd_GetEyePoses() suggests retrieving both poses at the same time, probably at the start of each frame. This moves the second eye pose 'further away' from the optimal pose you could use.
Is this intended? What are the recommendations for when to call ovrHmd_GetEyePoses() and use ist results?