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. To change the colors, you'd have to copy the two lines from below and overwrite the top two lines of the file.It is used because it preserves your configuration. Maybe similar can work for you so you can remark within the file as you see fit.
I need to do a bit more testing, but so far, I've got a few meter color settings below the TEST line and they aren't executed when I start the game/round. This seems to make the last 'command' be ignored, but it also seems to ignore the remainder of the file. In my testing with the autoexec.cfg file, after all of the commands I put TEST on the next line. No thanks, I'd like to be able to store everything in one file since it's only going to be a few changes. When you have chosen your own colors or copied the codes that some of us have provided, and you like the color contrasts, save that file in a safe place so you do not need to create it again. Now you have the color scheme you want for your 3click meter. After you have completed these steps, right click the new autoexec.cfg file, copy it then navigate to the Config Folder in Perfect Golf. You should have a blank file, not a text file. Important Note: Make sure your swing choice in the game is set to Swing Meter for the new autoexec.cfg to work. Here is the Click Path: C:\Program Files (x86)\Steam\steamapps\common\Perfect Golf\Config Type in the file name autoexec.cfg then save the file On the top left of Notepad (File), click Save As.ĥ. Where the field says File Type, choose All FilesĤ. Copy and paste the color scheme you want for your meter. We all have to make one manually, then copy and paste it into the Config Folder.Ģ. There is no autoexec.cfg file in the Config Folder.
0 kommentar(er)
