Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.5.0f1
Issue ID
850170
Regression
Yes
[SinglePassStereo | Oculus] Occlusion mesh artifacts
[SinglePassStereo] occlusion mesh artifacts
2. How we can reproduce it using the example you attached
1) Setup Oculus CV1 and Oculus SDK
2) Open 'Reflections' Scene
3) Enter play mode
4) Move the headset around so that the center of of it's view is not occluded by any gameobjects, i.e. look at the horizon
5) Observe the occlusion mesh artifacts rendered in the game view and in the headset
Additional steps
6) Create a standalone build
7) Follow step 4) above
8) Observe occlusion mesh artifacts rendered in game view and in the headset
Note:
I can't figure out exactly which component may be causing the issue but it is certainly something within this scene. Deleting all of the gameobjects (except the camera) and disabling the UI Add Text Compoenent that is attached to the camera seems to make the issue go away.
This is a regression from 5.5.0b11 to 5.5.0f1
I have also tested and found that this occurs on trunk rev 57e9de7c0b66
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
Add comment