Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2020.3.46f1
2021.3.22f1
2022.1.13f1
2022.3.0f1
2023.1.0b10
2023.2.0a8
2023.3.0a3
Issue ID
UUM-31506
Regression
No
Screen.resolutions returns resolutions that include the notch area when called on Macs with a notch
Reproduction steps:
1. Open the attached “ResolutionRepro” project
2. Go to File > Build Settings
3. Make sure that "Development Build", "Script Debugging" and "Wait for Managed Debugger" are checked and press “Build and Run”
4. When the Player prompts, attach the Debugger to the build through Console Window by pressing Editor and then the Player
Expected result: Resolutions without the notch area are reported
Actual result: Resolutions with and without the notch area are reported
Reproducible with: 2020.3.46f1, 2021.3.22f1, 2022.2.13f1, 2023.1.0b10, 2023.2.0a8
Reproducible on: macOS 13.2.1 (M1 Max, with notch)
Not reproducible on: macOS 12.6 (AMD, without notch)
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
- Player crash when switching focus in Exclusive Fullscreen mode with DirectX 12
- 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
Resolution Note:
Screen.resolutions API is working as designed, because it returns all full-screen resolutions that the monitor supports and these values are obtained directly from the display.
Resolution Note (2023.3.X):
Screen.resolutions API is working as designed, because it returns all full-screen resolutions that the monitor supports and these values are obtained directly from the display.