Make world's travelling transporters smoother#656
Merged
Conversation
Just like a gravship, travelling transporters (drop pods, shuttles) calculate their position in tick interval (once every 15 ticks if VTR is active). Since we always assume VTR is active on the world (besides gravships), this means they won't be moving too smoothly. I've set their update rate to always be 1 to fix this issue, just like with gravships. On top of that, I've rearranged the code into if/else branches to make sure we only assign the result once, instead of potentially twice.
SokyranTheDragon
added
enhancement
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
2 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.
Just like a gravship, travelling transporters (drop pods, shuttles) calculate their position in tick interval (once every 15 ticks if VTR is active). Since we always assume VTR is active on the world (besides gravships), this means they won't be moving too smoothly. I've set their update rate to always be 1 to fix this issue, just like with gravships.
On top of that, I've rearranged the code into if/else branches to make sure we only assign the result once, instead of potentially twice.