Search Issue Tracker
Fixed
Fixed in 6000.6.0a5
Votes
0
Found in
6000.0.72f1
6000.3.13f1
6000.4.3f1
6000.5.0b4
6000.6.0a2
Issue ID
UUM-139413
Regression
No
Graphics API cannot be changed after switching to UWP build profile when Graphics API is set to an unsupported-by-UWP Graphics API beforehand
Steps to reproduce:
- Create and open a new project
- Open Player Settings and change the Graphics API to Vulkan, restart the Editor
- Open Build Profiles and switch to the UWP build profile
- Observe the active Graphics API at the title bar of the Editor window (should be set to "<Vulkan>")
- Open Player Settings again
- Drag Direct3D11 or Direct3D12 on top to switch the Graphics API
- Observe the Editor
Actual results: Nothing happens
Expected results: The user is asked to restart the Editor to change the Graphics API
Reproducible with versions: 6000.0.0f1, 6000.0.72f1, 6000.3.13f1, 6000.4.3f1, 6000.5.0b4, 6000.6.0a2
Not reproducible with versions:
Can’t test with versions: 2023.1.0a1 (No UWP build profile until 6000.0 stream)
Tested on (OS): Windows 11 Pro (25H2)
Workaround:
1. Switch back to any other build profile
2. Switch to any Direct3D Graphics API
3. Switch to the UWP build profile again
Notes:
- Reproducible with any other Graphics API except Direct3D11 and Direct3D12
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note:
Fixed in 6000.6.0a5
Resolution Note (fix version 6000.6.0a5):
Fixed in 6000.6.0a5