Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.1p2
Issue ID
931226
Regression
No
Occlusion culling not occluding
Steps:
1. Use repro project in comment "SmallRepro.zip"
2. Bake occlusion culling with the following 2 cases:
(A) Enable "ROAD1_doesn'twork" and disable "ROAD1_work" -> bake occlusion culling -> the sphere is not occluded (wrong)
(B) Enable "ROAD1_work" and disable "ROAD1_doesn'twork" -> bake occlusion culling -> the sphere is occluded (correct)
Please see image in comment.
Note: The occlusion culling will start occluding objects if camera is much closer to the "wall"
Reproduced with: 2019.1.0b4, 2018.2.0a8, 2018.1.0b13, 2017.4.1f1, 2017.3.0a1, 2017.1.0p1, 5.6.2p4, 5.5.4p2
Working with: 2019.2.0a9
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
This is limitation of Umbra Occlusion Culling. We are working on new culling system so will close this.