Search Issue Tracker
Fixed in 5.5.0
Votes
21
Found in
5.1.2p3
Issue ID
725002
Regression
No
[Occlusion Culling] Occlusion visualization results change after restarting the editor
Reproduction steps:
1. Open attached project
2. Open scene "OcclusionTest"
3. Bake Occlusion data
4. Use Occlusion-Visualization panel to test the camera inside the room in the ship. Occlusion works as expected (exterior ship is not rendered unless looking out a doorway of the room)
5. Save scene and project
6. Exit and restart Unity
7. Without changing anything, select the same camera as before and test with Occlusion Visualization tool. Observe that occlusion culling is very different (in test case the exterior ship is now always rendered if it falls within the frustum. No occlusion culling at all)
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
- [Android] [Vulkan] UI that is activated after a delay flickers when a Scriptable Render Pass goes over it
- [Linux] Characters are converted to Latin letters when using IME on Linux
- [Ubuntu] Possible for Create menu to show sections with no options inside
- [Usability] Not possible to set Editor Window text colour to be default black without workaround
- Text field max length is -1 by default
ss0cratess
Oct 09, 2023 10:34
2020.3.48f1 anyone?
sinfawkes
May 03, 2017 07:37
5.4.2 still occurs
svanvs
Jun 02, 2016 17:29
Same as issue 739220
chrismarch
Apr 01, 2016 22:35
occurs in 5.3.4f1
Haze-Games
Dec 04, 2015 11:56
Tested in 5.2.3f1.
The issue is not just on Visualization; the occlusion data works perfectly just after the bake. If you reload the scene or work on another scene and come back, the occlusion data is broken.
DarthDisembowel
Sep 10, 2015 14:19
For a quicker test method, after baking occlusion and saving the scene, you can also simply double-click on the scene in the Project explorer to refresh the scene, which will immediately break the occlusion culling.
DarthDisembowel
Sep 09, 2015 08:23
Tested in 5.2.0f3, the problem still occurs.