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

Increase the client/server update rate to 125 Hz and 100 Hz #982

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Calinou
Copy link
Member

@Calinou Calinou commented Dec 26, 2019

This needs playtesting before it can be merged. While this should be fine on paper, it's possible that this is too much for less-than-ideal connections (4G, distant servers, …). I can host a 24/7 server with this pull request if this is desired 🙂

This decreases effective latency significantly by making clients and servers sending and receiving updates sooner. This increases network traffic by a factor of 3, but it should be manageable on today's networks.

The average game-induced latency (on top of network lag) should now be 14 ms (10 ms server + 0-8 ms client) instead of 60 ms (40 ms server + 0-40 ms client).

See https://extra-a.github.io/#bnet for more information.

This decreases effective latency significantly by making clients
and servers sending and receiving updates sooner. This increases
network traffic by a factor of 3, but it should be manageable
on today's networks.

The average game-induced latency (on top of network lag) should
now be 8 ms instead of 40 ms.

See https://extra-a.github.io/#bnet for more information.
@Calinou Calinou changed the title Increase the client/server update rate to 125 Hz Increase the client/server update rate to 125 Hz and 100 Hz Dec 26, 2019
@qreeves
Copy link
Member

qreeves commented Dec 29, 2019

Needs further testing and discussion.

Copy link
Member

@q009 q009 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The idea appears worth exploring to me. However, I think it'd be worth to put those behind variables, so the users can tune those. So, worst case scenario, the gist of the change may remain, only the final value of the variable would see further tweaks.

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

Successfully merging this pull request may close these issues.

3 participants