Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Unfortunately it looks that way. WC must have broken the user's ability to do this from an .ini.
I get the grass one goes somewhere else, but for the render flags:
[SystemSettings] in Engine.ini does not work
[/script/engine.rendersettings] in GameUserSettings.ini does not work
Steam Launch option -exec "\path\textfile.txt" containing console commands does not work
The last comment or two in threads covering this is usually someone going "I did it right, double checked, and it's not working". Appears they broke this last year sometime, or changed how/where they pull those initial flags from.
Pasting them all into console as one line piped is unfortunately the best option:
r.VolumetricCloud 0 | r.VolumetricFog 0 | r.FidelityFX.FSR3.Enabled 0 | r.FidelityFX.FSR3.QualityMode 0 | r.FidelityFX.FI.Enabled 0 | r.AntialiasingMethod 4 | grass.sizescale 0 | r.Lumen.DiffuseIndirectAllow 0
Except that Lumen doesn't turn off if you do this, and you have to run that one individually.
It's annoying, but not nearly as annoying as how garbage Lumen and FrameGen look.
If someone knows how to actually get render flags to load from an .ini: I'll pin it.
Nice job.