Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2021.1.X
Votes
0
Found in
2021.1
2021.1.0b2
2021.2
Issue ID
1306126
Regression
Yes
[DX12]Screen.SetResolution causes "Couldn’t switch to requested monitor resolution" error
Reproduction steps:
1. Open attached project "Resolution.zip"
2. Build and Run
3. Observe build
Expected result: No error
Actual result: "Switching to resolution 2560x1440 failed Screen: DX12 could not switch resolution (2560x1440 fs=1 hz=0)" error
Reproducible with: 2021.1.0b2, 2021.1.0b3, 2021.2.0a2
Not reproducible with: 2019.4.18f1, 2020.2.2f1, 2021.1.0b1
Could not test with: 2018.4.31f1 (compilation errors)
Note: only reproduces in non-development build.
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
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
- [macOS] "Add Component" button is broken when the Editor is moved to a different MacOS workspace
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a4
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b6