Search Issue Tracker
By Design
Votes
0
Found in
5.6.1f1
Issue ID
946497
Regression
No
[iOS] Static batching does not work, causes excessive amount of draw calls compared to Editor
1. Download & Open the attached project
2. Build to an iOS device
3. When the game is running on an iOS device, click "Debug->Capture GPU Frame" in Xcode
4. Enter Play mode of the scene in Unity Editor
5. Enable Frame Debugger
6. Compare the number of draw calls in Unity Editor and iOS build
Expected results: there's roughly the same amount of draw calls in both environments
Actual results: There are around 40 draw calls in Editor (many Static Batches), and hundreds of draw calls in the iOS build.
Reproduced with: 5.5.4p2, 5.6.3p2, 2017.1.0p5, 2017.2.0b9, 2017.3.0a4 [OpenGLES2 and Metal]
Device used: iPhone 6 (iOS 10.3.3)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
mpete
May 23, 2019 06:50
We experience similar issues in 2018.4