login
|
language
Български (Bulgarian)
čeština (Czech)
Dansk (Danish)
Nederlands (Dutch)
Suomi (Finnish)
Français (French)
Deutsch (German)
Ελληνικά (Greek)
Magyar (Hungarian)
Italiano (Italian)
日本語 (Japanese)
한국어 (Korean)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese)
Português-Brasil (Portuguese-Brazil)
Română (Romanian)
Русский (Russian)
简体中文 (Simplified Chinese)
Español (Spanish)
Svenska (Swedish)
繁體中文 (Traditional Chinese)
ไทย (Thai)
Türkçe (Turkish)
Українська (Ukrainian)
Help us translate Steam









Since every programm makes its own startparameter, i highly doubt that.
now having trouble undoing it
PC Specs:
Processor Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz, 3201 Mhz, 4 Core(s), 4 Logical Processor(s)
Installed Physical Memory (RAM) 8.00 GB
Graphics Card: GeForce GT 730
Evolution: from 15-25 fps to 35-50 while keeping the same ingame settings.
I'd just like to say THANK YOU so much for putting this guide out to the public, because it allows low end PC gamers like myself to play this game. So again, thank you.
THANKS
I use some console commands that help me as well, maybe you can add them here.
One is "sg.effectsquality 0" which disables mainly the refraction in the water.
Instead of "distance field shadowing" one can try medium in "general shadows" or "sg.ShadowQuality 1" (does the same), then "r.shadow.distancescale 1.5" and "r.shadowquality 3". That renders the shadow pretty far and blurs it enough to be acceptable to me.
To see the time spent on the game thread (cpu), the render thread(cpu) and the gpu per frame use "stat unit". There you can see if you are cpu or gpu bound.
The rest is possible in the settings menu. sky quality can be at 0% and ground clutter at 33%. post processing effects like ambient occlusion and motion blur cost a lot.
The main problem with performance currelty seems to be the landscape, which is drawn very far. You can test that by using "show landscape" to toggle it on and off to see the difference.