Search Issue Tracker
Fixed in 2020.2.X
Votes
2
Found in
2017.4
2020.2
2020.2.0a2
Issue ID
1225679
Regression
No
DX12 performance is significantly worse when compared to DX11
How to reproduce:
1. Open the attached project ("DX12-performance.zip")
2. Open the repro scene ("SampleScene")
3. Set DirectX11 as the main Unity Editor Graphics API
4. Enter Play Mode
5. Observe runtime statistics
6. Set DirectX12 as the main Unity Editor Graphics API
7. Enter Play Mode
8. Observe runtime statistics
Expected result: DirectX11 and DirectX12 runtime statistics don't differ a lot
Actual result: DirectX12 runs at the quarter of the DirectX11 speed
Reproducible with: 2017.4.37f1, 2018.4.18f1, 2019.3.4f1, 2020.1.0b1, 2020.1.0a2
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
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a12