Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
3.2.13
Issue ID
1258200
Regression
No
[XR SDK] E02 cell of the projection matrix shows same values in both eyes
Reproduction steps:
1. Open attached project ("EO2Repro.zip")
2. Enter "SampleScene" scene
3. Enter Play mode
4. Open Inspector window
5. Select "Repro" Game object
6. In Inspector window "Custom Projection Matrix" component expand "Leftmatrix" and "Rightmatrix" dropdowns
Expected result: Rightmatrix E02 cell value is positive, Leftmatrix E02 cell value is negative
Actual result: In both matrices E02 cells are negative
Reproducible with: XR SDK 3.2.13 (2019.4.6f1, 2020.1.1f1, 2020.2.0a20)
Not reproducible with: Legacy XR (2018.4.26f1, 2019.4.6f1)
Comments (1)
-
bugrock
Aug 01, 2020 04:31
Projection matrices are not the same per eye. Prior to installing the Oculus XR plugin the E02 cell of the projection matrix of the right eye is 0.1470005f (positive value). After installing the Oculus XR plugin the right eye projection matrix E02 cell value is -0.1470005f(negative value) . The left eye should be negative and the right should be positive. This is for projection matrices.
If one creates a project with the Oculus XR plugin with 2 cameras with one camera set to target eye left and the other camera set to target eye right they will see double vision in the oculus rift headset. I narrowed this down the the incorrect value in the projection matrix. This is not observable if only one camera is used and the target eyes are set to both.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Volume" Component documentation link is missing
- GUI.TextField cursor is misaligned from text when setting Content Offset on GUI Skin
- The beginning of the Animation doesn’t start at the correct position when it's being enabled through a Trigger event and the Physics Simulation mode is set to "Update"
- Values are cut off between Visual Scripting Node links when in Play mode
- UI Toolkit Style is inconsistent when using Style Classes named using digits
This is a duplicate of issue #1262524