Search Issue Tracker
Not Reproducible
Votes
27
Found in
2018.3.0a6
Issue ID
1064796
Regression
Yes
[Metal] Performance degradation on iOS devices
To reproduce:
1. Open the GraphicsPerf project with Unity 2018.2;
2. Change Graphics API to Metal;
3. Build and run DynamicVBO, Lights, Materials, Particles, ParticlesCollision and Tesselation scenes on iOS devices.
4. Repeat all steps with Unity 2018.3.0a6;
5. Compare frame time.
Important: let devices to cool down between each run.
Expected result: performance increases or at least remains the same.
Actual results: frame times increase 6-12% in trunk, even 40% with some devices.
Devices under testing:
-iPad Mini 4 (SoC: A8, iOS: 11.4),
-iPhone SE (SoC: A9, iOS: 10.0.1),
-iPhone X (SoC: A11, iOS: 11.4),
-iPad 5th gen (SoC: A9, iOS: 10.3).
Tested with: 2018.1.f1 and 2018.3.0a6
Comments (8)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
vincent-savysoda
Jan 07, 2019 06:09
Not sure if this should be mentioned here, but there's performance degradation issues for Android builds as well. Just updated to 2018.3f2 from 2018.2 and builds on devices suffered a sudden performance drop.
firstuser
Dec 28, 2018 01:39
Please fix.
odysoftware
Dec 14, 2018 20:12
"Necessary for shipping a final release" - and now we have 2018.3 final and report is still only "Active" ?
adslitw
Dec 08, 2018 06:59
Bump - an update on this would be great, especially considering how long this issue has been active for. It’ll get fixed for 2018.4 LTS right!?
Deeeds
Sep 20, 2018 17:09
Is this going to get addressed/fixed in 2018.3?