Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
5
Found in
5.6.1f1
Issue ID
925925
Regression
No
Standalone Player command line argument "-adapter" does not choose an alternate monitor
Steps to reproduce:
1. Create a new project
2. Build for Standalone
3. Create a shortcut to the .exe
4. Add the argument "-adapter X" to the shorctut
5. Launch the build
Expected result: build launches on the monitor corresponding to the X number
Actual result: build launches on the main monitor, ignoring the argument
Reproduced on 5.4.5p1. 5.5.4f1, 5.6.2p1, 2017.1.0f2, 2017.2.0b1
Verified FIXED 2017.3.0a3
Comments (3)
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
- Crash on object:runtime_invoke_void__this__ when opening a specific project
- Circle-shaped rendering artefacts visible in Local Volumetric Fog boundaries box in Scene view when Fog Distance is lower than 1
- “Fog Distance” property name and description is unclear in the Inspector window
- Crash with multiple stack traces when using Burst-Compiled Span.Fill()
- Broken compute shaders propagate via the cache server
M-Hanssen
Oct 04, 2017 12:48
You say "Verified FIXED 2017.3.0a3" Is this the most early release that this problem will be fixed?
M-Hanssen
Aug 28, 2017 07:29
Why is this fix still in review? And why isn't there any patch available yet?
M-Hanssen
Jul 19, 2017 14:16
Having the same problems