Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2017.4.0f1
2018.2.9f1
2018.3.0a1
2019.1.0a1
Issue ID
1094263
Regression
No
[Windows][Linux] -screen-quality command argument has no effect on built application
How to reproduce:
1. Open attached project "CommandLineArguments.zip" and scene "SampleScene"
2. In Unity Editor menu, select File -> Build Settings -> Build -> select "Build" folder located in the projects directory (if asks, application name must be "CommandLineArguments")
3. After building the project, go to the "Build" folder and open "StartMedium.bat"
4. In top-left corner observe "QualitySettings.GetQualityLevel(): ..."
Expected result: QualitySettings.GetQualityLevel(): Medium
Actual result: QualitySettings.GetQualityLevel() is not Medium (saves the last quality setting, it will be either Potato or Ultra)
Reproducible with: 2017.4.16f1, 2018.3.0f1, 2019.1.0a10
Not Reproducible on Linux with 2019.3.0a7, 2019.1.0f2
Comments (1)
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
- "Stevedore error: Cannot create artifact ps4-sdk-12_50 using repository unity-internal because that repository has been blocked" error when running "jam ProjectFiles"
- Crash on NVDEV_Thunk when changing VideoPlayer clip source on certain machines
- [HDRP] Forced context-switching occurs when adding an unregistered Custom Post Process to a scene Volume
- Multiple errors are spammed in the Console window when entering “Infinity” value in the Falloff field of a Freeform Light 2D
- Inspector loses focus or Material doesn't update when using GetModifiedMaterial with a Mask component
mngmra
Sep 08, 2021 21:17
Can't make -screen-quality command work on 2019.3.3f1, 2019.4.0f1. Other commands like -screen-fullscreen, etc work just fine