i have to do all these settings to become good!?!?!?!111 fffffffff iiiiiiittttt

but its nice though btw

very nice work.
i didn't knew that r_texturemode thingie, which impressed me a lot. with _Linear oder _Nearest its so much better to move and aim... thanks! :)

Nice one, altho i dont agree on a couple of things:

1- Im a shaft whore too (we should sort this out, railwhores are everywere but we shaftwores need space and its getting to crowd here) and cg_truelightning is the devil, why do you want the game to lie to you?

I ping >100 on every server and still do over 18% shaft easily so belive me when i say that truelighting is bad unless your ping is under 30 and you are too used to lan (not my case).

Still, the more info i've got the easier it will be for me to shaft the enemy so i dont want the game to tell me that the shaft is here when in fact its not there. And yes, ive tried setting it at 0.1 but it still sucked big time.

2- predictitems is a must :)

you think 18% is good?

¬_¬ yes it is with my ping.

18% with over 100 ping is good if he uses it alot

seen people with ping 150 shaft 35.
I use cg_truelightning 1 wich alot of people whine to me about
still I shaft 25-30 while using cg_truelightning 0.2 takes me to 20%.
There is no right or wrong. If I shaft better with truelightning 1 I'm not going to change it.
Start thinking like a man.
If it works... Dont fuck with it !

"...the sv_fps of the server, which is ALWAYS 25..."

You sure about that?

I thought 20/21 fps is server-side fps.

i don't clearly see the difference between between 16 bits and 32 bits, should i go to eye exam?

neh..

huan: although truelightning IS inaccurate it is my personal experience that it helps aiming in inet
you gotta try for yourself though, as i've written

anonymous: wrong expression.. should have said "q3 has a maximum server-client update of 25".. this isnt really the command sv_fps

newbeginner: yes you should, send me the bill for your new glasses :p


i admit i might have overseen 1 or 2 things in the article or havent found the right expression for them.. flame me for it, i like it :)

nice work.
i like it if there are screenshots to compare :)
i didn't thougt that there is so much difference between the enemycolors, because i play with a very bright cfg.

too bright is bad for your eye, especially when you play like 3 hours a day :(

I have r_mapoverbrightbits at 1, and it's dark :) but things like enemis and items glow, cause I use r_gamma 3 and r_ignorehwgamma 1.

i used it before to, but now i play with regular r_picmip 5 and r_gamma 1.4. Why? Coz I don't wont to reload a different config everytime I change a map.

About the r_texturemode...
I was also surprised the difference between gl_linear and gl_linear_mipmap_nearest, it feels faster/smoother, but is there a reason why? I thought mipmaping allows for less detail proportional to "distance" so I'd imagine it'd be faster w/ mipmap_nearest(but it sure doesn't feel that way!), but my understanding about the subject is very minimal. Like what's the difference between gl_nearest and gl_nearest_mipmap_nearest?

Also anyone know what r_simpleMipMaps does?

Thanks

anyone?

first you should register, and then we can talk about it :)

even though the game lies to you when you have truelightning , it helps you not get disturbed by the swingy beem , and you just concentrate holding it infront of the opponent , with this at 1.0 i get ab 28-32% lg aim almost every fight and i like it alot. But i have like 35 ping , and i would only recommend this for players with 45 and less ping .

That's exactly my thought too. It's almost impossible for me to aim without truelightning not set to 1. I usualy play with an average of 40 ping.

hmmmm , im dc (dreamcast q3) any i tried most of them and they didn't work any ideas?

AFAIK, the DC version was made with many of the tweakable features taken out (to supposedly better suit the console crowd...), that's why many of the settings discussed in this guide don't work for you (some of them are actually OSP settings). What's even worse is that the DC version is stuck at around 60fps, which doesn't give you the best physics. I doubt the developer fixed the fps-dependent physics for the DC version, since they intended to let it interface with PC servers that run 1.16n. I remember playing against a DC player (on my PC) once who asked me why I was moving much faster than him (and he told me that he was strafe jumping too)...

Nice article. I think somebody should pick up most Config Articles and wrote a big one :)

i dont see any difference between the 32bit and 16bit screenie.. :)

very nice article though

if i set the bits to 32 bit, do i have to set my windows options to 32 bit, too? or doesn't it matter?

really? well i see the difference, but i know what i have to look for since i always play 32 bit and i know the difference
anyways, in-game there is a much greater difference, things you wont notice on screenshots, so if your gfx can take it, use 32..

your windows options shouldnt affect quake3.. q3 choses the color depth via the r_colorbits (and r_texturebits) variable

i think this is one of the most interesting articles i read at XSR, config articles you know. everyone can spot an enemy when he's right in front of you, whats more important is trying to get the most accurate detailing at far distance. maybe try to sort out what r_ commands wich affect worldmap and those who only affect players/items etc. i think q3 is somewhat innacurate when an enemy moves fast at distance. related to timenudge i guess.

There is a new config Editor @ www.planetquake.com/dekket/

It´s very good try it :) A friend of mine has created it :)

Eh, sv_fps by default is 20.

very nice article, i just changed some cvars in my config and will test it asap :)
I change my config often after a certain period of playing with it :) it gives me a kind of new motivation... it's like IRL .... always doing the same, makes stuff boring =)

btw, just played vs a player today who always taunt'ed :D now he will never ever again disturb me ;p

wow. i decided to try this with rtcw. and i have known about s_mixahead awhile now, i never knew about s_mixprestep. i got an elsa gladiac 920 geforce3.. and was only getting a steady 90fps in rtcw (because i was too lazy to tweak my cfg). anyway, i tweaked it, capped it at 125.

i just stumbled on to this article, set s_mixprestep.. and i went on a server.. in an enclosed area, i got 363fps :) which is actually kind of sweet.. since i've never gone over 300 in q3 or rtcw.

danke. :)

WTF is ThinShaft? plz explain ppl ;) tkz

cg_fov 300
cg_zoomfov 120
+zoom


have fun

Useful stuff for most, I expect. Looking through the configs included with OSP would probably help a lot of you as well.

> cg_enemyColors ... command is a feature of OSP

Give credit where it's due, thanks. It's from CPMA.

The pmove_fixed 1 jerkiness is from a bug in the original id implementation. It's fixed in CPMA and I thought it was in OSP too, but I'll check. There are a few subtle differences between pmove 1 and just getting 125fps, but they're pretty tiny.

Huan - you couldn't be more wrong about truelightning.
I'm with Stony on predictitems as well: you're almost always much better off getting the truth from the server than thinking you picked up something that you didn't.

> although truelightning IS inaccurate

Not at all. It's an accurate representation of where your LG WILL be when the server actually gets round to noticing that you fired it. The problem with tl 1 is not that it's wrong, it's simply that most people can't get it through their skulls that they need to lead with the LG same as every other weapon, and TL 0 reminds them that they do actually have to deal with lag.

r_textureMode

>The way the textures are treated. GL_NEAREST is without any filtering, GL_LINEAR adds bilinear filtering, GL_LINEAR_MIPMAP_NEAREST does bilinear filtering with mipmapping, GL_LINEAR_MIPMAP_LINEAR does trilinear filtering with mipmapping. Usually, one would chose the best looking mode (GL_LINEAR_MIPMAP_LINEAR), which doesn't even cost much rendering power (FPS), BUT the deal is: the cycles used for filtering add a few ms of "graphics card lag" to the game. You will most probably notice it for yourself, at least when switching between GL_NEAREST and GL_LINEAR_MIPMAP_LINEAR. The game feels much more responsive with GL_NEAREST, so I'd recommend this setting. If you cannot play without filtering, take GL_LINEAR and not the more advanced modes.

ya wee dack!
just stick r_finish 1 on.
end of your worries. got the same "feel" as gl_nearest, gg tbh.
kermick

"snaps

The server-client updates per second. Default is 20. This command is bound to the sv_fps of the server, which is ALWAYS 25, so every setting above 25 should do fine. Above, there is no difference. Somehow people got used to set it to "40", probably because it looks good :) "

lmao! "looks good"... crap m8, most bw, jolt, BY, etc servers' sv_fps is set to 20, and putting your snaps to 40 wont make you "look good", but in some cases make u get 50 ms off your ping, which happens to me on some servers, such as some jolt ones.
You obviously know some tips, but you're also misleading some newbies reading your article; if i didnt know anything about q3 tweaking i'd rather go read some stuff written by people who know what they're talking about instead of this crap column. And please give ArQon the credits he and his team deserve with the work he put in CPMA when u're talking about features from this mod.
Sorry about being rude, but this snaps crap just sounded wank to me.

also: because of mipmapping gl_linear is quite a lot slower on lo end gf2mx cards. drops below 120 :/ quite handi tho cos the pro-mode skins are REALLY bright with it.

what exactly does r_finish 1 do?

GOTO here. the commends are explained much better than this amatuer

http://www.upsetchaps.cjb.net/Quake3Guide/AquaQuake3Guide.html

Can't see pictures