Search Issue Tracker
Fixed
Fixed in 2023.2.0a20
Votes
1
Found in
2023.2.0a18
Issue ID
UUM-37965
Regression
Yes
Editor stays on DX11 when changing Graphics API to DX12
Reproduction steps:
1. Create a new Project
2. Open Edit > Project Settings > Player Window
3. Under “Other Settings” uncheck “Auto Graphics API for Windows”
4. In the “Graphics APIs for Window” List drag the “Direct3d12” item to the top of the list
5. Restart the Editor
Expected result: The Editor starts using DX12
Actual result: The Editor does not start using DX12 and stays on DX11
Reproducible with: 2023.2.0a18
Not reproducible with: 2021.3.26f1, 2022.2.21f1, 2023.1.0b19, 2023.2.0a17
Reproducible on: Windows 10
Comments (1)
-
Lionious
Jun 09, 2023 07:32
is that problem getting a fix in the next versions ? if so which version?
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 (fix version 2023.2.0a20):
Fix a bug, where the editor is running DX11, although DX12 is selected.