Quake3World

Not very important, but if I put "seta r_picmip 0" in my config, when I go ingame it changes back to r_picmip 1. I've tried using an autoexec but it still happens.

Just a hunch but... Geforce 5?

geforce 6600

Have you try to type it directly into the console during game ?
/r_picmip 0
/vid_restart after that , check again into the console if the change is done, just type
/r_picmip
and the console will tell you what value you have now...

I recently started using r_picmip 5 but couldn't get it to stick, it kept reverting to r_picmip 1. After a few days this was driving me mad but when I had a go a sorting it out nothing seemed to work. However when I turned the PC on the next day the problem had gone. The only thing that I can say I did for sure was to make my configs read only, I don't know if this will help.

Geforce 3 ti 200

D'Artagnan wrote:Have you try to type it directly into the console during game ?
/r_picmip 0
/vid_restart after that , check again into the console if the change is done, just type
/r_picmip
and the console will tell you what value you have now...

Sorry, I should have said, yes doing it manually ingame works, but only for that session. Everytime I load up quake I have to do it again and it's rather irritating.

angst wrote:I recently started using r_picmip 5 but couldn't get it to stick, it kept reverting to r_picmip 1. After a few days this was driving me mad but when I had a go a sorting it out nothing seemed to work. However when I turned the PC on the next day the problem had gone. The only thing that I can say I did for sure was to make my configs read only, I don't know if this will help.

Geforce 3 ti 200

I'll try read-only and get back to you.

Edit: Nope, no luck.
Edit2: Oh and this has only started happening since I've been using my 6600...

Are you counting 'every time I load up quake' as actually every time you load the game, or every time you join a server?

cause if PB/OSP doesn't like your settings it'll throw a vid_restart and force them down, could be it's forcing your picmip down to 1?

I have vague recollection of another solution to this problem as well, but it escapes me

I experience the same issue with my nVidia card, and work around it by forcing r_picmip 0 in my Q3 launch scripts. You can do the same thing with shortcuts on Windows; add +set r_picmip 0 in the appropriate place.

I set my config to r_picmip 0 every single mother fucking time I join a server, and sometimes after I vid_restart in whatever Q3 mod. It's annoying. 7900 GT.

Foo wrote:Are you counting 'every time I load up quake' as actually every time you load the game, or every time you join a server?

cause if PB/OSP doesn't like your settings it'll throw a vid_restart and force them down, could be it's forcing your picmip down to 1?

I have vague recollection of another solution to this problem as well, but it escapes me

Everytime I join a server (in CPMA, not tried other mods), but I only play at one server most of the time and before I got my 6600 I had no trouble.

Do you have an autoexec.cfg in all your mod folders? If not you should. And try putting the quotes differently, like this: seta r_picmip "0"

Also if that dosen't work, like the other guy said, put it in your game shortcut (btw, it's best to have a shortcut to each mod, and not launch mods via the in-game menu, so you don't mess up q3config.cfg with mod cvars - you can set each mod shortcut with +set fs_game foldername), after the command line, put: +set r_picmip 0 But I take you don't use shortcuts, and use all-seeing eye? You can select the config file via the config line in game options in ase.

There is one last method that will work 100%. Backup your q3config.cfg and autoexec.cfg from baseq3 and your mod folders. Delete them all. Then run baseq3 again, it will generate a new q3config.cfg and reset everything to default. Exit the game, and paste your autoexec.cfg back into baseq3. This should really work.

Got all that?

I vaguely remember a bug that would reset the picmip. Can't remember if it was vanilla or OSP but you would have to execute it in the console even if you had it placed correctly in your autoexec.

**edit** This may help: http://www.quakesrc.org/forums/viewtopi ... 6e7fb9b841

Noobs. It's the texture quality preference of your nVidia drivers. Change Image Quality from 'Quality' to 'High Quality':



You can make a profile for the Q3 executable as well (with AA and AF enabled), if you don't want heavier games like Q4 to use HQ textures.

And how would I get there?
It also just occured to me I may not have the latest drivers for the 6600. I'm hopeless, can anyone link me to them because I have no clue.

edit: I got image quality on high quality now but still stuck on picmip 1, still I may have old drivers.

dzjepp wrote:Do you have an autoexec.cfg in all your mod folders? If not you should. And try putting the quotes differently, like this: seta r_picmip "0"

Yes and I do.

dzjepp wrote: Also if that dosen't work, like the other guy said, put it in your game shortcut (btw, it's best to have a shortcut to each mod, and not launch mods via the in-game menu, so you don't mess up q3config.cfg with mod cvars - you can set each mod shortcut with +set fs_game foldername), after the command line, put: +set r_picmip 0 But I take you don't use shortcuts, and use all-seeing eye? You can select the config file via the config line in game options in ase.

There is one last method that will work 100%. Backup your q3config.cfg and autoexec.cfg from baseq3 and your mod folders. Delete them all. Then run baseq3 again, it will generate a new q3config.cfg and reset everything to default. Exit the game, and paste your autoexec.cfg back into baseq3. This should really work.

Got all that?

I use ASE but I suppose I could give it a shot as my final chance if the driver thing doesn't work.

nVidia already added a profile for some games, including quake3, so you might wanna try changing image quality to HQ there too. I'm not totally sure, but that could be the solution. I had to go through the same things when i installed my 6800GS. Disable 'Conformant texture clamp' too when you're there btw. No more skybox lines.

It has nothing to do with the drivers

I "fixed" this by making a fresh new copy of q3a with the paks in there and a fresh new config. I don't get picmip 1 forcing anymore.

Oddly, I still do on my old copy even with the cfg deleted.

strange

You need to make sure ALL traces of q3config.cfg and autoexec.cfg are deleted from ALL directories if you attempt to fix it via that route... some cvars just wouldn't snap for me, and deleting all configs and restarting did fix it.

I've had this problem too.

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.

riddla wrote:

[xeno]Julios wrote:you don't need to store cfgs in the mod directories.

bad advice needs to stop.

It's true - why don't you try it out yourself

i store all my cfgs in baseq3 and i can exec them while in any mod.

riddla wrote:you're giving bad advice. mods have a reason to have a q3config.cfg file in their folder, esp with all the mod's custom settings and particular custom cvars, etc.

Your advice with that statement is just plain bad although it will work.

it'd be bad advice if i were advocating for using q3config.cfg as ur cfg

i made it clear that i was talkin about custom cfgs.

q3config.cfgs exist in all folders and if there are two cfgs with the same name - one in mod directory and one in baseq3, then priority will be given to the one in the mod directory.

If, however, you choose the route i suggested, and use a custom cfg such as juliosra3.cfg or juliososp.cfg then it makes sense to keep those cfgs ONLY in the baseq3 directory.

And so long as the cfgs are comprehensive and cover all settings, vid, binds, etc, then u can erase all other cfgs (q3config's will be immediately replaced once u load up the mod again) and not worry about conflicting settings.

True. I used Cure's modular config as a template for my extensive config. I have all my mod configs in baseq3/[config]. They're automatically loaded by a different autoexec.cfg in each mod folder (pointing to the appropriate mod config).

[xeno]Julios wrote:

riddla wrote:

[xeno]Julios wrote:you don't need to store cfgs in the mod directories.

bad advice needs to stop.

It's true - why don't you try it out yourself

i store all my cfgs in baseq3 and i can exec them while in any mod.

Yeh I use 1 autoexec.cfg in baseq3 for all mods and vanilla. My baseq3 contains everything though, binds, cvars, mod specific commands etc etc