Search Issue Tracker
By Design
Votes
0
Found in
2021.3.36f1
2022.3.22f1
2023.2.15f1
6000.0.0b12
Issue ID
UUM-66998
Regression
No
The number of draw calls increases when the number of meshes in a scene is increased
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Scenes/AllCubes” Scene
3. Open the Frame Debugger window (Window > Analysis > Frame Debugger)
4. Press the “Enable” button
5. Observe the “DrawOpaqueObjects” calls
6. Open the “Scenes/HalfCubesHalfSpheres” Scene
7. Observe the “DrawOpaqueObjects” calls
Expected result: The total sum of calls is 6
Actual result: The total sum of calls is 10 or 11
Reproducible with: 2021.3.36f1, 2022.3.22f1, 2023.2.15f1, 6000.0.0b12
Reproducible on: Windows 10
Not reproducible on: No other environment tested
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
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Resolution Note:
The drawcall separation is due to the camera using front-to-back sorting. Selecting the NoDistanceSort opaqueSortMode resolves the separation