Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b8
Issue ID
639789
Regression
Yes
Static batching statistics are misleading
To Reproduce:
1. Open and build the attached project ( one scene with 9 default cubes) to iOS on 4.5.5 and 5.0.0b9 (or use the attached xcode projects).
2. Deploy to device and click 'Debug\Capture GPU frame':
-on 4.5.5 the cubes are drawn in a single draw call ( attached captured_frame_455_9cubes.png) that takes ~3.29ms
-on 5.0.0b9 the cubes are drawn using 9 draw calls ( attached captured_frame_5b9_9cubes.png ) but all of them also take ~3.29ms.
Not sure whether http://fogbugz.unity3d.com/default.asp?614919 (Unity doesn't display static batching statistics correctly) is the cause of this. According to the internal profiler batching isn't working on 5.0.0b9 (0 calls batched), but if that is only an issue with Unity profiler, should that have an effect on how xCode displays draw calls?
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
- Shader Graph validation errors are not pointing to the right implementation
Add comment