Search Issue Tracker
Fixed in 5.3.6
Votes
1
Found in
5.3.4f1
Issue ID
798692
Regression
No
Reduced performance in Metal vs GLES3.0 when using Standard Shader
How to reproduce:
1. Open attached project
- Make sure that Metal is the selected Graphics API in the Player settings
2. Build to iOS and open the project in Xcode
3. In the Scheme settings enable the appropriate GPU Frame Capture setting (Metal in this case)
4. Deploy to device
5. In Xcode click the Camera icon to capture a frame
6. Once it loads, select the FPS tab at the top
- Make a note of the performance stats there (screenshot)
7. Repeat from step 2 but with OpenGLES3 instead of Metal
8. Compare the stats between GLES3 and Metal, when running on the same device
- Note how the Metal performance is worse than GLES3
- Reproduced in Version 5.2.4f1 (98095704e6fe), Version 5.3.4f1 (fdbb5133b820), Version 5.4.0b18 (cdaae1c8e465) on an iPad Pro (iOS 9.2.1)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment