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
- Error ‘cannot use casts on l-values’ when a variable is assigned inside a second-level nested if statement before being used in a conversion
- "You cannot save to an invalid folder" warning dialog box is shown when canceling Tile Palette creation
- Global Volume visual details are blurred when Tonemapping mode is set to any other than 'ACES'
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
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