minrate of 5000 is quite low, unless you're catering to dialup users. I
would try tweaking all of your min rates as well as the
splitpacket/splitrate cvars.
Choke itself is caused by the server holding back sending packets to a
player. This is due to the players rate being set too low to accomodate
however many updates they're requesting with their cl_updaterate
setting. In this particular instance that player has a cl_cmdrate and
cl_updaterate of 100, but they're only actually receiving 22 updates
from the server.
So my guess is that user has a low rate set. You can either tell him to
bump it manually, or force it to be higher with a higher sv_minrate
setting. The latter is the better choice in my opinion.
Read the last section of this wiki page for more info:
https://developer.valvesoftware.com/wiki/TF2_Network_Graph
On 8/5/2012 1:37 PM, Peter Reinhold wrote:
Only ones i've set in server.cfg is min and maxrate, 5000 and 0
(unlimited) respectively.
Rest are default, which for me is
sv_minupdaterate 10
sv_maxupdaterate 66
sv_mincmdrate 10
sv_maxcmdrate 66
net_splitpacket_maxrate 15000
net_splitrate 1
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
