Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2023.1.13f1
2023.2.0b9
2023.3.0a4
Issue ID
UUM-49101
Regression
No
The Player is not affected by the custom windowed resolution
How to reproduce:
1. Create a new Unity project
2. In the Project Settings → Player → Resolution and Presentation set the “Fullscreen Mode” to “Windowed”
3. Set the resolution of the window to smaller than the display resolution
4. Build And Run the project
5. Observe the Player resolution
Expected result: The Player matches the set resolution
Actual result: The Player matches the fullscreen resolution
Reproducible with: 2023.1.13f1, 2023.2.0b9, 2023.3.0a4
Not reproducible with: 2021.3.30f1, 2022.3.9f1
Reproducible on: Windows 11 Pro
Not reproducible with: No other environment tested
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
We could not repro this issue using the exact steps described. However, we can repro the issue by changing the resolution between builds when the "Fullscreen Mode" option remains set to "Windowed".
In this case, the behavior is expected because we serialize the last known size to the Windows registry. We only use the size from the player settings if no value has been set from a previous run.
Resolution Note (2023.3.X):
We could not repro this issue using the exact steps described. However, we can repro the issue by changing the resolution between builds when the "Fullscreen Mode" option remains set to "Windowed".
In this case, the behavior is expected because we serialize the last known size to the Windows registry. We only use the size from the player settings if no value has been set from a previous run.