Ping is not displayed anymore

[coopson]

"Ping is not displayed anymore unless there is a connection problem or if the ping is above 500ms."

Wut ? why would you do this it takes ages to get a game of 4 vs 4 full and the last thing you want in your game is people with high ping you start the game only to find it lagging and having to rehost.

[IceDreamer]

If someone ping is not over 500, they won't lag the game. So to stop people who don't know how the game works from kicking people with 450 ping (Who won't lag the game) unnecessarily, it has been hidden unless it is 500+ or there is another connection problem.

[errorblankfield]

I wonder if the cut off should be 500ms though... I mean if someone has a 499 pint, I wouldn't exactly hedge my bets on them never going over ping wise mid-match.

If I remember my lingo right, that's jitter I'm referring too. I'll assume we could tie in a jitter test to ensure even at the worst peak, it's under 500ms (or 490ish to be safe).

But yea, it's intended for reasons above.

[SomeoneAUS]

The way supcom communicates is with updates every 500ms. It sends out an update and expects to receive an update very 500ms. It is only if the game does not get an update from the other players within 500ms that it pauses while it waits for that update to come through. That pause is the lag that we experience.

If someone has a ping of 450 then it takes 450 ms for their update to get to you. Supcom waits receives the update at 450ms and thus will not pause and wait at 500ms allowing for smooth gameplay.

Problems occur when you ping is higher than the 500ms say its 550...

Supcom sends its update and expects to receive an update within 500ms at 500ms it has not received its update so the game freezes... supcom receives the update 50 ms (1/20th of a second) later and continues on. That 50ms over 500ms is what you see as lag. Every 1/2 a second (500ms) the game pauses for 1/20 of a second (50ms).


The difference between a 50ms person and a 450ms person is nothing as the game continues provided the update is received before 500ms


The above post is correct if a link is congested your ping will vary depending on how busy the link is at that exact time. That is jitter. The variance in latancy. Someone with 0 jitter will be fine with 500ms as they will never go over. However if you have 20ms jitter you would want to be under 480ms so that it never goes over. Otherwise when it does your little pause it detected...

I believe faf measures maxumin ping therefore ping of 250ms with 20 ms jitter actually shows up as 270ms so provided faf shows under 500 you should not see errors except for in cases of packet loss.

I hope that clears things up.

[Ze_PilOt]

That jitter is mostly caused by a limited bandwidth reaching its limit, and can't be seen in the lobby.

[SomeoneAUS]

How much bandwidth does supcom use late game. Maybe we could increase size of ICMP packet to simulate this while you do latancy test?

I fully appreciate the change implemented just wondering if we can find a way to better determine gameplay before starting the game.

[Ze_PilOt]

I don't think there is any packet size control available, so no.

[E8400-CV]

The locigal consequence of this will be that now all aussies get kicked instead of just the ones with the highest ping. Or are you gonna hide flags as well?

[Ze_PilOt]

If it has to go to that, yes.

It's up to users to be less stupid, or I will keep removing functions that are misused.

[E8400-CV]

Pff.. it's not stupid to kick someone with 400 ping. In reality, usually they go way over 500 after twenty minutes in the game.