Fix the bug with the interpolation start #11
Merged
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.
Fixed
end_tick - send_interval_in_ticks
so that the interpolation is still done over roughly send_intervalTODO
However there are new issues uncovered with this PR:
interpolation_tick
seems to be not correct at the beginning, and is even bigger thanlast_received_server_tick
! I think there's an issue with how syncing is done at the beginningprediction_time
seems to be set too far in advance? Problem in sync---> all this seems to happen when i spawn both clients at the same time! If i spawn client 1 first, and then client 2 later, everything works fine.
---> as time passes, the objective time/prediction time are correcting themselves via speedup/speeddown, but it's weird how the initial time can be very bad.