Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
18
Found in
2019.3
2019.3.0f5
2020.1
Issue ID
1212234
Regression
No
[HDRP] [XRSDK] Camera does not respect near/far clipping plane settings
How to reproduce:
1. Open attached project ("Repro-1212234.zip")
2. Open SampleScene scene
3. Enter Play mode
4. Select the Main Camera in Inspector window
5. Set Far Clipping plane value to anything bigger than 1170
6. Set Near Clipping plane to any value
Expected result: Near/Far Clipping plane settings are respected
Actual result: Near/Far Clippings plane settings aren't respected
Reproducible with: 2019.3.0f6 [HDRP 7.1.6] [XR Management 3.0.5], 2020.1.0a22 [HDRP 7.1.8] [XR Management preview.2 3.1.0]
Not tested with: 2019.2.21f1 and previous versions (XR SDK crashes HDRP, errors in code)
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2020.2):
Fix for this issue is incoming