Skip to main content
Anonymous
July 10, 2019

OvrSceneView::GetEyeProjectionMatrix ignores eye parameter... why?

I'm confused about this. The samples in the OVR SDK seem to use this to generate the projection matrices "per eye"... but, somehow, the eye parameter in the method is simply ignored, and a projection matrix based only on horizontal / vertical FOV and near distance is generated for both eyes.

The documentation for the method says "We may want to make per-eye projection matrices if we move away from nearly-centered lenses", but I´m not sure what it actually means. Anyone care to comment a bit further on this?

    1 reply

    xSzlobix
    New Participant
    October 13, 2019
    Can you link me to the dokumentation?

    As far as I know, there are 2 projection matrices computed for each eye, the eye offset is not calculated in the matrices themselves, but the image rendered is made rendered by 2 cameras, one for each eye, from the eyes respective location, using the oer eye projection matrices.

    Can you let me know the values the SDK uses for calculating the matrices, please?

    Thank you and good luck!
    Terms & ConditionsAccessibility statement