[cool_myll]

sv_minupdaterate 66 sv_maxupdaterate 67 sv_mincmdrate 66 sv_maxcmdrate 67

Why 67? Isnt 66 the limit? Why not both 66?

[daveyboye]

Originally Posted by cool_myll Why 67? Isnt 66 the limit? Why not both 66?

66 is the limit, however there is a bit of wiggle room and does allow you to flex up to 67

[nightrider]

Yes from what I can barely remember 67 is allowed in order to give you a true 66 tic.

[AeroAcrobat]

Originally Posted by nightrider 1x DayZ 1x CS:GO 1x Left4Dead2 1x Day of Defeat Source 1x Team Fortress 2 sv_minrate 30000 sv_maxrate 0 sv_minupdaterate 66 sv_maxupdaterate 67 sv_mincmdrate 66 sv_maxcmdrate 67 sv_client_cmdrate_difference 100 sv_client_predict 1 sv_client_interpolate 1 sv_client_min_interp_ratio -1 sv_client_max_interp_ratio -1 net_maxcleartime .01 net_splitpacket_maxrate 30000

why is sv_client_cmdrate_difference = 100 ?
isn't a lower value technicly better ?

"net_maxcleartime" = "4.0"
          - Max # of seconds we can wait for next packets to be sent based on rate setting (0 == no limit).

could someone give an example for this command ?
default value is 4 sec.
what would happen if I lower it ?

[Bacardi]

Originally Posted by AeroAcrobat sv_minupdaterate 66 sv_maxupdaterate 67 sv_mincmdrate 66 sv_maxcmdrate 67 sv_client_cmdrate_difference 100 why is sv_client_cmdrate_difference = 100 ? isn't a lower value technicly better ?

well, no matter now because cmdrate min/max value have capped.

When have sv_maxcmdrate 100; sv_mincmdrate 1; sv_client_cmdrate_difference 0
cl_cmdrate will be follow cl_updaterate with exactly same value:
cl_updaterate 66; cl_cmdrate 66

And if example sv_client_cmdrate_difference 20,
cl_cmdrate can be set +-20 of cl_updaterate value:
cl_updaterate 66; cl_cmdrate 46 ~ 86

Maybe when someone want host server with small bandwidth, can set scale cmdrate difference bigger,
to send less updates to players and download players cmds more.

sv_maxrate 0; sv_minrate 30000
sv_maxupdaterate 30; sv_minupdaterate 20
sv_maxcmdrate 100; sv_mincmdrate 30
sv_client_cmdrate_difference 100
// cl_updaterate 20 ~ 30
// cl_cmdrate 30 ~ 100

[TheGodKing]

On a 66 tick server there are 66 frames per second meaning that there can only be 66 updates to send to the client per second. In other words if you see 67 you are still only getting 66 updates per second from the server.

A fun little experiment would be to set these rates on a 66 tick server:

-tickrate 66 (commandline)
sv_maxupdaterate 100 (This sets the upper bound for cl_updaterate)
sv_minupdaterate 1 (This sets the lower bound for cl_updaterate)
(The fact that these are bounds means that setting the max as high as possible would make more sense then 67)

(Ingame) Set your cl_updaterate to 50, you will see 51 updates on net_graph
Now set your cl_updaterate to 66, you will see 67 updates
Now set cl_updaterate to 67, you will still see 67 updates

Now is the fun part.
If you change the tickrate on a server to 67 (-tickrate 67 commandline) and use cl_updaterate 67 you will see 68 on net_graph despite seeing 67 when we attempted the same thing with 66 tickrate. (This means the true value you should see with cl_updaterate 67 is actually 68/s in net_graph, but we saw 67 on a 66 tick server)

In other words what ever the servers tickrate is set to is the limit of cl_upaterate, setting the maxupdaterate to 67 on a 66 tickrate server won't do anything.

[nightrider]

After the most recent update of Counter-Strike Source to the Steampipe delivery system and Steamcmd,
Our CS:S server has had some major stutter lag without changing any of our previous network settings.
Is anyone else experiencing stutter?
Previously the server was rock stable without any stutter.
The only change was the conversion to the new Steampipe delivery system.

[Bacardi]

Have you Linux Or Windows server ?

[4square]

Originally Posted by nightrider After the most recent update of Counter-Strike Source to the Steampipe delivery system and Steamcmd, Our CS:S server has had some major stutter lag without changing any of our previous network settings. Is anyone else experiencing stutter? Previously the server was rock stable without any stutter. The only change was the conversion to the new Steampipe delivery system.

Finally i've found someone else with the same problem!!!

Hi Nightrider. I run 2 CSS servers. Before the latest steampipe upgrade we had almost 100% uptime with 0 lag and lovely rego. Since then, many of our players are experiencing massive 'jitter'.

Doing some research tonight, it would appear that the cause of this (or a contributing factor) is that players cannot send enough updates to the server.

Originally Posted by Server -tickrate 66 // server bandwidth and rate settings. fps_max 600 rate 30000 sv_minrate 20000 sv_maxrate 50000 sv_maxupdaterate 100 sv_minupdaterate 66 sv_maxcmdrate 100 sv_mincmdrate 66

Originally Posted by Client cl_cmdrate 100 "cl_cmdrate" = "100" ( def. "30" ) min. 10.000000 max. "cl_updaterate" = "100" ( def. "20" ) "rate" = "30000" "cl_interp" = "0.020000" ( def. "0.1" ) min. 0.000000 max. 0.50' "cl_interp_ratio" = "1" ( def. "2.0" )

This is what we run. Though the client, when using net_graph 2 (3rd column, 3rd line, c) will only be sending 67 down to 30ish updates. (he actual number of packets per second sent to the server (cl_cmdrate))

We are win2k8 64bit on 1x 4core xeon x3440 2.5Ghz (Hyperthreading enabled) with 8gb ddr3 ram.
Our network also hasn't changed, and i unloaded almost all surplus SM plugins with no change.

Sorry for the overload of info.
Very keen on getting this fixed

Cheers

[Ade]

someone said that on srcds.com people say fps_max should be set to 66 as it can't be any higher server side anyway, due to the tick
how true is that?