Search Issue Tracker

By Design

Votes

0

Found in

2019.4

2020.3

2020.3.18f1

2021.2

2022.1

Issue ID

1387714

Regression

No

Frame Debugger shows different number of Draw Calls when compared to ones shown in the Profiler

FrameDebugger

-

Reproduction steps:
1. Open the attached project "1127156.zip" and load Scene "SampleScene"
2. Open the Frame Debugger window (Window -> Analysis -> Frame Debugger)
3. Open the Profiler (Window -> Analysis -> Profiler) and select the Rendering Module
4. Enter Play Mode
5. Enable the Frame Debugger
6. Compare the Draw Calls values displayed in the Profiler and Frame Debugger,

Expected result: The Draw Calls values are the same
Actual result: The Frame Debugger and Profiler Draw Calls values do not match

Reproducible with: 2019.4.34f1, 2020.3.25f1, 2021.2.7f1, 2022.1.0b2

Notes:
- In older versions, in some situations the Stats window would also show different values, however, on the newest versions the values match the ones in the Profiler
- Disabling certain settings, such as SRP Batcher, Static batching and some others can make the difference in values smaller, however, they still do not match
- See attached screenshots with the different values

  1. Resolution Note (2022.2.X):

    The two numbers represent different things; 'batches' are draw calls (instanced, dynamic and static batched) we made, or would have made, to draw the scene - as batched draw calls are expanded (so one batched draw call could equal 4 'batches' on the stats window). The Frame Debugger, on the other hand, shows Rendering Events, which includes things other than draw calls, thus the two numbers measure different things. The documentation will be updated to make this clearer.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.