Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
4.3.0b2
Issue ID
563349
Regression
No
[Batching] Batching stats discrepancy in Profiler
TL;DR: to repro, run the attached project on a standalone platform, a mobile device, and in the editor player and record the draw calls in each user the profiler or stats button. It is my contention the profiler reports an incorrect number of draw calls in the standalone and mobile runs, but the stats viewer in the editor's player are correct.
---------------------------
The project features a camera passing through two sets of objects: one set is dynamic, the other static. The user can examine the number of draw calls by selecting and deselecting the static and dynamic batching boxes in File > Build Settings > Player Settings > Other Settings then running the project on standalone or mobile followed by running it in the editor's player. Doing so yields four possible selections - run anywhere but the editor's player, the profiler always yields odd numbers, which isn't mathematically possible (by my math, anyway). When run in the editor's player the results for yielded by the stats for each case are listed below:
Dynamic Only:
- When displaying the four boxes arranged in a square, the editor player's stats show 6 calls, 4 saved by batching.
- When displaying the four boxes arranged in a line, the editor player's stats show 4 calls, 2 saved by batching.
- When displaying nothing, all objects (except the point light and main camera, I presume) are effectively culled, thus 2 calls, 0 saved by batching.
Static Only:
- When displaying the four boxes arranged in a square, the editor player's stats show 8 calls, 2 saved by batching.
- When displaying the four boxes arranged in a line, the editor player's stats show 4 calls, 2 saved by batching.
- When displaying nothing, all objects (except the point light and main camera, I presume) are effectively culled, thus 2 calls, 0 saved by batching.
Both selected:
- When displaying the four boxes arranged in a square, the editor player's stats show 6 calls, 4 saved by batching.
- When displaying the four boxes arranged in a line, the editor player's stats show 4 calls, 2 saved by batching.
- When displaying nothing, all objects (except the point light and main camera, I presume) are effectively culled, thus 2 calls, 0 saved by batching.
None selected:
- When displaying the four boxes arranged in a square, the editor player's stats show 10 calls, 0 saved by batching.
- When displaying the four boxes arranged in a line, the editor player's stats show 6 calls, 0 saved by batching.
- When displaying nothing, all objects (except the point light and main camera, I presume) are effectively culled, thus 2 calls, 0 saved by batching.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment