Upvote Upvoted 6 Downvote Downvoted
What is "choke" and "loss" in net_graph ?
1
#1
0 Frags +

Helo, I've been having problems with certain french servers and it seems most of them come from varying numbers in "loss" and "choke" shown in net_graph 3.

http://i.imgur.com/k84wqNg.png

I know loss reffers to "Packet loss" but what do the numbers mean?
Does "loss: 5" mean 50% packet loss?

What is choke and how do I avoid it ?

Helo, I've been having problems with certain french servers and it seems most of them come from varying numbers in "loss" and "choke" shown in net_graph 3.

[img]http://i.imgur.com/k84wqNg.png[/img]

I know loss reffers to "Packet loss" but what do the numbers mean?
Does "loss: 5" mean 50% packet loss?

What is choke and how do I avoid it ?
2
#2
0 Frags +

I think it's number of packet within the last second (or whatever period is used for updating).
I'm not certain enough about choke but it's either the server struggling or network problems.

I think it's number of packet within the last second (or whatever period is used for updating).
I'm not certain enough about choke but it's either the server struggling or network problems.
3
#3
4 Frags +

TF2 Network Graph from the Developer Wiki will explain it

[url=https://developer.valvesoftware.com/wiki/TF2_Network_Graph]TF2 Network Graph from the Developer Wiki will explain it[/url]
4
#4
-19 Frags +

choke = percentage of data packets that are being lost FROM the server.

loss = percentage of data packets that are being lost TO the server.

choke = percentage of data packets that are being lost FROM the server.

loss = percentage of data packets that are being lost TO the server.
5
#5
serveme.tf
37 Frags +

Choke: Server has decided to not send you a packet because your "rate" is insufficient to receive the number of packets you requested ("cl_updaterate"). Packets can vary in size, in busy fights there's more information per packet, so this can be why you don't see choke all the time.

Solution, increase your "rate".

Choke: Server has decided to not send you a packet because your "rate" is insufficient to receive the number of packets you requested ("cl_updaterate"). Packets can vary in size, in busy fights there's more information per packet, so this can be why you don't see choke all the time.

Solution, increase your "rate".
6
#6
7 Frags +

#4
Completely wrong, both work both ways. Choke is also something completely different.

-> -frag #4, +frag #5

#4
Completely wrong, both work both ways. Choke is also something completely different.

-> -frag #4, +frag #5
7
#7
0 Frags +

thank you based arie
i still dont get why i get choke in specific french servers when all other servers always show choke 0

I will increase my rate to try to avoid this (currently 35000)

thank you based arie
i still dont get why i get choke in specific french servers when all other servers always show choke 0

I will increase my rate to try to avoid this (currently 35000)
8
#8
1 Frags +

Recently ive been getting regular choke spikes even though ive been using the same net settings for a long time

so is it still the net settings that are a problem or something else?

Recently ive been getting regular choke spikes even though ive been using the same net settings for a long time

so is it still the net settings that are a problem or something else?
9
#9
2 Frags +

Server side rates can be too low too, in case of either shitty configs or shitty bandwidth.
Then you have 2 options:
1. Lower cmdrate and updaterate to reduce the bandwidth you need.
2. Don't play on those shitty servers.

Server side rates can be too low too, in case of either shitty configs or shitty bandwidth.
Then you have 2 options:
1. Lower cmdrate and updaterate to reduce the bandwidth you need.
2. Don't play on those shitty servers.
Please sign in through STEAM to post a comment.