The following is a list of (but is not limited to) the things that cause choke. It can be hard to completely remove choke on low end PC setups but if it's as low as you can get it, then that's about the best you can do. Keep in mind however, that Valve only implemented this for Local Area Network environments and sv_maxrate 30000 is still the recommended and encouraged value for online servers to use.Ĭhoke is quite simply the server wanting to send an update to the client, but cannot. The new hard coded maximum rate is 1048576 bytes, which works out to be 1024 kilobytes. You will want to keep this the same value of cl_cmdrate though, to avoid choke. (Most commonly an overloaded server host with too many game servers running off the single PC host AKA 'box').Īssuming the server and your own internet connection was able to handle it though, setting cl_updaterate 100 will mean that you get the full amount of updates as it is not bound by your own FPS in any way. Server performance is the factor in what you see in net_graph 3's IN, if it's not at 100 (As in when it can't hold it at all, not just a small deviation from the number for short periods of time) then it's typically safe to say that the server can not sustain the tickrate because of either bandwidth or CPU requirement. Setting this to 100 on a server with 100 tickrate server would normally mean that you get the full amount of update that is possible with the Source Engine, but this is often not the case.

This variables determines how many times you update the location of yourself and the things you do within the world. Max number of command packets sent to server per second.

Cs source steam charts