Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.26f1
Issue ID
UUM-37730
Regression
No
UpdateRendererBoundingVolumes process takes more time when disabled Renderers are used
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Open the Profiler Window (Window > Analysis > Profiler)
5. In the Profiler Window, observe the UpdateRendererBoundingVolumes process
Expected result: The UpdateRendererBoundingVolumes process takes only a marginal amount of processing time
Actual result: The UpdateRendererBoundingVolumes process takes a significant processing time
Reproducible with: 2021.3.26f1, 2022.2.0a16
Not reproducible with: 2022.3.1f1, 2023.1.0b19, 2023.2.0a17
Fixed in: 2022.2.0a17
Could not test with: 2020.3.48f1 (UpdateRendererBoundingVolumes process is not visible inside the Profiler Window)
Reproducible on: Intel MacOS 13.3.1
Notes:
- The textures appear pink in all versions except for 2021.3.26f1 but the UpdateRendererBoundingVolumes process is still visible in the Profiler Window
- In the Hierarchy Window, deleting the “Test > Disabled Parent CHECK PROFILER AND REMOVE ME” GameObject reduces the time of the UpdateRendererBoundingVolumes processes significantly
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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. Currently, we're focusing our resources on fixing more critical issues that affect a larger portion of our user base.
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.