Fix stale data impacting predictive interpolation#75
Merged
Extremelyd1 merged 3 commits intoMay 30, 2026
Conversation
Add OnDisable to clear init/sequence state when a player container returns to the pool, and move position/state seeding into OnEnable so a recycled container starts from the position SpawnPlayer set on the transform rather than leftover values from the previous player.
Replace hard-coded RTT/correction/decay numbers with the Good-tier entries from the existing tier arrays so the spawn-state baseline is consistent with the rest of the adaptive system.
Early-out of ManualUpdate before anything runs so nothing is integrated until the first authoritative server packet arrives.
Liparakis
approved these changes
May 27, 2026
Extremelyd1
approved these changes
May 30, 2026
Owner
Extremelyd1
left a comment
Extremelyd1
left a comment
There was a problem hiding this comment.
Thanks fireb0rn, this looks great!
Extremelyd1
changed the title
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
3 participants
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.
Previously, this MonoBehaviour could be enabled holding stale data from the last time it was active. This resulted in an effect where, when a player entered a scene, their character would "flash" in an arbitrary location (from ForceSnap(_lastServerPosition) before their position updated to its correct location. This was mainly problematic in player vs. player games, where it would give away when a remote player is within a scene. Other changes are just minor cleanup.