Search Issue Tracker
Duplicate
Votes
1
Found in
2021.2
2021.2.0b13
2022.1
Issue ID
1374016
Regression
No
Screen.MoveMainWindowTo method often fails to switch monitors when the Player is for OSX Standalone
How to reproduce:
1. Open the user's attached "Display Management Handler 2021" project
2. Select "File -> Build and Run" in the menu bar
3. Select any other monitor in the built project
4. Click the "Apply" button
Expected result: The Player successfully switches to the chosen monitor
Actual result: The Player sometimes animate the switching process, but the project remains on the same monitor
Reproducible with: 2021.2.2f1, 2022.1.0a14
Couldn't test with: 2019.4.32f1, 2020.3.22f1, 2021.1.28f1 (error because of DisplayInfo class is not implemented)
Comments (2)
-
Claytonious
Feb 11, 2022 04:04
Yes, which bug is this a duplicate of? It is so unhelpful to mark as duplicate without linking to the other bug! Argh!
-
VoodooDetective
Feb 10, 2022 19:44
Please provide a link to the original ticket this duplicated so we can follow along.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
This is a duplicate of issue #1400427