Skip to content

Changed BTTask_FlyTo to provide MovementComponents with normalized inputs#16

Open
OregonJunco wants to merge 1 commit intoVSZue:masterfrom
OregonJunco:Normalized_MovementComponent_Input
Open

Changed BTTask_FlyTo to provide MovementComponents with normalized inputs#16
OregonJunco wants to merge 1 commit intoVSZue:masterfrom
OregonJunco:Normalized_MovementComponent_Input

Conversation

@OregonJunco
Copy link
Copy Markdown

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!

…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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant