fix: new interpolators delaying between stopping and starting #3413
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 fixes the issue where a server authority instance would lag behind when using the new interpolators. This was especially visible when the moving body completely stopped, all state updates were processed, and then shortly later it began to move again there would be a delay between the 1st state update and the rest of the pending state updates.
This also fixes an issue where if the frame rate takes longer than the tick frequency authority instances could invoke the same check for state changes more than once in the same frame. This is not needed since changes to the transform are frame driven and the check should only be performed once per new tick(s).
MTT-12027
Changelog
NetworkTransform
could check for state updates more than one time in a frame if the frame rate is slower than the tick frequency.Testing and Documentation
InterpolationStopAndStartMotionTest
.Backport
No backport is needed for this update since it pertains to 2.x only features.