help my r1q2 is not saving video settings ever

[dawk]

my r1q2 just saves the name and model and a few other settings but doesnt keep the video settings the same... help

[ToxicMonkey^MZC]

Find your config file in baseq2 folder, edit it with Notepad to your liking, then save it and write protect it.  Maybe?

Interesting topic.  I've noticed that sometimes Q2 saves your config and sometimes it doesn't.  My config is partially made up from temporary binds that Q2 decided to keep, although most of the time it doesn't keep them.  If we know what makes Q2 save the config, this could be another solution.

[Mask]

Just create a file called autoexec.cfg in your baseq2 folder and add whatever's not saved in your config.cfg

Here's what mine says, among other things:

//           ____________________
//          (    Video Settings  )
//           ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
set hand "2"
set cl_gun "0"
set fov "110"
set vid_ref "r1gl"
set gl_driver "opengl32"
set cl_particles "1"
set gl_polyblend "1"
set gl_mode "8"
set gl_modulate "4"
set intensity "2"
set vid_gamma "0.700000"
set gl_texture_lighting_mode "0"
set r_maxfps "125"



******
about gl_mode:

    Type: Toggle

    Default: 3

    Description: Toggle the screen resolution mode.

    Values:
    0 - 320 x 200
    1 - 400 x 300
    2 - 512 x 384
    3 - 640 x 480
    4 - 800 x 600
    5 - 960 x 720
    6 - 1024 x 768
    7 - 1152 x 864
    8 - 1280 x 960
    9 - 1600 x 1200

This should help.

[|iR|Focalor]

The problem is:

You are obviously editing your video settings while logged into a server. If you start up Q2, start a single player game, THEN edit your settings, THEN shut down the game, all of your changes should remain saved in your main baseq2 game configuration file. Usually, if you change any settings while playing on a server, it will OFTEN not save those changes.

[peewee_RotA]

Interesting topic.  I've noticed that sometimes Q2 saves your config and sometimes it doesn't.  My config is partially made up from temporary binds that Q2 decided to keep, although most of the time it doesn't keep them.  If we know what makes Q2 save the config, this could be another solution.

config.cfg gets created in the current game folder that you are using. The default game folder being baseq2, the config.cfg in baseq2 get's loaded every time that quake 2 loads. Everytime that quake 2 exits, it overwrites or creates a config.cfg in the current game folder. So if you were playing wod, then the game would create a config.cfg in your wod folder. If one already existed, it would overwrite it. That means that those changes never make it into the config.cfg in baseq2.

The only config.cfg that ever gets loaded is the one in baseq2, which is what loads at quake 2 start up. However, if you create an autoexec.cfg in your mod folders it will be executed every time that you change games. So the autoexec.cfg in your baseq2 folder will load as well as the config.cfg when quake 2 starts. When you connect to a mod server, the server tells the client to change mod directories, your game basically reloads while it gets the data from the mod directory and will execute the autoexec.cfg in that mod folder before loading the map that the server is hosting.

So that's really all just a long and drawn out way of saying that any changes you make while in a game hosting a mod will not be saved automatically. You have to make an autoexec.cfg in that mod folder.



Also focalor is probably addressing the problem at hand. If you are going to make changes to your video settings by using the quake 2 menus, always load a single player game first and make the changes. Otherwise do it manually by looking at the values already in your config.cfg and checking other documentation like: http://console.planetquake.gamespy.com/commands/quake_2.html

[APKIS]

Just Quit quake2 throw  main menu. If you type " quit " in console, it won't save your settings. That works for me very well even i am using cfg for sure  

[QwazyWabbit]

Quitting from the menu or just typing quit in the console perform the same functions. Com_Quit and Sys_Quit both call CL_Shutdown and CL_Shutdown calls CL_WriteConfiguration and it writes your current bindings into the "config.cfg" in the current mod folder. No matter what mod you are playing, when you quit, a new config.cfg is written into the current mod's gamedir. It does not matter (to r1q2 and stock Quake2 at least) whether you use "quit" in console or quit from the menu.

At startup, Quake2 client will load three files in the following order, "default.cfg" from the baseq2 folder, "config.cfg" from the baseq2 folder, and once you are connected to a server, "autoexec.cfg" from the gamedir folder where "gamedir" is the folder for the mod you are playing. It knows the gamedir folder name because it has already received the server cvarlist and it knows the contents of the "game" cvar.

Not surprisingly, most people don't know about default.cfg.

The general idea was to allow common default settings to be loaded into the client from default.cfg, this would be where you could put your video or other settings that you always wanted to start off with in all mods.

As you can see there is slight problem here. Config.cfg is always loaded from the baseq2 directory. A new config.cfg is written to the directory of the current mod directory. Your changes don't get communicated to the next startup unless you manually copy them.

What I like to recommend is to always configure your settings in "autoexec.cfg" and address all of your favorite settings there. If you make changes to settings in-game and you want them to be your startup settings, copy them from config.cfg into baseq2/default.cfg and make changes in moddir/autoexec.cfg for each mod.

[poopoppa]

what if you quite with F10?

[APKIS]

Quitting from the menu or just typing quit in the console perform the same functions.

Tried to check the "difference" on 16 computers, all of them acted as i explained. Quitting from Menu saves the settings. Quitting from console- doesn't. 

Didn't read your all post, but maybe you explained why its that. Maybe i got some extra cfg files or something else in q2 or q2/baseq2 dir

[jägermonsta]

Yeah, had a similar problem. It was the config.cfg file that would fuck up all my configuration changes. What I did was create a custom config to my liking then delete the config.cfg. Load up Quake and exec my custom config, set my video settings and such then Quit through the menu. This would create a config.cfg with all the settings I wanted to stick. There may also be config.cfg files for each mod folder, I would overwrite those with my good config.cfg.

[R1CH]

Quitting from the menu or just typing quit in the console perform the same functions.

Tried to check the "difference" on 16 computers, all of them acted as i explained. Quitting from Menu saves the settings. Quitting from console- doesn't. 

Didn't read your all post, but maybe you explained why its that. Maybe i got some extra cfg files or something else in q2 or q2/baseq2 dir

There is no difference between menu and console, unless you are using some weird modified Q2 client.

[The Happy Friar]

launching & connecting to a server via command line (ie qtracker) seems to not run the autoexec.cfg in the mod/base folder, it just runs the defaults in baseq2.  I solved this by putting "+exec autoexec.cfg" in my q2 command line paramaters.

since it won't run the local mod's config files it makes sense it is always wrong.

[APKIS]

Try with full screen. Make your screen small. Quit from console. Load quake2 (the exact one which you used to change video settings) it loads in full screen. Do the same stuff and quit from Menu. Small screen appear next time you launch that quake2.

Dunno, but that happens to me

[R1CH]

On a related note, I hate how Q2s config system doesn't save settings intuitively. I've been thinking of a way to fix this, but it would break backwards compatiibilty with the current config system. The solution is to simply stop cross-mod config pollution - eg every time the game is changed, all binds, cvars, aliases, etc are wiped out and a new config.cfg loaded from the mod dir. If the mod is changed mid-game, write the old mod config.cfg before loading the new mod config.cfg. In addition, preserve all user-added cvars, aliases and other settings that are not usually preserved.

This does pose a number of problems though, since if you run Q2 +connect serverIP as many people do, the game will first startup with your baseq2 config before loading your mod config. If the baseq2 config has window mode for example and the mod config is fullscreen, there will be an ugly res change every time you start Q2, and it may not be immediately obvious why this is happening since most people don't play baseq2.

[Whirlingdervish]

there can also be problems with certain mods determining an individual player ID if your config changes your name because you went from one mod folder to the next by switching servers.

I found that if you have 2 configs with different names, wallfly will completely ignore you if you try to use the invite or goto features.


For anyone here, I'd recommend taking the stock q2 config.cfg and making a copy.

Now open the copy, put in "unbindall" in the beginning of it, and rename it to yourplayername.cfg
Make any changes you want in this file, add some of the client specific settings and binds/aliases you like, then save it in your Quake 2 folder.

Now make a .txt file, call it autoexec.cfg and put in the line "exec ../yourplayername.cfg". put this in your baseq2 folder and one in all of your mod folders.

now pretty much anything in config.cfg will be ignored when you load q2.


If you want mod specific configs, just make a copy of the yourplayername.cfg in your quake 2 folder, edit in the stuff you want for that mod, add a suffix to the end of the filename like so: yourplayername_insta.cfg and then change the line in that mod's autoexec.cfg to match the new config name.

This way all your configs are seperate from the stock ones or mod ones, and you can run multiple different configs for different mods with ease.

Just make sure they all have the same playername if you're gonna be using goto