Tickrate is the number of clock cycles (I believe) that the server processes (per second?). Someone else could explain much better here I'm sure - but basically it increases the amount of processing power it uses to run your server - and therefore provides much more stable pings in my testing .. And is why I now run with '-tickrate 66' on the command-line for my server. Hitboxes seem to register much better as well.
Are you absolutely positive your client settings are 20000/100/100 - and that some unscrupulous admin didn't change them on you (with a client exec admin command) without your knowing? Please go verify them for me while in CS by typing all three for me (rate, cl_updaterate, cl_cmdrate). If they are correct, I'd like to see a screenshot of your net_graph data along with the scoreboard on that same screen showing the 'strange' ping. You can post it on my Counter-strike website. Let me know when you have it ready and I'll set you up on there. Also, have you tried another server to see if it displays the same 'strange' ping on there? You can try mine if you'd like: 65.69.123.132:27015 Kevin Whisper <[EMAIL PROTECTED]> wrote: >Here is the things that I don't understand The Server can be a 33 or 66 tickrate server. > >Both with default sv_maxupdaterates > >My clients rates are 20000/100/100 > >Yes Im aware of the fudge you can do by lowering your rates to give you a very low ping, but in the case I presented initially I >am not doing anything to manipulate them from my normal game play. > >Thanks _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
