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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.