how to make CFG
Posted: 15 Nov 2010, 21:23
Mouse acceleration
I strongly recommend turning this off. It just makes it harder to aim. To turn it off, the first thing you should do is go into the console and type:
/cl_mouseaccel 0
Here I'll go through some tweaks that can help boost your FPS (frames per second). A good FPS can make a world of difference; it's just damn hard to shoot enemies if they keep "warping" across your screen.
Your FPS is determined mainly by 3 things:
CPU clock speed (ghz)
Graphics card
RAM
Now before you begin tweaking, make sure to add "cg_drawfps 1" to your config, so you can see your frame rate.
set com_maxfps <n>
This lets you cap your FPS to some value. Due to numerical error in the Q3 engine, trickjumps work best at a steady FPS of 43 (good), 76 (great), or 125 (best). So if you want a steady FPS of 76 for example, then try to get your average FPS to be something like 80-90 (set com_maxfps to some really big number while you're doing this so you can see you`r true FPS without capping). Then once you are satisfied with the performance, add "com_maxfpx 125" to your config to cap it.
Ex: set com_maxfps 125
set r_picmip <n>
The bigger n is, the crappier your textures look, but it may improve performance on older video cards. Default value for n is 1. Allowed values are from 0 to 3.
Ex: set r_picmip 3
set r_picmip2 <n>
Similar to r_picmip. The default is already 3, so I don't see any reason to change it. You might be able to get better quality by lowering it, but as far as I can tell, the difference isn't noticeable.
set cg_wolfparticles <n>
This is 1 by default. If you notice your system slows down any time an airstrike goes off, then set this to 0. Besides boosting your FPS, turning off particles will also let you see through airstrikes more easily so you can shoot at people on the other side. The only disadvantage is that, without particles turned on, you might run into artillery strikes more often.
One option is to create a toggle script:
Ex: bind "key" toggle cg_wolfparticles
set cg_atmosphericeffects <n>
Turns on/off effects like rain or snow. There's really No reason why you would ever want this to be on, it just makes it harder to see and lowers your frame rate...
Ex: set cg_atmosphericeffects 0
set r_intensity <n>
Higher values of n make your screen brighter. Default is 1.0, allowed values are from 0 to 1.5
Ex: set r_intensity 1.2
set r_mapoverbrightbits <n>
Higher values of n make the shadowy parts of a map lighter, so you can spot enemies hiding in darker areas. Default is 2, allowed from 1 to 3. Setting it to 3 may help see targets that are hiding in shadows
Ex: set r_mapoverbrightbits 3
set r_dynamiclight <n>
Turns on (n=1) or off (n=0) dynamic light. Dynamic light is used very little in the game. I suggest you leave it on, because it is what makes the "glow" around dynamite, which is very useful to know when dyno has been planted.
Ex: set r_dynamiclight 0
set cg_shadows <n>
Turns on (n=1) or off (n=0) the little circular shadows that appear under your feet. Set this to 0 if you want, although the FPS boost will probably be negligible.
Ex: set cg_shadows 0
set r_finish <n>
Setting this to 1 enables "sync every frame". This is ONLY important if you have some device lag, like mouse or keyboard. (Perhaps if you have a wireless mouse and you find it lags behind your actions). If you don't notice your keyboard or mouse lagging, then set this to 0 to gain a few FPS.
Ex: set r_finish 0
set r_detailtextures <n>
When detail textures are enabled (n=1), it means that basically every object is textured twice to make it look more detailed. Obviously this is slower, so try disabling this (n=0) if you want to get a nice FPS boost.
Ex: set r_detailtextures 0
set r_subdivisions <n>
If you want a little performance boost, set this to 999. Otherwise, set it to 4.
Ex: set r_subdivisions 999
set r_texturemode <n>
This lets you set texture filtering. The most common values are:
(low quality): GL_NEAREST
(good quality): GL_LINEAR_MIPMAP_NEAREST (a.k.a. bilinear filtering)
(great quality): GL_LINEAR_MIPMAP_LINEAR (a.k.a. trilinear filtering)
(good quality): GL_LINEAR
In case you don't know, filtering is somewhat like antialiasing, except for textures. You can see what the game looks like without filtering by setting r_Texturemode to GL_NEAREST. It's pretty ugly, and everything is very "pixelated" or "blocky".
The default is bilinear filtering, and this will give you the best performance, and pretty good quality. For "best" quality you can use trilinear filtering, although there might possibly be some dip in FPS.
There's one problem with bilinear and trilinear filtering; both of them make your crosshair blurry. Personally I like to use a small crosshair, so this really annoys me because when the crosshair is blurred, I can barely see it. So, if this happens with you, then I'd suggest using GL_LINEAR. This mode will filter the textures and looks almost as good as bilinear filtering; yet the crosshair will still appear pretty sharp. BUT, be warned, using GL_LINEAR will likely cause a noticeable decrease in your FPS.
You could even use GL_NEAREST as your filtering mode but I wouldn't recommend it, because it looks like crap. I actually used to use this because, well, I didn't know about GL_LINEAR at the time
Ex: set r_texturemode GL_LINEAR
set r_fastsky <n>
If you set this to 1, it will just draw a solid color for your sky. This may give you a slight improvement in your FPS. It's not much, but then again, who cares how pretty the sky looks?
Ex: set r_fastsky 1
Resolution
set r_mode -1
set r_customwidth 1600
set r_customheight 1200
If you're having trouble with laggy/slow connections... Well, honestly there's not much you can do! You're pretty much fucked! But, tweaking these settings might help a little
set cl_maxpackets <n>
The bigger n is, the more information your computer sends to the server, so basically your actions will be more accurate. I think the default for this is 20, you can raise it higher if you want but no higher than 100 since this is the max allowed value. Be careful when tweaking this setting, if you set it to high, it may actually make your connection worse.
Ex: set cl_maxpackets 100
set rate <n>
Can be from 2500 to 45000. The faster your connection is, the higher you should set your rate. So for example, a modem might use a rate of 5000, whereas for LAN you would use 45000.
Ex: set rate 45000
And thats all what u need
some giys asking what is timenudge so here it is and how to use it
set cl_timenudge <n>
This is a very odd tweak: if you have a lot of lag, then setting this to a negative number will cause some crazy calculations to occur to take your lag into account when determining stuff like where your bullet went. Most people should leave this at 0. If you have serious ping problems, try setting this lower, but no lower than -50. (-50 is the lowest allowed value on most servers). In fact though, in most competitions, cl_timenudge must be zero. So if you play in a clan, don't tweak this...
Ex: set cl_timenudge 0
I strongly recommend turning this off. It just makes it harder to aim. To turn it off, the first thing you should do is go into the console and type:
/cl_mouseaccel 0
Here I'll go through some tweaks that can help boost your FPS (frames per second). A good FPS can make a world of difference; it's just damn hard to shoot enemies if they keep "warping" across your screen.
Your FPS is determined mainly by 3 things:
CPU clock speed (ghz)
Graphics card
RAM
Now before you begin tweaking, make sure to add "cg_drawfps 1" to your config, so you can see your frame rate.
set com_maxfps <n>
This lets you cap your FPS to some value. Due to numerical error in the Q3 engine, trickjumps work best at a steady FPS of 43 (good), 76 (great), or 125 (best). So if you want a steady FPS of 76 for example, then try to get your average FPS to be something like 80-90 (set com_maxfps to some really big number while you're doing this so you can see you`r true FPS without capping). Then once you are satisfied with the performance, add "com_maxfpx 125" to your config to cap it.
Ex: set com_maxfps 125
set r_picmip <n>
The bigger n is, the crappier your textures look, but it may improve performance on older video cards. Default value for n is 1. Allowed values are from 0 to 3.
Ex: set r_picmip 3
set r_picmip2 <n>
Similar to r_picmip. The default is already 3, so I don't see any reason to change it. You might be able to get better quality by lowering it, but as far as I can tell, the difference isn't noticeable.
set cg_wolfparticles <n>
This is 1 by default. If you notice your system slows down any time an airstrike goes off, then set this to 0. Besides boosting your FPS, turning off particles will also let you see through airstrikes more easily so you can shoot at people on the other side. The only disadvantage is that, without particles turned on, you might run into artillery strikes more often.
One option is to create a toggle script:
Ex: bind "key" toggle cg_wolfparticles
set cg_atmosphericeffects <n>
Turns on/off effects like rain or snow. There's really No reason why you would ever want this to be on, it just makes it harder to see and lowers your frame rate...
Ex: set cg_atmosphericeffects 0
set r_intensity <n>
Higher values of n make your screen brighter. Default is 1.0, allowed values are from 0 to 1.5
Ex: set r_intensity 1.2
set r_mapoverbrightbits <n>
Higher values of n make the shadowy parts of a map lighter, so you can spot enemies hiding in darker areas. Default is 2, allowed from 1 to 3. Setting it to 3 may help see targets that are hiding in shadows
Ex: set r_mapoverbrightbits 3
set r_dynamiclight <n>
Turns on (n=1) or off (n=0) dynamic light. Dynamic light is used very little in the game. I suggest you leave it on, because it is what makes the "glow" around dynamite, which is very useful to know when dyno has been planted.
Ex: set r_dynamiclight 0
set cg_shadows <n>
Turns on (n=1) or off (n=0) the little circular shadows that appear under your feet. Set this to 0 if you want, although the FPS boost will probably be negligible.
Ex: set cg_shadows 0
set r_finish <n>
Setting this to 1 enables "sync every frame". This is ONLY important if you have some device lag, like mouse or keyboard. (Perhaps if you have a wireless mouse and you find it lags behind your actions). If you don't notice your keyboard or mouse lagging, then set this to 0 to gain a few FPS.
Ex: set r_finish 0
set r_detailtextures <n>
When detail textures are enabled (n=1), it means that basically every object is textured twice to make it look more detailed. Obviously this is slower, so try disabling this (n=0) if you want to get a nice FPS boost.
Ex: set r_detailtextures 0
set r_subdivisions <n>
If you want a little performance boost, set this to 999. Otherwise, set it to 4.
Ex: set r_subdivisions 999
set r_texturemode <n>
This lets you set texture filtering. The most common values are:
(low quality): GL_NEAREST
(good quality): GL_LINEAR_MIPMAP_NEAREST (a.k.a. bilinear filtering)
(great quality): GL_LINEAR_MIPMAP_LINEAR (a.k.a. trilinear filtering)
(good quality): GL_LINEAR
In case you don't know, filtering is somewhat like antialiasing, except for textures. You can see what the game looks like without filtering by setting r_Texturemode to GL_NEAREST. It's pretty ugly, and everything is very "pixelated" or "blocky".
The default is bilinear filtering, and this will give you the best performance, and pretty good quality. For "best" quality you can use trilinear filtering, although there might possibly be some dip in FPS.
There's one problem with bilinear and trilinear filtering; both of them make your crosshair blurry. Personally I like to use a small crosshair, so this really annoys me because when the crosshair is blurred, I can barely see it. So, if this happens with you, then I'd suggest using GL_LINEAR. This mode will filter the textures and looks almost as good as bilinear filtering; yet the crosshair will still appear pretty sharp. BUT, be warned, using GL_LINEAR will likely cause a noticeable decrease in your FPS.
You could even use GL_NEAREST as your filtering mode but I wouldn't recommend it, because it looks like crap. I actually used to use this because, well, I didn't know about GL_LINEAR at the time
Ex: set r_texturemode GL_LINEAR
set r_fastsky <n>
If you set this to 1, it will just draw a solid color for your sky. This may give you a slight improvement in your FPS. It's not much, but then again, who cares how pretty the sky looks?
Ex: set r_fastsky 1
Resolution
set r_mode -1
set r_customwidth 1600
set r_customheight 1200
If you're having trouble with laggy/slow connections... Well, honestly there's not much you can do! You're pretty much fucked! But, tweaking these settings might help a little
set cl_maxpackets <n>
The bigger n is, the more information your computer sends to the server, so basically your actions will be more accurate. I think the default for this is 20, you can raise it higher if you want but no higher than 100 since this is the max allowed value. Be careful when tweaking this setting, if you set it to high, it may actually make your connection worse.
Ex: set cl_maxpackets 100
set rate <n>
Can be from 2500 to 45000. The faster your connection is, the higher you should set your rate. So for example, a modem might use a rate of 5000, whereas for LAN you would use 45000.
Ex: set rate 45000
And thats all what u need
some giys asking what is timenudge so here it is and how to use it
set cl_timenudge <n>
This is a very odd tweak: if you have a lot of lag, then setting this to a negative number will cause some crazy calculations to occur to take your lag into account when determining stuff like where your bullet went. Most people should leave this at 0. If you have serious ping problems, try setting this lower, but no lower than -50. (-50 is the lowest allowed value on most servers). In fact though, in most competitions, cl_timenudge must be zero. So if you play in a clan, don't tweak this...
Ex: set cl_timenudge 0