Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.31f1
2022.3.11f1
2023.1.18f1
2023.2.0b15
2023.3.0a11
Issue ID
UUM-54533
Regression
Yes
DrawMesh is not being batched showing the "Saved by batching" value in the "Stats" window as 0
How to reproduce:
1. Open the "IN_20895(1)" project
2. Open the "EngineTest1" Scene
3. Enter the Play Mode
4. Open the "Stats" window
5. Observe the "Stats" window
Expected result: "Saved by batching" value is more than zero
Actual result: "Saved by batching" value is zero
Reproducible with: 2021.3.31f1, 2022.3.11f1, 2023.1.18f1, 2023.2.0b15, 2023.3.0a11
Reproducible on: Windows 10 Pro
Not reproducible on: no other environment tested
Notes:
- The 2019.4.1f1 version didn't have this issue. To observe correct behaviour use "IN_20895(2)" project
- Couldn't test with 2020.3 stream due to errors in the Console when downgrading user project
- Didn't test player due to "Saved by batching" missing in the Profiler
- Couldn't find the regressed version due to the errors downgrading or upgrading projects
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:
In this specific project, batching does not take place in both versions. The "Saved by batching" number should remain at zero. In the 2019 version, there was an issue where negative numbers were displayed, but we have resolved that problem in subsequent versions.