Actually according to valve, it's not them getting a lack of updates that they want. Instead it's the server trying to send MORE updates then the client can handle.
Ah, thanks for the correction. The end result and its solution, however, is the same regardless.
---------- Choke happens when the server would like to send data to a client but it cannot because the client is not yet ready for more data (based on the client's "rate" setting or the server's sv_maxrate).
Either way, it's obvious that if you're going to artificially limit the rate (which is perfectly fine, assuming you're doing it for a reason, such as trying to save bandwidth, instead of doing it just because you think you're supposed to), then
Some things are obvious causes for choke, such as the client's rate simply being too low for the number of players on a server. Other things might not be so obvious, such as a client raising their cl_updaterate value too high.
From that we can conclude that choke is merely an indicator of conflicting settings. Either force a low cl_updaterate (with sv_maxupdaterate) or raise up your sv_maxrate setting.
-- Eric (the Deacon remix)
"But I don't want to be a pie; I hate gravy!" -Babs (Chicken Run)
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
