Search Issue Tracker
By Design
Votes
6
Found in
2020.3.46f1
2021.3.20f1
2022.2.10f1
2023.1.0b7
2023.2.0a5
2023.3.0a3
Issue ID
UUM-29074
Regression
No
Screen Space decals doubles the scene draw calls when rendering layers are enabled
How to reproduce:
1. Download and open the attached project
2. Open the "BugSampleScene" scene
3. Open the Game view window
4. Observe the Game view statistics
Expected outcome: Statistics window shows 8 batch call draws
Actual outcome: Statistics window shows 13 batch call draws
Reproducible with: 2020.3.46f1, 2021.3.20f1, 2022.2.10f1, 2023.1.0b7, 2023.2.0a5
-
ZZZGoat
Oct 20, 2023 09:14
Please resolve this issue! Is critical for our project also.
-
zenbin3d
Oct 19, 2023 10:29
Unity guys...this issue seems pretty bad. I mean, double draw calls?! Anyone?
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
- Sprite Masks affect Sprite Renderers outside their range when a Light2D is present with specific Target Sorting Layers selected
- URP Lens Flare is rendered in the wrong position when Render Graph Compatibility Mode is enabled and Render Scaling is not 0
- Editor crashes on DrvPresentBuffers when loading RenderDoc while using OpenGLES 3.0 or OpenGLES 2.0 Graphics API
- [Test Runner] Incorrect name under Window > Panel after project restart
- [iOS] Crash when using fallback fonts created at runtime
Resolution Note:
The reason for the increase in draw calls is because when MSAA is enabled, the renderer needs to get the layers from a DepthNormals prepass.
Rendering layers can not use MSAA resolve, because it encodes integers. By disabling MSAA, the draw count in that project does not change when enabling/disabling Rendering Layers.