Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.4
2019.4.11f1
2021.1
Issue ID
1293614
Regression
No
Player resolution set to diplay resolution when calling Screen.SetResolution with values larger than current display resolution
How to reproduce:
1. Open the attached project (ScreenSize.zip)
2. Make sure the "Sample Scene" is open and press Ctrl+B to build and run the project
3. In the Player press "G" to enter fullscreen window mode and set the resolution to 4000x3000
4. Observe the current resolution
Expected result: The current resolution is 4000x3000
Actual result: The current resolution is your display's resolution
Reproducible with: 2018.4.29f1, 2019.4.15f1, 2020.1.14f1, 2020.2.0b13, 2021.1.0a6
Not reproducible with:
Notes:
1. Reproducible on Ubuntu 18.04 and Windows 10
2. Same behavior reproducible with exclusive fullscreen and windowed modes
3. If after setting the 4000x3000 resolution in windowed mode, it is set again, then the Player's resolution correctly gets set to 4000x3000
a. Works correctly the first time on 2018.4.29f1 and 2021.1.0a6
b. On Windows 10 the resolution never gets set to 4000x3000
4. The Screen.width and Screen.height properties don't update on the same frame as the SetResolution call
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
we are not sure what the user is trying to accomplish by setting a resolution higher than what the monitor can support. The current implementation clamps the display width to the maximum that the screen can support if the provided resolution is greater than that. So, we are closing as Wont-fix.