New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identify the source of latency issue in-game #15834

Open
FRenzy-OpenRA opened this Issue Nov 18, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@FRenzy-OpenRA

FRenzy-OpenRA commented Nov 18, 2018

It would be useful to identify where the source of a slowdown comes from, while being in-game.

Maybe a ping value for each player and spectator could be an indicator here ? Or the already existing latency values ("Good", "Moderate", "Bad" IIRC).

Also, should work with "In-game kicking" #3516

@FRenzy-OpenRA FRenzy-OpenRA changed the title from Identify connection performance (ping) in-game to Identify the source of connection issue in-game (ping) Nov 18, 2018

@FRenzy-OpenRA FRenzy-OpenRA changed the title from Identify the source of connection issue in-game (ping) to Identify the source of latency issue in-game Nov 18, 2018

@matjaeck

This comment has been minimized.

Contributor

matjaeck commented Nov 20, 2018

Not sure about it tbh. It won't help in the affected game unless you identify a specator as the "lagger" you could ask to leave.

My concern is that if you happen to "lag" once and people identify you, they could convince others that you are a terrible "lagger" and people should kick you from lobbies...

@FRenzy-OpenRA

This comment has been minimized.

FRenzy-OpenRA commented Nov 20, 2018

That is true.

There is still some kind of identification nowadays, and filtering.
Currently, in case of lag and in general, all spectators are asked to leave one by one (sometimes a player appears to be the cause), and usually they're remembered next games.

And in any case, kicking often happens before the start with latency values / colors.

I'd argue that sometimes, a game can go well even if players appear to lag before starting. And vice versa.

It is punishing for the players, and the potential spectators, not to be able to know where the problem comes from. And after deciding a re-make due to lag, it results in kicking a lot of spectators to avoid potential lag.

@netnazgul

This comment has been minimized.

Contributor

netnazgul commented Nov 21, 2018

Main problem with kicking potential laggers is that you can't remove them from the game once it is started, so people try to prevent it before. Ingame admin tools would be nice to have, and only then the ingame latency indicator might help.

@matjaeck

This comment has been minimized.

Contributor

matjaeck commented Nov 21, 2018

Actually, we already have the server messages that identify players with connection problems so this wouldn't make any big difference. Instead, we would know if for example a spectator is "lagging" and could ask this person to leave. At the moment it is common to ask all spectators to leave in the hope that one might be the "lagger".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment