Search Issue Tracker
Fixed in 2023.1.0b16
Fixed in 2023.1.X, 2023.2.X, 2023.2.0a8
Votes
0
Found in
2023.1.0b8
2023.2.0a6
Issue ID
UUM-30237
Regression
Yes
[DirectX12] Different behaviour to DX11 when vsync is disabled in Editor
To reproduce:
1. Open repro project
2. Open Window > General >Test Runner and double-click the test 'PerformanceTest'
3. Open Window > Analysis > Performance Test Report and click 'Refresh'
4. Observe the median FPS
Expected result: Median FPS is similar between DirectX11 and DirectX12
Actual result: Median FPS is lower on DX12 compared to DX11
(From local test:
DX11 ~320 FPS,
DX12 ~120 FPS)
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 2023.2):
DX12: Fixed case where vsync is off to allow tearing like on DX11.