Search Issue Tracker
Fixed in 4.0.0-pre.3
Votes
0
Found in [Package]
4.0.0-pre.3
Issue ID
1305592
Regression
No
[XR SDK] Console window is spammed with errors when Orthographic Camera's Clipping Plane Near is set to 0 and Target Eye to Both
Reproduction steps:
1. Open the attached "case_1305592.zip" project
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: XR SDK 3.2.17, 4.0.0-pre.3 (2019.4.18f, 2020.2.2f1, 2021.1.0b2, 2021.2.0a1)
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)
Note: 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
- Sprite Preview is broken when the Sprite is too tall or too wide
- Objects are invisible in Scene view when using Wireframe Shading Mode
- The property of a component becomes read-only when it is bound to "PropertyStreamHandle"
- Physics.Raycast does not work when used on the whole model
- Shader Graph changes the Position of Prefab instances in Play mode
Resolution Note (fix version 4.0.0-pre.3):
Properly guarded against setting Orthographic projection for rendering to the main view when XR enabled and any XR plugin is running and added warning hints in the editor and debug log warning as well. Fixed in: 2021.2.0a11
Resolution Note (fix version 4.0.0-pre.3):
Fixed in: 2020.3.10f1
Resolution Note (fix version 4.0.0-pre.3):
Fixed in: 2021.1.8f1
Resolution Note:
Fixed in: 2019.4.27f1