Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.31f1
2022.3.11f1
2023.1.16f1
2023.2.0b14
2023.3.0a10
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
7000.0.0a1
Issue ID
UUM-53531
Regression
Yes
"DX11 Could not switch resolution" error in Windows Standalone Player after launching and trying to resize the window
Steps to reproduce:
1. Open the attached user's project "UnityTestSwitchResolutionDX11.zip"
2. Download the attached "unitywin.zip" and extract it
3. Perform a Non-Development Standalone Windows Player Build
4. Navigate to "C:\Downloads\unitywin" and open "gpf_config.xml" in a text editor
5. Modify the "setExecPath" to point to the built Player exe path
6. Launch "GPF64.exe" binary
7. Observe the error once the Application launches
Expected results: Hosting window can be resized without issues
Actual Results: "DX11 Could not switch resolution" error in Windows Standalone Player after launching and trying to resize the window
Reproducible with: 2020.3.33f1, 2021.3.31f1, 2021.3.29f1, 2022.3.11f1, 2023.1.16f1, 2023.2.0b14, 2023.3.0a10
Not reproducible on 2020.3.32f1
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
Notes:
-See attached "ScreenResolutionError.png" for the error message
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.