Allow the time difference to jump when it notices that its consistently too far off from the true value - #3479
Open
IntegratedQuantum wants to merge 1 commit into
Conversation
…ly too far off from the true value
Contributor
Member
Author
|
same account multiplayer is no longer supported as of #3434 |
Contributor
Member
Author
|
This is unrelated too #3477 |
Contributor
Member
Author
|
Can you not host local with different account? |
Contributor
|
I am not sure where my account key is, so changing account might make me lose my current one. |
Member
Author
|
Then set a different cubyz dir in the launch config |
Member
Author
|
or, even better, copy it from the settings file and store it somewhere secure this time |
Contributor
Contributor
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
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.




This is detected by checking whether the last 5 seconds worth of samples were off in the same direction, at which point it should be obvious that the old estimate is wrong by a big margin.
This improves correction of an issue on startup where the initial time difference is overestimated, causing interpolation on the client to be incorrect.
(Note this does not fix the root issue, I'll make an issue for the root issue in a bit)
@iNiKKo Please confirm that this fixes the issue, it will still be present for 5 seconds, but then it should fix itself.