Search Issue Tracker
Fixed in 5.5.0
Votes
5
Found in
5.5.0b5
Issue ID
836850
Regression
Yes
[5.5] Batches increase in 5.5 compared to 5.4, various FrameDebugger issues with batching
To reproduce:
1. Open user project
2. Open the scene "CH_Level_1_Build"
3. Enter Play mode
4. Check "Batches" and "SetPass calls" in Game Stats.
Expected:
The Batches and SetPass calls count stays roughly the same in both versions.
Actual:
1) [not a bug, 5.3 actually was not counting SetPass in depth render] 5.4.2 compared to 5.3.6 has about 2x more SetPass calls (coming from depth texture rendering), similar amount of batches
2) [fixed] 5.5 compared to previous (5.3 or 5.4) has much more batches
3) [fixed] 5.5 when not in play mode, does not display "saved by dynamic batching" stat
4) [fixed] 5.5 when in play mode, doubles SetPass calls compared to outside of play mode
5) [fixed] 5.5 many static batch draw calls in frame debugger aren't shown as such (due to static batch draw call merging that was done)
6) [fixed] 5.6 frame debugger left side tree often does not update to reflect changes
7) [fixed] 5.6 frame debugger rendertarget display often displays wrong/stale data?
Reproduced on: 5.4.0f3, 5.5.0b5
Did not reproduce on: 5.3.4f1, 5.3.6p3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment