Changed BTTask_FlyTo to provide MovementComponents with normalized inputs #16
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
…put vectors instead of raw deltas to the next waypoint, as this is consistent with how normal PathFollowingComponents give input to MovementComponents
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.
Currently BTTask_FlyTo provides Pawns' MovementComponents with input vectors that are the raw deltas from the pawns' locations to their next waypoint target -- usually a few hundred centimeters long. This is subjective, but for me I would expect BTTask_FlyTo to provide normalized input, as that is the convention used by normal Unreal PathFollowingComponents and most character controllers. This PR implements the latter behavior.
Thank you for all your hard work on DoN!