Richard Eid wrote:
101 isn't a real value for cl_cmdrate and cl_updaterate. 100 is the maximum
value for these CVars. I'm not sure what you mean by 'orbital value', but
there isn't, and has never been, any reason to set this above 100. Most
GoldSource server admins out there don't even
Datum: Thu, 23 Oct 2008 16:39:04 -0400
Von: Richard Eid [EMAIL PROTECTED]
An: Half-Life dedicated Linux server mailing list
hlds_linux@list.valvesoftware.com
Betreff: Re: [hlds_linux] hlds update 23/10: forcing cl_updaterate to 20?
101 isn't a real value for cl_cmdrate and cl_updaterate
Some players complain about bad ping. I saw that the cl_updaterate will
be forced to 20 if they chose a higher value than the server's
sv_maxupdaterate.
example
server: sv_maxupdaterate 100
player: cl_cmdrate 101
Results in forcing player to cl_cmdrate 20
Is there any way to avoid this but
101 isn't a real value for cl_cmdrate and cl_updaterate. 100 is the maximum
value for these CVars. I'm not sure what you mean by 'orbital value', but
there isn't, and has never been, any reason to set this above 100. Most
GoldSource server admins out there don't even change the sv_maxupdaterate
Set it to 100. Anything above 100 makes it reset to 20.
On Thu, Oct 23, 2008 at 9:27 PM, Marcel [EMAIL PROTECTED] wrote:
Some players complain about bad ping. I saw that the cl_updaterate will
be forced to 20 if they chose a higher value than the server's
sv_maxupdaterate.
example
server:
2008/10/23 Wiktor Deresz [EMAIL PROTECTED]
Set it to 100. Anything above 100 makes it reset to 20.
On Thu, Oct 23, 2008 at 9:27 PM, Marcel [EMAIL PROTECTED] wrote:
Some players complain about bad ping. I saw that the cl_updaterate will
be forced to 20 if they chose a higher value than the
6 matches
Mail list logo
