Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.29f1
2022.3.8f1
2023.1.10f1
2023.2.0b6
2023.3.0a2
Issue ID
UUM-46881
Regression
No
GameObjects are not always culled when outside the Camera's frustum
Reproduction steps:
1. Open the attached “IN-48510 Frustum Culling.zip” project
2. Open the “IN-48510_FrustumCull_Bug” scene
3. Enable the Statistics overlay by pressing the “Stats” button on the Game view Control Bar
Expected result: The “Cube” is frustum culled and the Statistics in the Game view display “Tris: 2”, “Verts: 4” and “SetPass calls: 1”
Actual result: The “Cube” is not frustum culled and the Statistics in the Game display “Tris: 14”, “Verts: 28” and “SetPass calls: 2”
Reproducible with: 2021.3.29f1, 2022.3.8f1, 2023.1.10f1, 2023.2.0b6, 2023.3.0a2
Reproduced on: Windows 11 Pro (22H2)
Not reproduced on: No other environment tested
Notes:
- Different Rendering Paths used by the “Main Camera” produce different triangles' and vertices' amounts but the issue still reproduces the same way
- Field of View and Near Clipping Plane settings of the “Main Camera” change the Position and/or Rotation the Camera needs to be at to reproduce the issue
- Could not test in Player due to the “Cube” GameObject not being visible on the screen whenever the issue reproduces or not
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
- Memory leaks when Instantiating Objects with SerializeReference
- Currently selected Action Map switches to the first Action Map in the list and it's first Action when editing the Binding Path of a newly created Action
- "F" default focusing Unity shortcut zooms out when the first time focusing the GameObject
- DropdownField options added with PointerDownEvent are not shown when clicking the DropddownField for the first time
- References are reset to "None" when opening the project
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.