How to fix your rates.

Home › Forum Archive › Club Services › How-to Information › How to fix your rates.

Viewing 20 posts - 1 through 20 (of 20 total)
  • Author
    Posts
  • #2908
    Brian
    Spectator

    cl_cmdrate “101”

    cl_interp “0.01”

    cl_interpolate “1”

    cl_lagcomp_errorcheck “0”

    cl_lagcompensation “1”

    cl_smooth “1”

    cl_updaterate “101”

    rate “30000”

     

    this is what your rates should be set at. None of the 0.02 interp bull*edited* please, that creates unnecessary latency since we are on a 100 tic server and can utilize 0.01 interp.

     

    Unless you are getting choke/loss on this cl_lagcomp_errorcheck “0” is what you need other it will waste resources if you getting neither of those which is what these rates as a whole should accomplish, if you have rates otherwise and you are getting 0 loss/choke then there is no problem. 0 loss/choke means you are very rarely if ever going to have unregistered shots, that being said it can still be helped even more by having you monitor refresh rate and max fps in game the same as your cmdrate and updaterates, basically locked at 100.

     

    The last steam update said something about the max rate being at 1Mb now, I don’t know how to utilize that atm, sorry. It ain’t really a problem if you are getting no choke or loss.

    #27056
    Kuros
    Spectator

    .02 interp isn’t really as bad as a lot of people who come in with .04 or .05.

    #27064
    Writhen
    Spectator

    O_o

    #27082
    MasterP
    Spectator

    Cmdrate can go as low as 20 without causing trouble, below that you start causing trouble for everyone.

    #27090
    Liam
    Spectator

    MasterP said:

    Cmdrate can go as low as 20 without causing trouble, below that you start causing trouble for everyone.

     

    Yes, you can set it client-side to be as low as you want, however, the server will force you to a minimum of 70 I believe.

    #27118
    MasterP
    Spectator

    Post bashing isn’t the point of this thread either. Was mearly pointing out that a cmdrate of 100 is fairly high. Btw, server enforcement of rates isn’t terribly common.

    #27129

    Servers allow people to use a cmdrate of 100 because it betters the registry and people’s shots. With sv_pure as well as the cvar’s now, we can set the minimum to what people’s rates go to. We don’t have sv_pure enabled but we have set up the cvars so that people do no longer play at 20/30 default rates but instead now have the rates bumped up to a minimum of 66 cmdrate and I believe 66 updaterate. It only changes the rates to those that are lower than what the cvars have set and if they are higher than the cvars then the server does nothing to the client. These cvars do not cause other players to lag once when they did not before and they do not cause the server to lag at all as well. Many public servers with 100tic enabled have set up these cvars so that registration is at its best, you just don’t realize it. Go into a handful of public servers with default rates of 20/30 and then try changing them after you’ve entered the server, see if your rates aren’t something like 66 or higher afterwards.

    #33647
    Grimmjow
    Spectator

    Well TY for this imma def try it out since nothing ever regs in the pub for me :(

    #33871
    B R I E F S
    Spectator

    my fps is a constant 60, I tried alot of things with my rates, and they are currently configured to the first post of this thread, still 60 fps, any suggestions? and yes, I have it set to fps_max 101

    #33875
    Liam
    Spectator

    B R I E F S said:

    my fps is a constant 60, I tried alot of things with my rates, and they are currently configured to the first post of this thread, still 60 fps, any suggestions? and yes, I have it set to fps_max 101

     

    Turn off vsync.

    #33876
    starterat
    Spectator

    does it help for other games too like, i dunno, tf2?

    #33879
    Liam
    Spectator

    starterat said:

    does it help for other games too like, i dunno, tf2?

     

    This should. They’re both running the HL2 engine.

    #33898
    starterat
    Spectator

    sweet then

    #33901
    MasterP
    Spectator

    If it’s a solid 60 then leave the Vsync on. If your card is running Vsync at full speed you might try increasing the resolution or cranking AA/AS up, you’ve got the power for it.

     

    Having 300 FPS does you no good when your eye can only detect around 30.

    #33974
    B R I E F S
    Spectator

    whats the command for turning it off lol?

    #40313
    MajorMajorMajor
    Spectator

    ok so i did all these changes and my choke went from 0 to 30 (avg)

     

    what can i do to fix this?

    #40320
    MasterP
    Spectator

    Brian said:

    cl_lagcomp_errorcheck “0”

    Unless you are getting choke/loss on this cl_lagcomp_errorcheck “0” is what you need other it will waste resources if you getting neither of those which is what these rates as a whole should accomplish, if you have rates otherwise and you are getting 0 loss/choke then there is no problem. 0 loss/choke means you are very rarely if ever going to have unregistered shots, that being said it can still be helped even more by having you monitor refresh rate and max fps in game the same as your cmdrate and updaterates, basically locked at 100.

     

    Set:

    cl_lagcomp_errorcheck “1”

    #40356
    Nickname
    Spectator

    cl_cry 0

    #67093
    SpartaN beaR***
    Spectator

    for CS 1.6 rates this thread has the correct information: http://www.wcugaming.org/forums/index.php?showtopic=6840

    #67120
    Ex
    Spectator

    MasterP said:

    If it’s a solid 60 then leave the Vsync on. If your card is running Vsync at full speed you might try increasing the resolution or cranking AA/AS up, you’ve got the power for it.

     

    Having 300 FPS does you no good when your eye can only detect around 30.

    actuly your eyes can detect more than 30 fps its more like 45 to 60

Viewing 20 posts - 1 through 20 (of 20 total)
  • The forum ‘How-to Information’ is closed to new topics and replies.