The netgraph

[Urmel]

Since 2.3 we have a cool new feature called netgraph. I like it. However, nobody seems to be able to give me detailed information about what it's trying to tell me.

There are orange (or yellow) graphs, white and red ones, and sometimes I think there are green ones, and the "incoming" window is very populated, while the "outgoing" one mainly contains emptiness.

The orange ones seem to be the rather harmless ones, while white and red ones are quite suspicious to be a bad sign for my performance. The green graphs are completely cryptic to me, which I don't mind as they barely appear.

Afaik LordHavoc coded the netgraph, maybe this is the way to get him to talk about his creation? I'd really like to know all about it...

[Urmel]

*bump*

80 hits and nobody knows...

[:)]

I think red means "not able to connect at that time"
White is maybe a lost packet?

Here's a typical netgraph for me:

[kyre]

Red's packetloss. Orange are a received packet, the height indicates time it took. Dunno about the other colors.

[Mr.Carlyle]

I think red means "not able to connect at that time"
White is maybe a lost packet?

Here's a typical netgraph for me:

Ouch...I've never used to see packet loss that much, but since I"m now behind a router I'm experiencing it. Its not very fun and I wish I could say I feel your pain but, my netgraph doesn't look anything like yours.

[LordHavoc]

First the bad/special ones:
Red is lost packet (out of sequence packets also count as lost as they are no longer relevant by the time they are received) - you want as little of this as possible!
Yellow is choked packet, meaning that your rate limit is set too low - note this only shows on your outgoing graph (incoming does not know if packets were choked).

If it's not one of those colors, then it is a bar graph showing how much of each of the following traffic occurred in the given direction (received or sent):

Orange - normal unreliable messages, this includes input (which looks like a pretty flat block, sometimes interspersed with yellow if your rate is set too low), explosions, sounds and other effects, as well as game objects and most other data.

White - reliable messages, such as chat, death messages, scoreboard frags/colors/name updates, screen flashes from item pickups, centerprint text (while spectating for example), and assorted other things that occur less frequently (such as when changing level).

Green - acknowledgement of receipt of reliable messages, for example when chat is received by the client, the input graph will show a green blip due to sending an acknowledgement packet, and if you send chat, the world (data from the server) graph will show a green blip a moment later.

There are two different graphs, one for world updates (from the server), and one for input (from you), the input one tends to look very boring as it uses a steady amount of bandwidth (other than chat), the world one varies wildly, and gets very high in fighting, eventually hitting a plateau when it reaches your rate limit.

Adjusting rate limit (higher or lower) can improve play, and cl_netinputpacketsperserverpacket can be adjusted when using cl_movement 1, other than that you have very little control over the network conditions.

[Urmel]

aah nice, at last, that will help

many thanks!