I have all my tweaks in an autoexec.cfg file in etmain, and it only loads/sets the settings (i.e. r_picmip, cg_atmosphericeffects, etc…) about half the time when I boot up ET. However, about 1/2 the time it just doesn’t load/set the settings (or sometimes it loads only certain settings). It seems to be the video settings that don’t load all the time (in fact, I don’t recall anything but video settings that haven’t worked right). I’ll even try typing /exec autoexec.cfg in the console and it still doesn’t work. I did notice when ET loads sometimes it says “vid_restart unknown command” (which is the last line in the autoexec file) . I don’t think it is something wrong with the config file itself because it does work sometimes. I am stumped. Sorry if I didn’t make much sense, I am not familiar with the correct terms when dealing with this subject.
autoexec.cfg not so auto?
It might help to make a batch-file, which is described in the following thread: http://www.splashdamage.com/forums/viewtopic.php?t=3883
your autoexec may or may not get execed, depending on what server browser you use, and what mod the server you join is running. Getting it to really run all the time is hard.
If your game browser starts the game with +fs_game for mod servers, then ET will look for the autoexec in the mod directory, rather than your ET main. I believe All Seeing Eye does this. A simple way to work around this is to put your main .cfg file in etmain, and then put an autoexec.cfg in each of your mod directories, and have it just exec your main .cfg. ASE also has an option to exec a specific .cfg whenever you join a server.
If your game browser does not (pathfinder, for example), or if you used the in game browser, then your autoexec will be run, but the settings might be lost when you connect to a mod server. There is no really good workaround for this, except to manually exec your cfg after you join.
The batch file thing Cerebrate mentions won’t help any of this, but it will help other issues you get when joining mod servers. You could make your batch file always execute a specific .cfg, and ignore your autoexecs completely.
well, I created a batch file and put an autoexec file in each mod folder, but it still doesnt work 100% of the time. However, most of the time it does work so I can live with having to execute it via the console in game when it doesn’t.
I’ve found it’s just easier to go and edit the main config.cfg file, then copy the new config to the shrub folder profile too…