Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.7f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1162730
Regression
No
No command line argument for running the Standalone in Exclusive Fullscreen mode
How to reproduce:
1. Open attached project "Exclusive.zip"
2. Build the Standalone
3. Create a shortcut of the .exe
4. Add a command line argument -window-mode exclusive or -screen-fullscreen 2, apply changes
5. Run shortcut
6. Observe top-left corner of the Standalone
Expected result: the Standalone runs in exclusive fullscreen mode
Actual result: the Standalone runs in regular fullscreen mode
Could not test with: 2017.4 due to "Screen" class not implemented yet
Reproducible with: 2018.4.3f1, 2019.1.9f1, 2019.2.0b7, 2019.3.0a7
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 (2019.3.X):
Unfortunately, the only workaround for you would be to implement some logic via script:
https://docs.unity3d.com/ScriptReference/Screen.html
https://docs.unity3d.com/ScriptReference/Screen-fullScreenMode.html
You could also try creating your own command line arguments, I have found an interesting article here:
https://answers.unity.com/questions/138715/read-command-line-arguments.html