Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.3.X
Votes
0
Found in
2019.4
2019.4.12f1
2020.1
2020.2
2021.2
Issue ID
1289059
Regression
No
[XR SDK] [Oculus] Occlusion glitches when camera is close to the clipping plane and transitions between 2 baked occlusion areas
Reproduction steps:
1. Open the attached project ("1289059-Repro.zip")
2. Open "SampleScene" scene
3. Move Headset a bit (CenterEyeAnchor Game object Position needs to be very close to 0; 0; 0;)
Expected result: All geometry that should be visible remains visible all the time.
Actual result: Geometry that should be visible becomes invisible on very specific points between bakes occlusion areas
Reproducible with: XR SDK 3.2.16 (2019.4.14f1, 2020.1.12f1, 2020.2.0b10, 2021.1.0a4)
Could not test with: 2018.4.28f1 (XR SDK not available)
Tested:
- Oculus Rift
Note:
- On Rift make sure to toggle "Reset Tracker On Load" in OVRCameraRig Game object
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
- The sidebar reopens when Unity Hub is started when Unity Hub was closed with the sidebar closed
- Characters are invisible in the TextField when certain Japanese characters are used
- "InvalidOperationException" is thrown when using Prefab > Replace to replace a Canvas GameObject with a Prefab that has an incompatible root Transform type
- Looping AudioSource resumes from the wrong playback position when the app is backgrounded and resumed on iOS Safari
- "AnyState Transition Created" action can be undone when pressing "Auto Generate Animation" on the uGUI GameObjects
Resolution Note (fix version 2021.1):
Fixed with 2021.2.0a4, backported to 2021.1.0b10, 2020.3.1f1, 2019.4.24f1