Search Issue Tracker
By Design
Votes
0
Found in
2023.1.0a9
Issue ID
UUM-13806
Regression
Yes
[2023.1] Static batching processes five times fewer objects than it should when rendering on a specific project
How to reproduce:
1. Open the user’s attached “StaticBatchingRegression” project
2. Enter the Play Mode in the “Perf_Batching” Scene
3. Observe the Static Batching reported data in the “Profiler → Rendering” module
Expected result: Batches count is 271
Actual result: Batches count is 55
Reproducible with: 2023.1.0a5, 2023.1.0a9
Not reproducible with: 2020.3.39f1, 2021.3.9f1, 2022.1.16f1, 2022.2.0b7, 2023.1.0a4
Reproduced on: macOS 12.5 (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
- 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
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Less batches with visually equal results is the result of an optimization and the central goal of batching: Reducing draw calls.