Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0b9
Issue ID
946946
Regression
No
Dynamic Batching Draw Calls always 0 in a player
Steps to reproduce:
1. Open the attached project
2. Open Player Settings and notice Dynamic Batching is enabled
3. Press File/Build & Run to build a Windows Standalone 64bit player (XBOX or UWP)
4. Connect and enable Profiler to running Player
5. Select "Rendering" tab
6. Observe "Dynamic Batching" shows "Batched Draw Calls: 0" always
Actual results:"Batched Draw Calls: 0" always
Expected results: Batched Draw Calls should not be 0
Reproduced with: 5.5.4p4, 5.6.3p2, 2017.1.1f1, 2017.2.0b11, 2017.3.0a7
Comments (1)
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Peter77
Sep 22, 2017 13:18
Here is the related forum thread:
https://forum.unity.com/threads/case-946946-dynamic-batching-not-working-in-a-player.491903/