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
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
- Errors and warnings are thrown after installing Visual Effect Graph Learning Samples
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