Search Issue Tracker
Active
Votes
0
Found in
2022.3.60f1
6000.0.43f1
6000.1.0b11
6000.2.0a7
Issue ID
UUM-100357
Regression
No
Screen.resolutions does not return the correct list of supported resolutions when called on a MacBook Pro with a notch
Reproduction steps:
1. Open the attached “ScreenResolutionTest” project
2. Open the “Assets/Scenes/SampleScene” Scene
3. Enter Play Mode
4. Observe the logged resolutions in the Console
5. Open System Display Settings (System Settings > Displays)
6. Make sure Built-in Display is selected and all resolutions are shown
7. Compare the list of resolution in System Settings to the logged resolutions from step 4
Expected result: All resolutions from System Settings that are higher than the default resolution are logged in the Console
Actual result: Some resolutions are missing (2056x1329, 2056x1285, 3456x2234) or are wrong (3456x2170)
Reproducible with: 2022.1.0a1, 2022.3.60f1, 6000.0.43f1, 6000.1.0b11, 6000.2.0a7
Reproducible on: macOS Sequoia 15.3.2 (15-inch, M1 Max)
Not reproducible on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are thrown on Editor launch when the Project window was locked in the previous project
- Render Pipeline Converter selected asset counter reports one fewer item when using manual selection
- [Android] [Adreno] [WebGL] A light cookie is not rendered with shader compile error when WebGL build is launched on a device with Adreno GPU
- Rigibody sliding over a flat surface that is made of several GameObjects detects false collisions when Collision Detection is set to "Continuous" or "Continuous Dynamic"
- UI Toolkit Label height is incorrectly calculated when using max-width with percentage value
Add comment