Rates For Specific System Thread

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Spencer/

    #16
    Re: Rates For Specific System Thread

    This is gonna sound real dum but are there any patches in css that automatically detect server rates and fix them to it. Cause i see here on the third post people are saying to put rates like this

    100 tic

    cl_updaterate 100
    cl_cmdrate 100
    rate 20000
    ex_interp 0

    66 tick would be

    cl_updaterate 66
    cl_cmdrate 66
    rate 20000

    I have been in rooms before and people tell me to put 100 101 30000 or 66 66 25000 and these are the admins but yet here it says different. I even got into it with an admin the other day about this and he said rates are different for each room. But i don't know im lost. I hear in a lan server it automatically detects rates just wonderin if there was any way i could do this with a patch upon entering a room cause rates really make the difference. And one more thing someone mentioned net_graph 3 don't really know how to read it. If anyone has some answers for me it would really be cool.

    Comment

    • Sintra
      Member
      • Aug 2026
      • 0

      #17
      Re: Rates For Specific System Thread

      Ugh, I really don't remember all too much from rates. I posted lots of info back in the day.

      rate 30000 or rate 25000 is the same as rate 20000. The hl engine is limited to rate 20000, so there's no point in going over the limit. It makes no difference, as I mentioned somewhere before.

      There are no patches. But you should be able to find scripts that change rates on the fly.
      As said before, cl_updaterate should be set to the server's sv_maxupdaterate and rate should be set to the server's sv_maxrate, exception being when this value is 0, which means you can set rate to 20000.
      net_graph 3 shows info on screen. It displays ping, choke and loss. Ping is the round trip time, or in simpler words, the time information takes from your computer to the server and then back. Choke represents packets that are being sent/received too late. Any connection can have 0 choke; this conveys a sense of fluidity to the game. Loss represents packet loss. Basically if you have this, you probably just can't play on that particular server. You can maybe minimize it, but that is rarely the case.
      So, having net_graph running allows you to check your choke in order to completely remove it by tweaking updaterate and cmdrate. You can check to see if the connection is bad, either by high ping or by having loss.

      Comment

      Working...