Search Issue Tracker
Active
Votes
1
Found in
2017.4
2019.3.0f1
2020.1
Issue ID
1205126
Regression
No
DirectX12 performance is worse compared to DirectX11 and Vulkan
How to reproduce:
1. Open attached project ("DrawCallPerf.zip")
2. Open SampleScene scene
3. In Game window Enable stats and Maximize On Play in the top right corner
4. In Project Settings window, Player tab, disable Auto Graphics API for windows option (Edit->Project Settings->Player)
5. Set Graphics API to Vulcan
6. Enter Play mode
7. Observe FPS (ms) in the Statistics panel
8. Set Graphics API to DirectX11
9. Enter Play mode
10. Observe FPS (ms) in the Statistics panel
11. Set Graphics API to DirectX12
12. Enter Play mode
13. Observe FPS (ms) in the Statistics panel
Expected result: All Graphics APIs should have similar performance
Actual result: DirectX12 performance is worse more than twice compared to Vulcan and DirectX11
- D11: 232fps, 4.3ms | D12: 111fps, 9.2ms | V: 225fps, 4.5ms
Reproducible with: 2017.4.35f1, 2018.4.15f1, 2018.4.15f1, 2019.3.0f4, 2020.1.0a18
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
Add comment