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

Reduce bandwidth usage #1451

Merged
merged 8 commits into from
Sep 10, 2024
Merged

Conversation

stilnat
Copy link
Contributor

@stilnat stilnat commented Sep 5, 2024

Summary

Roughly reduce bandwidth consumption by a factor 6, from an average by client of 30 KB/s sent to server to 5 KB/s sent to server.

Current bandwidth usage is terrible for two reasons :

  • Server tick rate is way too high for this kind of game (120/s)
  • We sync way too much transforms of stuff that do not need to be synced.

Solution :

  • cut tick rate to 30/s (imo enough for this kind of game, we're not a competitive fps).
  • do not sync transforms that do not need syncing : that includes stuff in containers as they can rely solely on the networked container transform, and that include ragdolls not ragdolling.

This PR does not deal with reducing the impact of ragdolling, which is going to be an issue later. I got a few ideas but that require a PR on its own and I rather focus on other things for now.

PR checklist

  • The game builds properly without errors.
  • No unrelated changes are present.
  • No "trash" files are committed.
  • Relevant code is documented.
  • Update the related GitBook document, or create a new one if needed.

Testing

  • Open one client, one host
  • Move client around, taking stuff
  • See the average bandwidth usage and compare to the actual one

Copy link
Contributor

@iamteapot422 iamteapot422 left a comment

Choose a reason for hiding this comment

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

Good

@iamteapot422 iamteapot422 merged commit 9da104d into RE-SS3D:develop Sep 10, 2024
2 checks passed
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