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
- Crash on mono_domain_jit_foreach when performing various Unity operations
- Error is thrown when playing audio through Timeline in a Windows Server Build
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
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.