105 replies to this topic

[katana.]

Since everyone has a different PC and preferences, It's always best to create your own cfg.
This will be like a tutorial to help out those in need. Enjoy and happy gaming!

And remember, it is best if you put these commands in your cfg manually instead of in sof.
Open your config with notepad/wordpad and press ctrl+f and type in for example: r_picmip and change the values.
If it doesnt find a certain command add it manually.

GRAPHICS -

The goal is to achieve stable 125 FPS.

- r_picmip (0-4) changes the overall texture quality, use 4 if u prefer lower graphics
- r_lodbias (0-4) changes the geometric detail level, use 4 if u prefer lower graphics
- r_simplemipmaps (0/1) changes the sharpness of all the items, use 0 if u prefer lower graphics
- r_colorbits (16/32) sets the color depth, using 16bit colors wont give u a noticeable fps boost and it also makes it harder to see through nades
- r_texturebits (16/32) changes the texture quality, unlike with colorbits, using a value of 16 here might give u a little fps boost and it wont affect the nades
- fx_countscale (0.25-1) reduces the greyish smoke coming from the nades when a value of 0.25 is used
- r_detailtextures (0/1) changes the detail layers used, use 0 if u prefer lower graphics
- fp_vertexlight (0/1) changes the lighting of the map, probably one of the only commands that give u a noticeable fps boost when used, can make the view worse at some particular spots
- cg_fov (80-100) determines the field of vision which is basically how much u see on ur screen when ur not moving
- r_subdivisions (46-999) Put it to 999, it will increase your FPS, not by much but every little thing can help!
- seta r_displayrefresh "75" This Depends on your monitor refreshrate, see what the max your monitor can handle, and add that in your config manually.

MOUSE SETTINGS

This is personal for everyone, just experiment and see what you feel comfortable with
It is recommended not to change these settings once you find your preference.

put these to zero:
cg_bobup "0"
cg_bobpitch "0"
cg_bobroll "0"
cg_runpitch "0"
cg_runroll "0"

- m_pitch, changes the vertical (up-down) sensitivity, some people still think using a lower value decreases ur recoil which is plain bullshit
- m_yaw, changes the horizontal (left-right) sensitivity
- cl_mouseaccel, sets the acceleration of ur mouse ingame

Make sure u installed the drivers for ur mouse, else it may not work as it should do)

CONNECTION -

Lowest ping with the smoothest lagometer.

- rate, controls all the packets u send and recieve, this should be set to 15000-30000 depending on ur connection
- cl_maxpackets, limits the amount of packets sent to the server, do not set this below 30 or it will cause some little warping. the best value for this (when using com_maxfps 125) is 63 cause the amount of frames u send to the server is either every frame, every second frame and so on. its not possible to set it to 125 so its better to use 63 (125/2=62.5) for the optimal bullet reg.
- snaps, determines the amount of updates u recieve from the server, anyone with an ok connection should use a value of 40 on this one
- cl_timenudge, originally its made for decreasing the delay of highpingers but it also works other way around. inserting a negative value such as -5 might help ur bullet reg a little
- com_maxfps, sets the max fps, the more the better, 200 makes it a little easier to land some spray kills but u wont be able to move the same way than with 125
- cg_lagometer, with this enabled ur able to see any packet loss and/or lags u get and have them explained. i dont want to make it too complicated so ill just mention the red lines are packet loss.

this is what it looks like when u have bad connection settings and/or ur connection is not stable:


this is what its supposed to look like when ur rates are fine and ur connection isnt lagging:


Some side notes: If you cant get stable 125 fps, you could lower your fps up to the point where it doesnt jump up and down for some smoother gameplay.
I dont recommend anything lower than 90-100 though.
You can find your lowest fps by adding ''cg_drawfps 1'' in your cfg and throw a couple fire nades while standing on patio (stand a bit to the corner side)
And if you are really struggling for decent fps, update your graphics drivers and put all the settings for your card to low! for nvidia its NVDIDIA Control Panel for ATI cards its Catalyst control center ( CCC ) or if you rocking it integrated, use intel graphic and media control panel! GL and feel free to ask questions if you feel lost.

Edited by katana., 15 November 2012 - 05:21 PM.

[DARK]

bind mouse1 kill, jk relax

[Foxdie]

should put standard commands in first post like
GRAPHICS
com_maxfps "125"
AIM
cg_bobup "0"
cg_bobpitch "0"
cg_bobroll "0"
cg_runpitch "0"
cg_runroll "0"

[fleim]

GRAPHICS

the most important 'graphical' commands affecting ur fps in the game;

- r_picmip (0-4) changes the overall texture quality, use 4 if u prefer lower graphics
- r_lodbias (0-4) changes the geometric detail level, use 4 if u prefer lower graphics
- r_simplemipmaps (0/1) changes the sharpness of all the items, use 0 if u prefer lower graphics
- r_colorbits (16/32) sets the color depth, using 16bit colors wont give u a noticeable fps boost and it also makes it harder to see through nades
- r_texturebits (16/32) changes the texture quality, unlike with colorbits, using a value of 16 here might give u a little fps boost and it wont affect the nades
- fx_countscale (0.25-1) reduces the greyish smoke coming from the nades when a value of 0.25 is used
- r_detailtextures (0/1) changes the detail layers used, use 0 if u prefer lower graphics
- fp_vertexlight (0/1) changes the lighting of the map, probably one of the only commands that give u a noticeable fps boost when used, can make the view worse at some particular spots
- cg_fov (80-100) determines the field of vision which is basically how much u see on ur screen when ur not moving


MOUSE SETTINGS

these settings are ALL personal, there are no good or bad mouse settings;

- m_pitch, changes the vertical (up-down) sensitivity, some people still think using a lower value decreases ur recoil which is plain bullshit
- m_yaw, changes the horizontal (left-right) sensitivity, never seen anyone use anything but a default value so i dont think this useful for anyone
- cl_mouseaccel, sets the acceleration of ur mouse ingame

(this is not so cfg related but make sure u have installed the drivers for ur mouse, else it may not work as it should do)


CONNECTION

- rate, controls all the packets u send and recieve, this should be set to 15000-30000 depending on ur connection
- cl_maxpackets, limits the amount of packets sent to the server, do not set this below 30 or it will cause some little warping. the best value for this (when using com_maxfps 125) is 63 cause the amount of frames u send to the server is either every frame, every second frame and so on. its not possible to set it to 125 so its better to use 63 (125/2=62.5) for the optimal bullet reg.
- snaps, determines the amount of updates u recieve from the server, anyone with an ok connection should use a value of 40 on this one
- cl_timenudge, originally its made for decreasing the delay of highpingers but it also works other way around. inserting a negative value such as -5 might help ur bullet reg a little
- com_maxfps, sets the max fps, the more the better, 200 makes it a little easier to land some spray kills but u wont be able to move the same way than with 125
- cg_lagometer, with this enabled ur able to see any packet loss and/or lags u get and have them explained. i dont want to make it too complicated so ill just mention the red lines are packet loss.

few examples of lagometer in use;

this is what it looks like when u have bad connection settings and/or ur connection is not stable:


this is what its supposed to look like when ur rates are fine and ur connection isnt lagging:



BINDS AND SCRIPTS

personally i dont find these too useful but some people probably have few weapon scripts to share, ill jst put the normal record bind used by alot of people

- record bind; bind f1 "g_synchronousclients 1 ; record ; g_synchronousclients 0"


NoW GeT GoOd

[FLAiR]

rocket taught me something about maxfps, maxpackets and snaps, but i forgot it. #facepalm

seta com_maxfps "125"
seta cl_maxpackets "63"

cause 63 x 2 = almost 125? lol, rocket's input required!

oh, here's a link. googled it quickly. it's about rate, snaps, maxpackets, maxfps and more. definitely worth reading: http://www.funender....connection.html

weapon toggle bind, i didn't like this shit in the beginning, but i can't play without it anymore lol.
bind 1 "weaptoggle pistol pistol; weapprev"
bind 2 "weaptoggle pistol pistol; cg_drawcrosshair 1"

bind MOUSE1 "+attack"
bind MOUSE2 "+altattack"
bind MOUSE4 "weaptoggle grenade grenade; cg_drawcrosshair 1"
bind MWHEELDOWN "weaptoggle primary primary; cg_drawcrosshair 1"
bind MWHEELUP "weaptoggle secondary secondary; cg_Drawcrosshair 2"

and also make sure your display refresh rate is the same as your screen:
seta r_displayRefresh "<your display refresh rate>"

lol @ foxdie, not full of noob after all

Edited by FLAiR, 29 June 2012 - 02:25 PM.

[Foxdie]

flairs post is full of noob

[bing bang blaow]

GRAPHICS

the most important 'graphical' commands affecting ur fps in the game;

- r_picmip (0-4) changes the overall texture quality, use 4 if u prefer lower graphics
- r_lodbias (0-4) changes the geometric detail level, use 4 if u prefer lower graphics
- r_simplemipmaps (0/1) changes the sharpness of all the items, use 0 if u prefer lower graphics
- r_colorbits (16/32) sets the color depth, using 16bit colors wont give u a noticeable fps boost and it also makes it harder to see through nades
- r_texturebits (16/32) changes the texture quality, unlike with colorbits, using a value of 16 here might give u a little fps boost and it wont affect the nades
- fx_countscale (0.25-1) reduces the greyish smoke coming from the nades when a value of 0.25 is used
- r_detailtextures (0/1) changes the detail layers used, use 0 if u prefer lower graphics
- fp_vertexlight (0/1) changes the lighting of the map, probably one of the only commands that give u a noticeable fps boost when used, can make the view worse at some particular spots
- cg_fov (80-100) determines the field of vision which is basically how much u see on ur screen when ur not moving


MOUSE SETTINGS

these settings are ALL personal, there are no good or bad mouse settings;

- m_pitch, changes the vertical (up-down) sensitivity, some people still think using a lower value decreases ur recoil which is plain bullshit
- m_yaw, changes the horizontal (left-right) sensitivity, never seen anyone use anything but a default value so i dont think this useful for anyone
- cl_mouseaccel, sets the acceleration of ur mouse ingame

(this is not so cfg related but make sure u have installed the drivers for ur mouse, else it may not work as it should do)


CONNECTION

- rate, controls all the packets u send and recieve, this should be set to 15000-30000 depending on ur connection
- cl_maxpackets, limits the amount of packets sent to the server, do not set this below 30 or it will cause some little warping. the best value for this (when using com_maxfps 125) is 63 cause the amount of frames u send to the server is either every frame, every second frame and so on. its not possible to set it to 125 so its better to use 63 (125/2=62.5) for the optimal bullet reg.
- snaps, determines the amount of updates u recieve from the server, anyone with an ok connection should use a value of 40 on this one
- cl_timenudge, originally its made for decreasing the delay of highpingers but it also works other way around. inserting a negative value such as -5 might help ur bullet reg a little
- com_maxfps, sets the max fps, the more the better, 200 makes it a little easier to land some spray kills but u wont be able to move the same way than with 125
- cg_lagometer, with this enabled ur able to see any packet loss and/or lags u get and have them explained. i dont want to make it too complicated so ill just mention the red lines are packet loss.

few examples of lagometer in use;

this is what it looks like when u have bad connection settings and/or ur connection is not stable:


this is what its supposed to look like when ur rates are fine and ur connection isnt lagging:



BINDS AND SCRIPTS

personally i dont find these too useful but some people probably have few weapon scripts to share, ill jst put the normal record bind used by alot of people

- record bind; bind f1 "g_synchronousclients 1 ; record ; g_synchronousclients 0"


NoW GeT GoOd

to continue network part

cl_maxpackets

This is the Maximum number of data packets that can be SENT to the server per second. The higher you set this, the smoother your game will feel as your actions (run, shoot, jump etc.) will be updated more frequently. Broadbanders will be able to go up to 125 (but not higher) but this depends on your individual connections. Dialup users will just about be able to manage 30, so 20 is more of a stable setting.

Also if you set your MaxPackets too high, your ping will start to rise. This is due to the increase in upstream bandwidth usage. So you should set your MaxPackets as high as you can without it affecting your ping (and without going over 125).



com_maxfps

This is the maximum graphical framerate permitted. You can not use any MaxFPS value. The only valid values are those which are equal to (1000/x) where x is an integer. So for example your 125fps comes from (1000/8 = 125). If you try and set MaxFPS to 120, you will still get 125fps. This is because any invalid setting is rounded up to the next (1000/x).

Some valid Values for MaxFPS:

1000/3 = ~333
1000/4 = 250
1000/5 = 200
1000/6 = ~166
1000/7 = ~142
1000/8 = 125
1000/9 = ~111
1000/10 = 100
1000/11 = ~90
1000/12 = ~83
1000/13 = ~76
1000/14 = ~71
1000/15 = ~66
1000/16 = ~62
1000/17 = ~58
1000/18 = ~55
etc.



cl_maxpackets and com_maxfps

This is where your graphical framerate affects your connection. The actual MaxPackets sent to the server MUST be equal to (your_FPS/x), once again where x is an integer. If you set your MaxPackets to a value which is not equal to (your_FPS/x) then your MaxPackets will actually be rounded down to the nearest valid setting.

Most of you will use MaxFPS 125. If so, your valid MaxPackets values will be as follows (assuming your PC can achieve its MaxFPS value constantly):

(always round up these calculations to integers)

125/1 = 125
125/2 = 63
125/3 = 42
125/4 = 32
125/5 = 25
etc.

You should choose the largest value that your connection can handle. If your MaxPackets is not set to a valid value, it is a potential waste of bandwidth and therefore potential lag/instability.

For example, if your framerate drops to 100 then your valid MaxPackets values will change to:

100/1 = 100
100/2 = 50
100/3 = 34
100/4 = 25
etc.

So if you have your cl_maxpackets set to 100 and are using 125fps then mostly your MaxPackets will be at 63 (highlited in yellow above) (this is the largest value not exceeding the input cl_maxpackets limit). However, when the framerate drops to 100fps, the MaxPackets will change to 100 as this is now the largest value that does not exceed the input cl_maxpackets limit (highlited in yellow above). If your connection cannot handle 100 packets it will cause your ping to rise or spike. Even if it can handle the jump from 63 to 100 packets, this may well cause your ping to fluctuate more than if your actual MaxPackets were constant.

from cod4 forums but same applies in sof2

[Fastlain]

some handy binds

bind 1 "weapon 8;cg_drawgun 1" (nade)
bind 2 "weapon 1;cg_drawgun 1" (knife)

bind MWHEELDOWN "weaptoggle secondary secondary;cg_drawgun 1"
bind MWHEELUP "weaptoggle primary primary;cg_drawgun 1"

bind p "screenshot"

Outfitting binds.

bind UPARROW "OUTFITTING AAADA;echo; say_team ^7Ak^)/^7Shotgun^)/^7flamenade^)."
bind DOWNARROW "OUTFITTING AAAAA;echo; say_team ^7Ak^)/^7Shotgun^)/^7fragnade^)."
bind LEFTARROW "OUTFITTING DAADA;echo; say_team ^-Sniper^)/^-Shotgun^)/^-flamenade^)."
bind RIGHTARROW "OUTFITTING DAAAA;echo; say_team ^-Sniper^)/^-Shotgun^)/^-fragnade^)."

rcon binds

bind F5 "rcon map_restart"
bind F6 "rcon gametype_restart"
bind F7 "rcon g_speed 0"
bind F8 "rcon g_speed 280"

fov zoom bind

bind CAPSLOCK "vstr zoom"
seta zoomout "cg_fov 100; echo Zoom Out; set zoom vstr zoomin"
seta zoomin "cg_fov 80; echo Zoom In; set zoom vstr zoomout"
seta zoom "vstr zoomin"

Edited by Fastlain, 25 June 2012 - 08:00 PM.

[Foxdie]

i hope your knife and nade binds are a joke LOL

[l'ANGELINOOO `]

u can select your nade and pistol faster : )

Edited by l'ANGELINOOO `, 25 June 2012 - 08:26 PM.

[malign]

Use weaptoggle grenade grenade for that :x = faster

[bing bang blaow]

bind 1 "weaptoggle pistol pistol; weapprev"

[Foxdie]

exactry my point

[defqon]

i hope your knife and nade binds are a joke LOL

LOL I HOPE SO TOO

[-AGGA-]

gl.

[dvz]

this is what it looks like when u have bad connection settings and/or ur connection is not stable:

best

[NavySeall]

LOL WTF u fuckign nerds.
Just learn how 2 aim man, no need for all those bullshit.

[katana.]

thanks everyone! Added all in first post.

Sticky plox so we can direct people to this topic from now!

Edited by katana., 25 June 2012 - 09:22 PM.

[Foxdie]

SNAPS info is wrong though snaps 40 will still behave as 20 because sv_fps is 20 so there is absolutely no point in changing snaps

[azzy]

LOL WTF u fuckign nerds.
Just learn how 2 aim man, no need for all those bullshit.

Config is not the far most important thing there is, but the settings above are recommended. Sens etc is own preference.



*edit: sorry misread name

Edited by azzy, 25 June 2012 - 10:26 PM.