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

LockstepNetcode: Handle case where state sync arrives early #81

Open
rameshvarun opened this issue May 12, 2023 · 0 comments
Open

LockstepNetcode: Handle case where state sync arrives early #81

rameshvarun opened this issue May 12, 2023 · 0 comments

Comments

@rameshvarun
Copy link
Owner

Right now there's an edge case in LockstepNetcode where the host's authoritative state sync can arrive before a client actually reaches that frame (and thus the client can't apply the state sync). This is mostly likely to happen when communicating over localhost.

The fix is to queue the state syncs if they arrive early.

It should be impossible for a state sync to arrive late since the sync is sent before the host's inputs. Without the host's inputs, we can never advance past that frame.

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

No branches or pull requests

1 participant