Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
12.0.0
Issue ID
1325200
Regression
No
[XR SDK] Console window is spammed with errors when Orthographic Camera Clipping Plane Near is set to 0 and Target Eye to Both
Reproduction steps:
1. Open the attached "case_1325200_URP.zip" project (or "case_1325200_HDRP.zip")
2. Load the "SampleScene"
3. Select "Main Camera" in the Hierarchy window
4. Make sure the Projection is set to "Orthographic", Clipping Planes Near to "0" and Target Eye to "Both" in the Inspector window
5. Enter Play mode
6. Observe the Console window
Expected result: no errors appear in the Console window
Actual result: the Console window is being spammed with errors
Reproduced with: 7.5.3 (2019.4.23f1), 10.4.0 (2020.3.2f1), 11.0.0 (2021.1.1f1), 12.0.0 (2021.2.0a11)
Could not test with 2018.4 (no XR SDK package)
Error messages:
- Assertion failed on expression: 'IsMatrixValid(matrix)'
- Assertion failed on expression: '!camera.GetOrthographic()'
- Screen position out of view frustum (screen pos 672.000000, 0.000000, 145.720001) (Camera rect 672 0 672 1600)
Notes:
- Reproducible with URP and HDRP
- Tested with Oculus and Unity Mock HMD plug-in providers
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Won't fix. Please use perspective camera projection for VR cameras.