Re: [hlds_linux] hlds update 23/10: forcing cl_updaterate to 20?
but now the red dots in net_graph 1 are back interp 0.01 fps_max 100, cl_updaterate 101 --> no red dots in net_graph (old version) fps_max 100, cl_updaterate 100 --> a lot of red dots fps_max 99, cl_updaterate 100 --> no red dots have the red dots in the net_graph an assertion anymore? 2. problem i dont understand the cl_cmdbackup one example cl_cmdbackup 0, in/out value 5k cl_cmdbackup 4, in/out value 6k cl_cmdbackup 6, in/out value 7k cl_cmdbackup 8, in/out value 6k cl_cmdbackup >= 10, in/out value 5k whats the matter with this? regards Original-Nachricht > Datum: Thu, 23 Oct 2008 16:39:04 -0400 > Von: "Richard Eid" <[EMAIL PROTECTED]> > An: "Half-Life dedicated Linux server mailing list" > > 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. 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 > to > 100, so it's left at the default value of 20 anyway. > > Just start instructing your community to use a value of 100 if their > connection and your server(s) permit it. > > -Richard Eid > > > On Thu, Oct 23, 2008 at 3: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: sv_maxupdaterate 100 > > > > player: cl_cmdrate 101 > > Results in forcing player to cl_cmdrate 20 > > > > > > Is there any way to avoid this but setting the sv_maxupdaterate to an > > orbital value? > > > > cheers > > > > marcel > > > > ___ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] hlds update 23/10: forcing cl_updaterate to 20?
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 change the sv_maxupdaterate to > 100, so it's left at the default value of 20 anyway. I know that 100 is max. But some idi...err "good players" provided the information that 101 is uber-over-skill-super-duper-mega-great.and well, many many players set their config to 101 :( And please agree that it's really stupid that the server sets the players value to the MINIMUM ,instead to the MAXIMUM when they set their own value MORE than the allowed max... Normally I would expect the engine setting it to the maximum allowed value. > Just start instructing your community to use a value of 100 if their > connection and your server(s) permit it. > > -Richard Eid I'll have tod o that, but I also that hope Valve will "fix" that problem. Alfred: See it as a feature request to avoid bad gaming experience for players that are not that common with editing their configs. - Marcel ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] hlds update 23/10: forcing cl_updaterate to 20?
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 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 setting the sv_maxupdaterate to an > > orbital value? > > > > cheers > > > > marcel > > > > ___ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > yeah, and when sv_minupdaterate is 30, and my cl_cmdrate is 20, then set it 100 automatically... Tyrael ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] hlds update 23/10: forcing cl_updaterate to 20?
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: sv_maxupdaterate 100 > > player: cl_cmdrate 101 > Results in forcing player to cl_cmdrate 20 > > > Is there any way to avoid this but setting the sv_maxupdaterate to an > orbital value? > > cheers > > marcel > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] hlds update 23/10: forcing cl_updaterate to 20?
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 to 100, so it's left at the default value of 20 anyway. Just start instructing your community to use a value of 100 if their connection and your server(s) permit it. -Richard Eid On Thu, Oct 23, 2008 at 3: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: sv_maxupdaterate 100 > > player: cl_cmdrate 101 > Results in forcing player to cl_cmdrate 20 > > > Is there any way to avoid this but setting the sv_maxupdaterate to an > orbital value? > > cheers > > marcel > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
[hlds_linux] hlds update 23/10: forcing cl_updaterate to 20?
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 setting the sv_maxupdaterate to an orbital value? cheers marcel ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
