having some trouble with r_picmip

[Oeloe]

If you've got extensive configs for a couple of mods combined in one autoexec, you can quickly run into the "error after max_cvars" error though, causing OSP and Defrag (and others probably) not being able to start up anymore.

[prince1000]

i avoid these problems by doing the following:

delete all cfgs from all directories EXCEPT baseq3 - you don't need to store cfgs in the mod directories.

everytime i load quake i exec my personal cfg - so if i'm playing ra3 i'll type /exec ra3.cfg and then /connect ip

if i join directly from ASE, then i just type /exec ra3.cfg after i've joined - no need to vid_Restart since the vid settings are already transfered to the q3config.cfg in my ra3 directory.

im not quite sure i follow. so do you delete your q3config.cfg (in mod dir) after every game of q3? even after exec-ing mod specific cfgs if you make any vid changes you're still going to have latched variables the next time you start that mod, unless you delete /mod/q3config.cfg.

and i dont think it's bad advice. maybe a little complex to understand for newbs but there's nothing wrong with simplifying your cfgs.

[prince1000]

you could have just added that whoever goes that route needs to remember to back up their shit first.

[[xeno]Julios]

im not quite sure i follow. so do you delete your q3config.cfg (in mod dir) after every game of q3? even after exec-ing mod specific cfgs if you make any vid changes you're still going to have latched variables the next time you start that mod, unless you delete /mod/q3config.cfg.

deleting all cfgs is just a one time maintenance thing.

let's say you've been playing ra3 for a few months, experimenting with diff settings, using other ppl's cfgs, etc.

Somewhere along the line, things are getting a bit screwy. What may have happened is that some of the commands from these various cfgs and settings u used got written to the local q3config.cfg, and they may conflict with other cfgs or settings.

What I'm suggesting is this:

Step 1: create your own personal cfg which is comprehensive and has all the settings u want. Name is something other than q3config.cfg

Step2: delete all cfgs from all folders (do this wisely - don't delete server cfgs which u need if ur hosting a server, etc.)

Step3: put the personal cfg into baseq3

Step4: now whenever u load up quake, type /exec personal.cfg and then connect to the server

I suppose you can do this with autoexecs - i just find it psychologically more satisfying to exec manually - as i remember issues with autoexecs - they didn't seem to exec EVERYTHING - not sure tho.

writeprotecting your q3config.cfg may also help, but not really an issue if you use a comprehensive and personal cfg

[[xeno]Julios]

just upgraded and had this same picmip problem. It's a driver issue.

See this thread:

http://www.esreality.com/?a=post&id=1086503

[CrinklyArse]

cool, removing r_lastValidRenderer from my config worked. :icon14:

[[xeno]Julios]

didn't work for me - my drivers were super anal about imposing image quality on a global level. Only way I could get picmip 5 was to have it load like that at the start. But if i vid_restarted even once during gameplay, it was impossible to change it unless i quit quake.

Luckily the new forceware drivers fixed it (91.31 i think)