Skip to content
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

Refactoring connectivity windows #3658

Conversation

Garanas
Copy link
Member

@Garanas Garanas commented Feb 3, 2022

Refactors the connectivity windows to:

  • (1) Improve performance, no more GetSessionClients() each frame
  • (2) Improve readability
  • (3) Improve communication

(2) is done by appending the ping with a box plot: we sample the ping over X seconds and compute some statistical data over it. We visualize this with a small box plot. The tooltip will contain information about what is seen in the box plot. This should give you a better idea of how the connection between you and someone else performs.

(3) is done by adding a button that allows you to send your ping information to the game. As an example, if you suspect someone is lagging then you can click this button and the boxplot is translated to some string that represents the relevant information.

@Garanas
Copy link
Member Author

Garanas commented Feb 3, 2022

This PR is delayed until #3659 is merged.

@Crotalus
Copy link
Member

Crotalus commented Feb 3, 2022

Will the new connection window show "jitter" i.e. min / max values of the ping? Fluctuating ping often indicates loss of packets / lack of bandwidth while a stable 400 ping could be completely fine.

@Garanas
Copy link
Member Author

Garanas commented Feb 3, 2022

Yes - the idea is this:

image

But then with a better UI. The box plot will be more informative about how the ping evolves over time. Left is 0 ping, right is 600 ping. The tooltip will contain a description of the boxplot so that people can make their own interpretations. It will also contain the fact that any (stable) ping < 500 is fine, to help all those poor Australians 😄 .

@Garanas Garanas force-pushed the improve-disconnection-dialog branch from 53efb0d to 3e840e6 Compare February 4, 2022 18:48
@Garanas
Copy link
Member Author

Garanas commented Jun 25, 2022

Closing due to the introduction of the new UI build pattern, which this PR doesn't use.

@Garanas Garanas closed this Jun 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants