Localstrike-team - Desarrollado por vBulletin
Seginos en Discord
Seginos en Youtube
Seginos en Facebook
Resultados 1 al 7 de 7
  1. #1
    Fundador Avatar de Venom
    Fecha de ingreso
    Aug 2019
    Ubicación
    Santa Fe, Santa Fe
    Mensajes
    118

    Post Guía de Rates [Por traducir]

    CSS Lag: Ping Loss and Choke

    Tips for less lag in Counter Strike Source

    This guide is for users with Counter Strike Source, but will also work with Counter Strike 1.6. Lag, ping choke and loss on CSS are all related, and can be cured in most situations. The steps below will help you lower your lag in game, and explain in detail exactly what it does, and what the terms mean.


    Lag - A term used to say that a persons connection is slow, lagging.
    Ping - This is a measure of the round trip time for a message to get from your computer to the server and back again, measured in milliseconds.
    Latency - This measures the one way trip time from your computer, to the server. (if you think about it, latency at any time is LESS than your ping)
    Rates - General term used for the speed settings of counter strike source


    Ping is NOT Latency



    Choke - Choke is server lag. Choke basically means that your computer is sending your players position, and what he does (shoot, nade, knife) to the server, and its not getting there. Counter Strike Source default is to send your players actions to the server 30 times a second. Choke is caused by two things:
    • Your computer is sending too many packets to the server per second. If you try to send 100 commands to the server per second, and it can only accept 40, you are going to be getting 60 choke. This will make you SUCK, none of your shots will register, and only 40% of the things you try to make your player do will be done. (for solution, see below)
    • The server is not able to read all of the information being sent to it. This can be caused by network lag at the server, or CPU lag at the server. The client cannot control this, but can accomodate for it (solution below)

    Loss - Loss is lag from outside your computer and usually outside the server. This means that while your commands that are going to the server, they are following a path (sometimes can be 30 networks your commands go thru before they reach the server) and somewhere in that path, the packets dont make it to the next place. Those packets are 'lost' in the bowels of the net. Loss can also come from wireless connections, in which case you can change your wireless channel to fix.. Loss is for the most part out of your control, and could always be the most common situation, your connection just plain sucks.



    net_graph 3 on CSS

    To start, you will need to be able to access the console in Counter Strike Source. Press the ~ button, and drop the console. Enter the command "net_graph 3" and press enter (to remove this later, net_graph 0). Once you leave the console, you should see in the lower right of your screen some numbers that look like this:

    Definitions of this menu:


    • FPS- How many frames per second your graphics card is doing
    • Ping- Round trip time from your computer to the server and back
    • Data - How many TCP/IP packets youre sending (you dont need to know this)
    • kilobits per second- how much actual data youre sending in and out (not needed)
    • How many times per second your computer updates your players position on the server (out -- the bottom one)


    How many times per second the server sends your computer players positions (in -- the top one)

    • Loss - explained above
    • Choke - explained above





    Steps to fix your lag in CSS

    The following steps are meant for anyone that can read (even n00bs). These steps will solve your network lag, as long as it has to do with your Counter Strike Source settings. Use this guide for fixing all types of lag.

    Note: Your ping may not be affected with these, but your lag will be cured.

    You are going to be changing your rates, in an educated guess and check method, to achieve the best rates for your computer. You will need to know how to read net_graph 3, and you will need to have it enabled. You need to join a server, to tweak these settings properly.


    To set your rates, enter the rate you want to set, then the number of times per second you want it set to.
    Example: cl_cmdrate 30


    cl_updaterate - How often your computer asks the server for players positions per second (default: 20)
    cl_cmdrate - How many times per second your computer sends your position to server per second (default: 30)
    rate - Maximum bytes per second you can receive
    cl_interp - Changes the speed at which players positions are updated






    Part 1 - Cmdrate and Updaterate
    • Enter a server and change your rates. cl_cmdrate 80 and cl_updaterate 60
    • Play the game for a few minutes. You will need to make sure that area 5 on the net_graph is not being limited by the server. If it stays at 33.3 or 66.6 all the time, it means you should tweak this on a different server that allows for higher rates (100 tick servers mean max of 100 updates and commands per second!)
    • Once you find a server that is not limited, you want to make sure your rates are cmd 80, and update 60. Play on the server for a few rounds, and keep an eye on your CHOKE and LOSS.
    • If you are experiencing choke, you will need to change your rates lower. The correct ratio for update to command means cl_updaterate should be 3/4 of cmdrate (75% is good)-- *This means CMDRATE is higher than UPDATERATE by a pinch*. So, lower your rates, keeping ROUGHLY the same ratio. If your choke is 30, lower your rates about 30 (but make sure you still use the ratio of 75%). This would mean cl_updaterate 35 and cl_cmdrate 50 (thats 70% ratio, close enough)
    • Try the new settings, and adjust your rates as needed. You want to lower your rates until you get less than 2 choke in the middle of a round, and less than 10 at the beginning, and end of a round. (choke is higher at beginning and end of rounds while server does stats, and resets objects)
    • Once you get to 0 choke, and 0 loss (loss may not change if it is a network problem) you have your proper rates.

    Part 2 - The rate setting in CSS
    The rate setting is used to set the MAX amount of data coming to you from the server in bytes per second. Rarely does your computer receive more than the max, and the more players on the server you are on, the more data you will recieve. On a 32 player server, you receive player positions, voice, chat, and nades weapons etc move. That will obviously use a lot of bandwidth to receive all that info.
    In short, heres what you set your rate to, its not very important to tweak.

    Connection Speed Set your rate to:56k or slower 1800comcastSlow DSL/Cable20000Fast DSL/Cable 25000


    Part 3 - Interp setting in CSS
    In Counter Strike Source, once your lag ping choke and loss are all fixed, you can improve your connection even more. The interp setting in CSS is used to tell your computer how fast to interpret the player and object positions sent to you by the server. The proper interp depends on your updaterate. Your cl_interp should be 1/updaterate. This means that if your updaterate is 50, your interp should be .02 - In the console type "cl_interp .02" or whatever yours should be. MAKE SURE YOU GET THE .02 and not just .2
    There is also an interp setting that sets your interp automatically, adjusting dynamically. I do not use it, and cant give any advice, but the command is cl_interp 0.



    CSS Rates Conclusion

    These rates you now have apply best for the server you are on, but will be around the best rates for your computer on Counter Strike Source. Factors affecting your rates can change second to second and server to server, but now you know how to lower lag


    [Solo usuarios registrados pueden ver los links ]
    _
    Citar Citar  

  2. #2
    Administrador Avatar de Furgoneta
    Fecha de ingreso
    Aug 2019
    Ubicación
    Buenos Aires, Capital federal.
    Mensajes
    77
    CSS Lag: Ping Loss and Choke

    Tips for less lag in Counter Strike Source

    This guide is for users with Counter Strike Source, but will also work with Counter Strike 1.6. Lag, ping choke and loss on CSS are all related, and can be cured in most situations. The steps below will help you lower your lag in game, and explain in detail exactly what it does, and what the terms mean.


    Lag - A term used to say that a persons connection is slow, lagging.
    Ping - This is a measure of the round trip time for a message to get from your computer to the server and back again, measured in milliseconds.
    Latency - This measures the one way trip time from your computer, to the server. (if you think about it, latency at any time is LESS than your ping)
    Rates - General term used for the speed settings of counter strike source

    Ping is NOT Latency


    Choke - Choke is server lag. Choke basically means that your computer is sending your players position, and what he does (shoot, nade, knife) to the server, and its not getting there. Counter Strike Source default is to send your players actions to the server 30 times a second. Choke is caused by two things:
    Your computer is sending too many packets to the server per second. If you try to send 100 commands to the server per second, and it can only accept 40, you are going to be getting 60 choke. This will make you SUCK, none of your shots will register, and only 40% of the things you try to make your player do will be done. (for solution, see below)
    The server is not able to read all of the information being sent to it. This can be caused by network lag at the server, or CPU lag at the server. The client cannot control this, but can accomodate for it (solution below)

    Loss - Loss is lag from outside your computer and usually outside the server. This means that while your commands that are going to the server, they are following a path (sometimes can be 30 networks your commands go thru before they reach the server) and somewhere in that path, the packets dont make it to the next place. Those packets are 'lost' in the bowels of the net. Loss can also come from wireless connections, in which case you can change your wireless channel to fix.. Loss is for the most part out of your control, and could always be the most common situation, your connection just plain sucks.
    hola, vengo a traducir un cachito nomas. espero traducirlo "legible" y con las menores falta ortograficas posibles xd.

    Lag en el CSS: Ping, Loss y Chocke
    Consejos para tener menos lag en el Counter Strike Source
    Esta guia es para la gente del CSS, pero puede funcionar tambien en el CS 1.6. Lag, ping y loss en el CSS esta relacionado, y tambien puede ser solucionado en la mayoria de las casos. Estos pasos a continuacion pueden ayudarte a tener menos lag en el juego, explicando en detalle que es lo que hace, y que es lo que el significa cada cosa.

    Lag - Es usado para decir que la conexion de una persona es lenta, lageada.
    Ping - Es la medida de tiempo transcurrido del viaje que toma un mensaje para llegar de tu PC al servidor y viceversa, medido en milisegundos.
    Latencia - Esto mide el tiempo que toma en hacer un viaje de tu PC al servidor (para que te des una idea, latencia es la mitad mas chica que tu ping).
    Rates - Termino general usado para describir la configuracion de la velocidad en el CSS.

    El Ping no es la latencia
    Choke - Choke es el lag del servidor. El Choke es basicamente cuando tu PC manda la posicion de tu personaje, y que es lo que hace (disparar, rebolear una nade, acuchillar) al servidor, y estos no son agarrados. En el CSS por defecto envia tus acciones de tu personaje al servidor unas 30 veces por segundo. Choke es causado por dos motivos.
    • Tu PC envia muchos paquetes al servidor por segundo. Si envias 100 comandos al servidor por segundo y solamente admite 40, vas a tener 60 de choke. Esto va a hacer que la PETEES, ninguno de los tiros van a poder registrarse, y solo el 40% de las cosas que intente hacer tu personaje van a poder hacerse. (para solucionarlo, mira abajo)
    • El servidor no es capaz de leer toda la informacion enviada. Puede ser causado por el lag de la conexion en el servidor, o el lag de la CPU del servidor. El cliente no tiene control de esto, pero puedes acomodarte para estas situaciones.

    Loss - Es el lag desde afuera de tu PC y por lo general afuera del servidor. Esto significa que cuando tus comandos estan yendo para el servidor, estos siguen un camino (aveces pueden ser 30 las redes que viajan tus comandos antes de que llegen al servidor) y en algun lugar del recorrido, los paquetes no llegan al destino. Estos paquetes estan "Lost" (perdidos) en las entrañas de la NET. Loss tambien puede ser por las conexiones innalambricas, en cual caso cambia tu frecuencia del wifi para arreglarlo. Loss en mayor medida esta fuera de tu control y puede ser en todos los casos que tu conexion es lenteja.

    espero haber contribuido xd.

    "Lurking eyes at your disposal!"
    GLA radar van.
    Citar Citar  

  3. #3
    Miembro Avatar de Mecha
    Fecha de ingreso
    Sep 2019
    Mensajes
    22

    Que traducción mas palabra de dios locoooooooo

    [Solo usuarios registrados pueden ver los links ]


    agradescanmelo en otra ocasión deah, hasta que corriga algunos errores y termine no voy a publicar la traduccicon completa jiji
    va aunque ya esta completa solo le falta que le arregle unos pares errores que supongo abre cometido jsjsjs salu2
    Citar Citar  

  4. #4
    Miembro Avatar de Mecha
    Fecha de ingreso
    Sep 2019
    Mensajes
    22
    nota: aganme acordar de que no envie más capturas ya que mi pc es una basura y no comprende que la única resolución no es 144p bueno en fin estaba traduciendo el tema de los rates
    Citar Citar  

  5. #5
    Admin CSS Avatar de Usb.
    Fecha de ingreso
    Sep 2019
    Ubicación
    Buenos Aires
    Mensajes
    32
    no es culpa de tu pc, subi la imagen a un host y ahi la pones acá
    Citar Citar  

  6. #6
    Admin CSS Avatar de Unline
    Fecha de ingreso
    Sep 2019
    Ubicación
    Granadero Baigorria
    Mensajes
    19
    Hola genio.
    La verdad que no entiendo nada, entre la foto miniatura y los errores ortográficos y de redacción estás para atrás amigo.
    Es imposible que tu pc haga un screen tan chico, el problema está en el hosting donde subís tu imagen, no lo hagas directo al del foro porque tiene poca capacidad de alojamiento y baja la calidad al mínimo-

    Hay muchos hosting de imagenes, podes googlear y elegir pero te dejo 2 claves

    [Solo usuarios registrados pueden ver los links ]
    [Solo usuarios registrados pueden ver los links ]

    Subí de nuevo la imagen, asi entiendo de que se trata xD
    salu2
    Citar Citar  

  7. #7
    Administrador Avatar de Furgoneta
    Fecha de ingreso
    Aug 2019
    Ubicación
    Buenos Aires, Capital federal.
    Mensajes
    77
    seguro nos quiere vender de jamones.

    "Lurking eyes at your disposal!"
    GLA radar van.
    Citar Citar  

Permisos de publicación

  • No puedes crear nuevos temas
  • No puedes responder temas
  • No puedes subir archivos adjuntos
  • No puedes editar tus mensajes
  •  

Go to the top of the page