Search Issue Tracker
Third Party Issue
Votes
1
Found in
2021.2.19f1
2022.1.1f1
2022.2.0a13
Issue ID
UUM-643
Regression
No
Screen.MoveMainWindowTo API often fails to switch fullscreen Player between screens on Mac OSX with specific monitors
How to reproduce:
1. Open the user's attached "1109810 - MoveMainWindowTo" project
2. Build and Run the "SampleScene" Scene
3. Select any other monitor in the Player
4. Click the "Apply" button
Expected result: The Player successfully switches to the chosen monitor
Actual result: The Player sometimes animates the switching process, but the project remains on the same monitor
Reproducible with: 2021.2.17f1, 2022.1.0b13, 2022.2.0a9
Couldn't test with: 2019.4.37f1, 2020.3.32f1 (API isn't available)
Note: The issue seems to be reproducible with a specific monitor configuration.
Reproducible with:
- Dell P2419H
- Dell U2719ВС
- Dell U2719D (rarely)
- Dell U2719DC (considered to be the most reproducible one, however, in some cases it doesn't reproduce)
- HP 24MQ
- Lenovo ThinkVision P27H
Not reproducible with:
- HP Z27k G3
Comments (1)
-
Zenoversion
May 25, 2022 20:51
I have been able to reproduce this problem on both macOS 12.4 and in Windows 11 using a Dell S2722QC. I've only seen the problem when using borderless fullscreen, not in a window.
As a workaround, switching to windowed mode before moving to another monitor, and then going back to fullscreen mode afterwards, is working for me. However, in macOS (on my specific test setup, at least), waiting any fewer than 9 frames between MoveMainWindowTo and SetResolution still results in the bug occurring. The extra wait frames do not seem to be necessary for the workaround to work in Windows.
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
- "Volume" Component documentation link is missing
- GUI.TextField cursor is misaligned from text when setting Content Offset on GUI Skin
- The beginning of the Animation doesn’t start at the correct position when it's being enabled through a Trigger event and the Physics Simulation mode is set to "Update"
- Values are cut off between Visual Scripting Node links when in Play mode
- UI Toolkit Style is inconsistent when using Style Classes named using digits
Resolution Note:
This is a macOS issue.