Best net, and fps settings client/server side

[tejeskifly]

Hi, i have a CS:S server, and i have a few question

What is the best fps_max value?

66, 333, 666, 1000 or another value? (server and client side)

What is the best cl_intrep/cl_intrep_ratio?

What is the best rate, cl_cmdrate, cl_updaterate?

i mean the right value:

rate: high value (the maximum rate was 1048576 right? this is a great value for gameing?)

cl_cmdrate/updaterate: 66

sry for my english...

[Monk]

66fps. You should leave everything stock, rate should be 25k or 30k at max.

[BehaartesEtwas]

to be precise: fps_max 66.66 is optimal. I run with the following rates:

Code:

sv_maxrate "140000"
sv_minrate "15000"

sv_maxupdaterate "66"
sv_minupdaterate "33"

sv_maxcmdrate "66"
sv_mincmdrate "33"

the exact height of the sv_maxrate setting is not important, as long as it is high enough to allow the necessary traffic. you cannot set it too high, the actual rate will simply not get higher at a certain point. on the contrary, if you set it too low, you will get choke (as that is exactly the original meaning of "choke": the game wants to send data but that would lead to a bandwidth higher than the rate. so it refrains from sending that data). in case you have a bandwidth problem, decrease cmd/updaterates instead.

cl_interp/cl_interp_ratio should not be too small, as you might get problems with hit registration then. cl_interp_ratio 2 is the absolute minimum, better use 3.

[tejeskifly]

Thanks, i try this settings.

For intrep, im using: cl_intrep 0.0151516 (i read somewhere, this is the right value)

[BehaartesEtwas]

(08-29-2011, 04:34 AM)tejeskifly Wrote:  For intrep, im using: cl_intrep 0.0151516 (i read somewhere, this is the right value)

that would be cl_interp_ratio 1 approximately, so no, it's not a good value. I wouldn't set cl_interp but use cl_interp_ratio instead. it's much easier to understand (number of ticks the client is able to interpolate). 1 is a bad idea, as the client will need to extrapolate everytime a tick is delayed a tiny bit. that happens all the time (variation in network latency).

plus there is no negative side effect having it a bit larger. why bother "optimizing" it at all? valve default is very nice (even though much larger)...

[tejeskifly]

(08-29-2011, 05:21 PM)BehaartesEtwas Wrote:  

(08-29-2011, 04:34 AM)tejeskifly Wrote:  For intrep, im using: cl_intrep 0.0151516 (i read somewhere, this is the right value)

that would be cl_interp_ratio 1 approximately, so no, it's not a good value. I wouldn't set cl_interp but use cl_interp_ratio instead. it's much easier to understand (number of ticks the client is able to interpolate). 1 is a bad idea, as the client will need to extrapolate everytime a tick is delayed a tiny bit. that happens all the time (variation in network latency).

plus there is no negative side effect having it a bit larger. why bother "optimizing" it at all? valve default is very nice (even though much larger)...

Ok thanks, and wich is the default value?
I want set is back

[Mike]

Just type;
cl_interp
cl_interp_ratio
in console and see what the default value is.