The remaining lines contain a command and a corresponding value. If you use autoexec and start the game on the desktop resolution it will overwrite the net_graph position and adjust it for you since you defined it previously in the autoexec. Without usage of autoexec it will be saved in the cloud and overwrite your desktop configuration forcing you to adjust the net_graph position to your 1920x1080 desktop resolution again. Using autoexec enables you to specify settings for your local machine that will not be overwritten if changed by another machine.įor example imaging changing the net_graph position for your laptop resolution. So the config will be rewritten on every startup without the burden of changing the config itself every time. However the autoexec itself is not touched by the source-engine, only read. This is not necessary for settings that have no binding at all like con_enable 1 To circumvent this you need to unbind all keys from the ingame menu and set it once manually in the autoexec. If you open the settings via ingame menu you will still see the old values because those consumerfriendly settings have higher priority resulting in another rewrite of the config.
There is no autoexec.cfg file per default so it needs to be created in the same folder as config.cfg (For example DotA2: …\Steam\SteamApps\common\dota 2 beta\dota\cfg\, some games have it's cfg folder one directory up). AutoexecĪutoexec does execute commands and settings on startup after the cloud sync and rewrites the config. That's why changing the config directly might work for one startup but will be reset after the game closes because the game rewrites the config too at this point. However if you change the settings via ingame menu - let's say controls for example - the config file will be rewritten from scratch. After that the config is loaded into the game but not into the settings. First we need to clarify what happens when you start a source-engine game from steam.Īt startup steam - if activated - loads a config from the cloud and checks back with the local config.
If you edit the config.cfg or use the ingame console directly the settings will only stay until you closed the game.
It is used because it preserves your configuration.
0 kommentar(er)
