Search Issue Tracker
Fixed
Fixed in 2021.3.31f1, 2022.3.10f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a1, 2024.1.0a1
Votes
2
Found in
2021.3.23f1
2022.3.1f1
2023.1
2023.2.0a10
2023.3.0a1
Issue ID
UUM-33795
Regression
No
[Windows] Incorrect display selected when spanning multiple displays
Screen.MoveMainWindowTo misbehaves when window is windowed and spans several monitors
To reproduce this issue, arrange your monitors vertically in windows display settings. The display with the smallest resolution should be the top one. Then, start the build with -window-width and -window-height parameters that span the entire desktop virtual space, and use "-monitor x" command to specify which display the game should be on. Observe that no matter which monitor you specify, the window top left corner will never be on the top monitor.
-
globacore
Feb 01, 2024 20:27
This issue is still happening in version 2022.3.10f1
We have apps not starting on the main Windows display when spanning across multiple displays in windowed mode. We have different display layouts set up in Windows display settings:- 5x 1080p displays, portrait orientation, 1x5 layout, command line arguments: -popupwindow -screen-fullscreen 0 -screen-width 5400 -screen-height 1920
- 7x 1080p displays, portrait orientation, 1x7 layout, command line arguments: -popupwindow -screen-fullscreen 0 -screen-width 7560 -screen-height 1920
- 4x 1080p displays, landscape orientation, 2x2 layout, command line arguments: -popupwindow -screen-fullscreen 0 -screen-width 3840 -screen-height 2160We tried many different things to fix the issue and the only thing that seemed to work, at least temporarily, was to set a different display as the main display and delete the Windows registry key UnitySelectMonitor which had the value of 0 but still didn't start the app on the correct display. After some time, the app would not start again on the first display and we had to delete the registry key again.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2023.3.0a1):
Fixed UUM-33795
Graphics: Fixed game window display position on-screen for additional uncommon multi-monitor layouts