Search Issue Tracker
Won't Fix
Unknown (hidden) 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X
Votes
0
Found in
2020.3.41f1
2021.3.13f1
2022.1.23f1
2022.2.0b15
2023.1.0a19
Issue ID
UUM-19044
Regression
No
The viewport is not set to fullscreen when the MacBook retina display is set as an extended display
Repro steps:
1. Connect the secondary display to a MacBook with a retina display
2. In the settings set the built-in display as an extended display
3. Build and run the project
4. Click the “Activate Second Monitor” button
Expected result: The built-in display is set to fullscreen mode
Actual result: The built-in display has a small viewport in the bottom left corner
Reproducible with: 2020.3.41f1, 2021.3.13f1, 2022.1.23f1, 2022.2.0b15, 2023.1.0a19
Reproducible on: macOS 13.0 (Intel, M1)
Note: On 2022.2.0b15 and higher the the viewport looks like it’s set to fullscreen, but the resolution is wrong
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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Resolution Note:
For content to render properly in a secondary display, there needs to be something assigned to render to it (such as another camera or another canvas with the targetDisplay set to Display 2). Otherwise, the behavior of the second display when activated is undefined. When the camera or canvas is properly set, activating the second display will begin rendering in that display's resolution in fullscreen mode as expected.