Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Votes
0
Found in
2021.3.31f1
2022.3.11f1
2023.1.16f1
2023.2.0b14
2023.3.0a10
6000.0.0b11
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on RenderBufferManager::Textures::GetTempBuffer when rendering a specific scene
- The Inspector header is incorrectly displayed when scripts are recompiled while a Scriptable Object instance is selected
- NullReferenceException is thrown when overriding the UxmlObjectReferences in template instances
- Shaders created with Shader Graph generate a large amount of shader variants and cause slow build times when using a baked lightmap in BIRP
- Shader Graph Matrix property produces random output values when SRP Batcher is enabled
Add comment