Net graph 3

From ETCwiki
Revision as of 13:46, 11 September 2009 by Ddxfish (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Net_Graph 3

Net Graph 3 is a tool that counter strike source displays on your heads up display. It shows all relevant info about your connection to the server. 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:

ping choke loss lag css net_graph 3

  1. FPS- How many frames per second your graphics card is computing
  2. Ping- Round trip time from your computer to the server and back
  3. Incoming Packet Size - size of incoming packets from the server
    1. Measured in bytes, this shows the size of the current incoming data packet from the server.
  4. Incoming Data - how many kilobytes per second you are receiving from server
    1. Incoming data rate = (Average Incoming Packet Size) x (Inbound packets per second) / 1000
    2. This number will spike during round change, when grenades blow lots of objects around, and when you are around many other players
  5. IN Packets Per Second - times per second your computer is receiving info from the server
    1. This is set by cl_updaterate
  6. Outgoing Packet Size - size of outgoing packets from your computer
    1. Measured in bytes, the size of each packet sent to the server.
  7. Outgoing Data - how many kilobytes per second you are sending to the server
    1. Outgoing data rate = (Average Outgoing Packet Size) x (Outbound packets per second) / 1000
    2. This number should not spike often, and should remain roughly the same always
  8. OUT Packets Per Second - times per second your computer is sending info to the server
    1. This is set by cl_cmdrate
  9. Loss - packets that are not reaching the server
    1. Loss should be 0 all the time. If you have loss, chances are you cant fix it at your computer.
  10. Choke - packets that failed sending to or from server
    1. Choke should be below 10 during mid round play, or there will be lag.