Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.1.1f1
Issue ID
1050509
Regression
No
[Metal][macOS] Performance decrease with Metal Graphics API compared to OpenGL Core
To reproduce:
1. Open attached project;
2. Set Graphics API for Mac to OpenGL Core;
3. Build and run the Courtyard scene;
4. Wait for the counter (on the top left corner) to count average FPS;
5. Set Graphics API for Mac to Metal;
6. Repeat 3-4 steps and compare results.
Expected results: Performance with Metal should be similar to OpenGL Core.
Actual results: Performance decreases when using Metal Graphics API compared to the OpenGL Core
Hardware:
Reproduced with: AMD Radeon Pro 455 2048 MB
Not reproduced with: AMD Radeon Pro 560 4096 MB
Reproduced with: 2017.3.1f1, 2017.4.6f1, 2018.1.6f1, 2018.2.0b9, 2018.3.0a3.
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
Resolution Note (2019.1.X):
We've had many Metal performance improvements in the past year, we believe this is no longer an issue.