The last time I tried migrating a project from the built-in render pipeline to URP about 6 months ago, I noticed that SpriteRenderers were contributing to way more draw calls than before. Upon closer inspection, it appeared to be related to SRP Batcher: it simply didn’t support batching SpriteRenderers and refused to use dynamic batching to combine them.
I’ve found [this comment]( "SRP Batcher" in 2018.2 page-2#post-4701479) from 2019 where Arnaud said that SPR Batcher doesn’t support SpriteRenderers, but they may look into it later. It seems this hasn’t changed since then.
Are there any plans to support SpriteRenderers in SRP Batcher? I only ask that it uses dynamic batching the same way the built-in RP does. SpriteRenderer is very useful in 3D and VR for drawing flat elements in world space without the overhead of a world-space Canvas and with better batching (when it works) and workflow when compared to MeshRenderer quads.
Yes, it should. Do let us know if it is not the case!
Here is a quick test of two different characters, Knight and Skeleton, with each using their own SpriteAtlas using the Sprite-Lit-Default material without 2D animation deformation for 2023.1.3f1.
That’s amazing, but kinda makes all my knowledge about optimizing draw calls obsolete now. Would there be some update to the documentation about optimizing draw calls/performance with SRP?
For sprites with dense mesh or skinned, SRP-Batcher usually results in better performance as SRP-Batcher.
For sprites that are full rect (quads) or with very few vertices, Dynamic-batching (disabling SRP-Batcher or disabling SRP-Batcher with a custom shader) is preferable.
