quick question

[Agent 420]

when i play q2 i have to enter cl_maxfps everytime. if i don't i get the disconnect icon up top....i type in cl_maxfps 30 and it's fine.
never used to do this but for some reason it wont save my fps.
 

[[BTF] Reflex]

Put it in your cfg,  then make it read only.


If it still is screwy,  copy the config.  Rename it like 'rabid.cfg',  edit it to your hearts content,  save it.

now in the game do 'exec rabid.cfg'

[|iR|Focalor]

If you don't know how to manually edit your main config file, do this instead:

1. Start R1Q2
2. In console, type "set cl_maxfps 30"
3. Exit game to desktop

This should save that setting your main config and use it each time you start the game. All good.

[QwazyWabbit]

Always edit autoexec.cfg, not config.cfg.

The config.cfg gets re-written by the game when you exit. It contains the values as they were at the time of exit. You can tweak the game, exit and copy-paste the new variables into an autoexec.cfg file but you should refrain from editing config.cfg itself.

Use autoexec.cfg as your main configuration. Some players use one in the baseq2 folder as a master and then use one in each mod folder to override the master per mod but I find it hard to track changes that way. I keep basic stuff in autoexec.cfg in each mod and use smaller .cfg files to do special binds. You can write "exec somefcfg.cfg" in the autoexec.cfg to add different config features just like calling a subroutine.

[|iR|Focalor]

Always edit autoexec.cfg, not config.cfg.

He's obviously new and has no clue what all that means.

And I don't have any config named autoexec.cfg... at all. I'd venture to say that most people don't.

[quadz]

Always edit autoexec.cfg, not config.cfg.

He's obviously new and has no clue what all that means.

Hmm.  Newbie or not, it's the correct advice.

I cringe whenever I see newbies advised to edit their config.cfg.  There's a reason that file says at the top, "// generated by quake, do not modify".

autoexec.cfg is the file that Q2 automatically exec's, but will not modify.

Regards,

[Whirlingdervish]

I'd say the real downside of editting your config.cfg is that if you break it, you may have to reinstall to get a stock one, unless you were smart enough to back it up somewhere.

for the most part, if you've never touched your config.cfg, you can delete the autoexec.cfg just in case you broke a setting and voila! your q2 will work again.

[|iR|Focalor]

Always edit autoexec.cfg, not config.cfg.

He's obviously new and has no clue what all that means.

Hmm.  Newbie or not, it's the correct advice.

I cringe whenever I see newbies advised to edit their config.cfg.  There's a reason that file says at the top, "// generated by quake, do not modify".

autoexec.cfg is the file that Q2 automatically exec's, but will not modify.

Regards,

Like I said, I don't have an "autoexec.cfg", and never have... that I recall. I was under the impression that if one were to simply delete the "config.cfg" in baseq2, Quake2 would write a new default one to that location upon starting the game.

[Whirlingdervish]

hrm... disregard my above comment about getting a new stock config.cfg.

I just tested it and Foc's right, it writes a new stock config.cfg if you delete all your .cfg files and try to run quake2.



In other news, I hadn't seen it bone stock for a long ass time.. wow q2 is dark.

 

[|iR|Focalor]

See, us dumb rednecks know us some shit.

[quadz]

Like I said, I don't have an "autoexec.cfg", and never have...

Yes, you won't have an "autoexec.cfg" until you create it yourself.

If you're editing your "config.cfg", you're fighting the design of Q2.

The "config.cfg" file is generated by Q2 and is not intended to be edited.

If "autoexec.cfg" exists, it is exec'd by Q2.  The purpose of autoexec.cfg is to provide a file where your custom config can be safely edited, unlike config.cfg.


Regards,

[m0n0LiTh0]

When you got a Wod mod back in the day , it came with a stock autoexec. cfg so that all your hook , decoy, tractor beam , laser, jetpac , so forth so on binds were already basically set up so you where ready play..

You just modify to suit what ever.. Was easier for n00bs , but still was always "this don't work , that don't work , what do i do now?" blah blah blah..
                           
 

[Whirlingdervish]

nice to see that you're still alive and kickin mono!

 

[QwazyWabbit]

Always edit autoexec.cfg, not config.cfg.

He's obviously new and has no clue what all that means.

And I don't have any config named autoexec.cfg... at all. I'd venture to say that most people don't.

To which noob are you referring?  Certainly not me.

All people (by default) didn't have autoexec.cfg. It was one you had to write yourself, usually by copying the config.cfg and modifying the copy yourself. Editing config.cfg is asking for trouble and the reason all the newbs keep saying write-protect the file once you edit it. It gets wiped out each and every time you exit the game otherwise.

The Quake 2 client, by design, writes a new copy of config.cfg into the current mod folder whenever the client terminates, by "quit" command, or by any error condition that causes the client to terminate via the CL_Shutdown function.

When a client session starts up, once the game file system is initialized the first config file it executes is "default.cfg", then config.cfg (if any), then it executes baseq2/autoexec.cfg, if any and then moddir/autoexec.cfg, if any. So anything set in autoexec.cfg for the current mod you are playing automatically overrides any settings you made in config.cfg. Any changes you make to variables in the console will be recorded in config.cfg when you exit the client with the quit command.

Somewhere in Quake II's original documentation is the instructions to edit autoexec.cfg, I don't remember where I saw it anymore but that's how I originally discovered how to do it.

[Slayer :D]

Here is my instructions on how to edit a configuration (.cfg) file. You can do this to any config except config.cfg.

http://tastyspleen.net/quake/forums/index.php?topic=11859.msg122262#msg122262

I know it is long, but hey!