Antilag refactor #3
Open
Conversation
This file contains 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
…d be removed, and some others seem to have been done incorrectly.
…than that just added more comments so the code can be understood more easily later on,.
…ecks to prevent unnecessarty shifting of clients to reduce load (due to higher trail count). Now that more trails are stored, it's unnecessary snap and clamp the trail time. the more precision and information we have the better.
Moved check that prevents clients trying to timeshift too far back (> 500ms). Replaced IS_ACTIVE macro with function.
…ft even if it's surpassed level.time. level.time is only incremented every 50ms (sv_fps = 20).. so high fps clients can catch up and even surpass before the next 50ms increment can happen. if there are no clients with a trail <= than this really fast client's serverTime, then it'll just end up using server's current player states for collision detection anyways, so it's a-okay.
…it easier to read/understand (imo).
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.
The interpolation was going in the wrong direction, that has been fixed.
There were only 10 samples (trail nodes) per client that spanned 500 ms. 125 fps clients send around ~64 usercmd packets every 500ms; so I increased the samples to 64, and rate limited trail node storage for clients > 125 fps.
Due to the added granularity, this also means there's no need to have "leveltime" checks (& snapping) anymore; so that was all removed.