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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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.