--
[ Picked text/plain from multipart/alternative ]
The default sv_maxupdaterate for SRCDS is 60
"sv_maxupdaterate" = "100" ( def. "60" )
notify
- Maximum updates per second that the server will allow
My servers are 100 tickrate thus the output above.
I think most of us are aware that tickrate is the final arbiter of how many
updates per second a server can send to clients.
The question is, why is the sv_maxupdaterate defaulted to 60 on default 33
tickrate CS SRCDS and defaulted to 60 on HL2DM & DoD SRCDS which are both 66
tickrate?
Just to spell it out for some of you who are not familiar with the point I
am getting at.
On a 33 tickrate CS SRCDS the clients never receive more than 33.9 updates
per second (yeah its not exact, but its close enough) therefore a
sv_maxupdaterate of 60 is a complete waste, and if it is not, then I have
not seen a explanation as to the rationale why!
On a 66 tickrate HL2DM SRCDS the server wants to send 66 updates a second
but is limited to 60 updates a second by the default sv_maxupdaterate and
thus do not get the full benefit of running at 66 tickrate.
Why is it so? (Alfred will get that last line)
Cheers
--
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
