Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.3.X, 2022.1.X
Votes
0
Found in
2019.4
2020.3
2020.3.26f1
2021.2
2022.1
2022.2
Issue ID
1401606
Regression
No
Unity Window not launching from specified hardware display when using command line arguments
How to reproduce:
1. Open the attached project "ReproProject.zip"
2. Open "SampleScene" Scene
3. Build the Project (File > Build Settings... > Build)
4. Open the command-line interpreter (cmd) and navigate to the folder where the Project is built
5. Launch the built application using this command: "ReproProject -monitor 2 -screen-fullscreen 0 -window-mode -screen-width 3840 -screen-height 1080"
Expected result: The Player build launches from the second monitor
Actual result: The Player build launches from the first monitor
Reproducible with: 2019.4.36f1, 2020.3.30f1, 2021.2.15f1, 2022.1.0b10, 2022.2.0a7
Tested on: Windows 10, dual 1920x1080 monitors
Notes:
- Not reproducible on MacOS
- The issue is reproducible if the second monitor is set as primary
- The resolution should be set to max (native) on both monitors
- If using different size monitors set the screen width to monitor1 width + monitor2 width and set the screen height to the height of the biggest monitor
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
- Prefab's scripts are constantly reloaded when trying to enter multiple digits or characters into public fields on custom scripts consecutively
- Crash on mono_g_hash_table_find_slot when entering Play Mode
- [iOS] Crash when pressing "Done" on the keyboard layout
- Sprite Atlas remains loaded in memory after scene change or unloading assets
- Decompressing a DeflateStream under IL2CPP misses a few bytes
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a9
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0f1
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.2f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.34f1