Search Issue Tracker
By Design
Votes
1
Found in
6000.0.5f1
Issue ID
UUM-73318
Regression
No
Draw call batching does not work when using identical Sprite Renderers in URP
Reproduction steps:
1. Open the attached “SpriteBatch.zip” project
2. Enter the Play mode
3. Open the Profiler (Window > Analysis > Profiler)
4. Click on the “Rendering” Module
5. Observe the “(Dynamic Batching) Batched Draw Calls” value
Expected result: “(Dynamic Batching) Batched Draw Calls” value is equal to 4
Actual result: “(Dynamic Batching) Batched Draw Calls” value is equal to 0
Reproducible with: 2023.1.0a11, 6000.0.5f1
Not reproducible with: 2021.3.39f1, 2022.3.32f1, 2023.1.0a10
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Note: Reproducible on a new project
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
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
Resolution Note:
In https://unity.com/releases/editor/alpha/2023.1.0a18 we introduced SRP-Batching for 2D Renderers. Previously when Sprites are dynamic-batched draw-calls are reduced. SRP-Batcher is focused on reducing CPU costs but may result in more draw-calls. Hence the difference in draw-calls.