Getting cfg settings to stay in cfg

Post by **Mr.Bios** » Sat Oct 29, 2005 10:26 am

Every time I add or edit things in my config they disappear after the game loads. Simple things like allowconsole, fov and a demo recording script dont stay in my config.

Sometimes they stay in my config and I can use them whwn I start the game but after that they will vanish and now I just have to type the basic things like fov into the console every time I start the game.

Any ideas how to fix this?

Post by **Method** » Sat Oct 29, 2005 11:05 am

You can also add this to the target line of Q4 shortcut:

C:\Program Files\id Software\Quake 4\Quake4.exe" +exec <configname>.cfg

-Method

Post by **Mr.Bios** » Sun Oct 30, 2005 12:26 pm

ok, thanks for the info but im still having a problem with my fov. Even if I add the command to the shortcut the the fov still goes to the default and not what I have defined.

Also.. how can I change the sensitivity for each weapon? I thought id try what I done in q3:- bind "e" "_impulse7; sensitivity 13.3" but that doesnt work.

Post by **DRuM** » Sun Oct 30, 2005 12:33 pm

Mr.Bios wrote:ok, thanks for the info but im still having a problem with my fov. Even if I add the command to the shortcut the the fov still goes to the default and not what I have defined.

This my shortcut target line which allows the console, loads straight to the menu screen, and also saves my fov.

"C:\Games\Quake 4\Quake4.exe" +seta com_allowConsole 1 +disconnect +set g_fov 110

After where it says Quake4.exe in your path, paste:

+seta com_allowConsole 1 +disconnect+set g_fov 110

and leave spaces before each '+' That might make the difference. Press apply.

Post by **d3fin3d** » Sun Oct 30, 2005 4:36 pm

No need to mess about with shortcut command lines.

Do this:

1 - Write everything manually into your quake4config.cfg (seta com_allowconsole 1, chat binds, seta g_fov, etc).

2 - Save it, duplicate it and rename it autoexec.cfg

(2a - Copy both quake4config.cfg and autoexec.cfg (which are the same file, just different names) into any mod folders you have and change specific mod variables as you wish.)

3 - Done. Play.

Post by **AmIdYfReAk** » Sun Oct 30, 2005 5:36 pm

I've resorted to the command line thing, and i have tryed the autoexec..

the only thing that is working is infact the command line, and thats why i was wondering if there was another way

Post by **d3fin3d** » Sun Oct 30, 2005 5:38 pm

The autoexec.cfg works fine, you just need to check that the commands are in autoexec.cfg with seta preceeding them.

put:

seta com_allowconsole "1"
seta g_fov "100"

works fine for me, just need to check the commands are there.

Post by **Freakaloin** » Sun Oct 30, 2005 5:39 pm

fov 102 is best...because I'm a moron.

Post by **Scourge** » Sun Oct 30, 2005 5:41 pm

Freakaloin wrote:fov 102 is best...

For you.

Post by **Mr.Bios** » Tue Nov 01, 2005 5:54 pm

Ev erything seems to be working now. Adding seta in front of each line fixed it.

What about the sensitivity thing? How can I change sens fopr each weapon?