> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Ben Kennish
> http://www.serverwiki.org/index.php/Advanced_Tickrate ...
>
> "rate The Maximum amount of Bytes Per Second the Client will request
> from the server. rate overrides the servers sv_maxrate
> setting if rate is less than the servers sv_maxrate setting."
Rate and sv_maxrate are both values in Bytes per Second. This is a bandwidth
CAP (maximum flow limit) for network data transfer, on a per client basis.
These values are intended to allow clients or server admins to restrict
Source' use of bandwidth. At any one time, the lower of the two cvars is
used, unless the client cvar "rate" is below the servers sv_minrate, in
which case minrate is used.
> "cl_updaterate
> The Maximum amount of Updates Per Second the Client will
> request from the server. cl_updaterate overrides the servers
> sv_maxupdaterate setting if cl_updaterate is less than the
> servers sv_maxupdaterate setting."
Sv_maxupdate rate puts a maximal cap and is the finally determining upper
cap. If a client has cl_updaterate higher than sv_maxupdaterate then
sv_maxupdaterate is used. Sv_minupdaterate is a minimal cap on this value,
if the clients cl_updaterate is less than sv_minupdaterate, then
sv_minupdaterate is used.
> Also it would be good to mention exactly what sort of "better
> experience" the players can expect by increasing the tick rate etc?
The best Source gaming experience comes from setting the rates to what they
_should_ be - this includes for low bandwidth links and low tickrates.
Updaterate 12, rate 5000 at 33 tick is actually playable with cl_interp 0.1
on a stable server. There is little reason to run at a tickrate above 66,
unless playing on very high bandwidth low latency connections (where pings
should average under 10ms or so). Tickrate 33 is noticably slow, and
interpolation, client prediction, and collision resolution being what they
are, you will get a more accurate world representation running on tickrate
66 with sv_maxupdaterate 66 and cl_updaterate 66 with sv_maxrate & rate
above 16000. The fruits of this can be observed by watching the deviation of
server positioning to client positioning over different interp and rate
settings.
If someone wouldn't mind cleaning up / amalgamating and addiung to the wiki
I'd be much obliged.
___
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
