Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.40f1
2021.3.10f1
2022.2.0b8
2023.1.0a11
2023.2.0a1
Issue ID
UUM-15173
Regression
No
Culling performance affected linearly when using LODs
Reproduction steps:
1. Open the attached project
2. Open scene "Scenes/SampleScene"
3. Open the Profiler and Profile Analyzer from Windows -> Analysis
4. Make sure that "Objects_WithoutLODs" is enabled and "Objects_WithLODs" is disabled
5. Enter Play mode and record 300< frames
6. Exit Play mode and pull data to the Profile Analyzer Comparison window
7. Enable "Objects_WithLODs" and disable "Objects_WithoutLODs" in the scene
8. Repeat steps 5 and 6
9. Compare the results
Expected result: Culling performance is not affected
Actual result: Noticeable difference in culling performance can be seen
Reproducible with: 2020.3.40f1, 2021.3.10f1, 2022.2.0b8, 2023.1.0a11
Reproduced on: macOS 12.5.1 (Intel)
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
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.
Resolution Note (2023.2.X):
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.