Search Issue Tracker
In Progress
Fix In Review for 6000.3.X
In Progress in 6000.0.X, 6000.4.X, 6000.5.X
Won't Fix in 6000.2.X
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.56f1
6000.2.1f1
6000.3.0a5
6000.4.0a1
6000.5.0a1
Issue ID
UUM-114407
Regression
No
Screen.SetResolution() ignores width and height parameters when switching from Fullscreen to Windowed mode
Reproduction steps:
1. Open the attached “IN-110600.zip” project
2. Build and Run the project (File > Build and Run)
3. In the Player, enable the “Fullscreen” checkbox
4. In the resolutions dropdown, select the lowest available resolution in the list (e.g., 1280x800)
5. Disable the “Fullscreen” checkbox
6. Observe the resolution of the Player
Expected result: The Player window should be automatically set to 1920x1080 resolution (or whatever the first windowed resolution option is)
Actual result: The Player window remains at the previous fullscreen resolution (1280x800)
Reproducible with: 2023.2.0a5, 6000.0.56f1, 6000.2.1f1, 6000.3.0a5
Reproducible on: Windows 11
Not reproducible on: macOS 15.5 (M1 Max), macOS 15.3 (M2 Ultra)
Note:
- Does not reproduce if more than one monitor is used while reproducing
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (6000.2.X):
Thank you for reporting a bug to Unity.
While we are aiming to fix this issue in future releasesof Unity, there are no more releases of the 6000.2 stream planned so we are closing this particular port of the bug report.