[GOMPS-522] fixes character jitter in high packet loss scenarios #326
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nced, unreliable). This significantly improves user experience in high-packet-loss scenarios
fernando-cortez
approved these changes
May 11, 2021
Contributor
fernando-cortez
left a comment
fernando-cortez
left a comment
There was a problem hiding this comment.
Tested this before + after this addition with LiteNetLib's injected latency (min 80ms, max 120ms, 10% packet loss).
What was really noticeable was that the big teleports essentially disappeared. We need to document this for easy improvements to movement syncing.
Cosmin-B
approved these changes
May 12, 2021
Contributor
|
@lkrell See above! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have moved position and rotation to the MLAPI PositionUpdate channel, which is {Unreliable,Sequenced}. This significantly improves the user experience in high packet loss scenarios.
I tested with clumsy, 50ms of bi-directional latency (measuring 250ms RTT in game), and 10% packet loss. Without this change, movement and camera were both horribly janky. After the change, the experience was largely tolerable, with occasional subtle disruptions (not too bad, considering 10% packet loss is pretty rough!)