Search Issue Tracker
By Design
Votes
0
Found in
2017.4
2018.4.12f1
2020.2
Issue ID
1230814
Regression
No
GameObject is not culled and can be seen in the Frame Debugger when Camera is facing away from it
How to reproduce:
1. Open the attached project's Scene labeled "CullingTest2"
2. Open the Frame Debugger (Window->Analysis->Frame Debugger)
3. Enter the Play Mode
4. In the Frame Debugger, inspect the "RenderForward.RenderLoopJob" tab
Expected result: "TestObj" GameObject is culled
Actual result: "TestObj" GameObject is not culled
Reproducible with: 2017.4.38f1, 2018.4.20f1, 2019.3.6f1, 2020.1.0b3, 2020.2.0a5
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
- 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
Resolution Note:
Hi in this case for culling we use 'sphere bounds' for performance reasons. In the example sent the sphere bounds for this object intersect with the frustum still.