Search Issue Tracker
By Design
Votes
0
Found in
5.6.0b9
Issue ID
886280
Regression
Yes
Occlusion culling not culling all needed objects
Reproduction steps:
1. Open the project occlusion1 on version 5.5.0b2
2. Open the project occlusion2 on version 5.5.0b3 or newer
3. Bake occlusion on both projects if there is no occlusion data
4. Select Camera in both objects
5. Check Visualize option in scene view of both projects
6. Observe results
Expected: same view
Actual: on newer version, not all of the needed objects are culled
Not reproduced on: 5.5.0b2
Reproduced on: 5.5.0b3, 5.6.0b9, 5.6.0f3, 2017.1.0a6
Regression introduced on: 5.5.0b3
By design: In Unity 5.5 and above, when a renderer is part of a LOD group, we only consider in the bake data LOD0. User has it's LOD0 occluder settings different from the one set for other LOD levels. he should update his scene in order to propertly flag LOD0 renderers.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment