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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
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.