- Home /
Why is my occlusion Culling different at runtime?
Hi Unity,
So, I'm having a strange issue with my scene. I have Occlusion Culling setup and working perfect in the editor. I do all my visual debugging in the editor and even in the Unity Player. However, once I compile the scene and run it on my machine, the Occlusion Culling is very different. I have large segments of my map just disappear. I'm using Unity pro 4.3.3, and the default settings for Occlusion Bake inspector.
Has anyone else had this happen?
It may be worth noting that this only happening in my executable builds. Unity player/web player work fine.
So, I'm now convinced that this is a problem with Umbra and its temp files. I took one piece of the map that was not showing up and replaced it with a prefab version and rebaked the Occlusion Data, not only did it fix that part of the map, but all of the other pieces of the map that were broken too.
Your answer
![](https://koobas.hobune.stream/wayback/20220613130914im_/https://answers.unity.com/themes/thub/images/avi.jpg)
Follow this Question
Related Questions
How can apply Occlusion Culling in Prefabs 0 Answers
Is Occlusion culling "free"? 2 Answers
Unity 3.0 tutorials 2 Answers
How could i achieve unity pro features in unity indie 1 Answer
Dynamic Occlusion Culling 1 Answer