Move to Location, AI Move To, Simple Move to Location - are always 0,0,0 velocity in first frame

[eblade]

@wab11

O course you’re right. But Epic himself try to adapt Unreal Engine for as many types of project as possible.
Another problem is: I don’t want to write two thousand lines of code for achieve one little things. Especially if Epic programmers can change Engine in few lines probably.

You have access to the complete engine code. Or you can simply override whatever class implements the problem behavior, and implement your own.

Implement your own Movement component, or your own PathFollowingComponent, and just… do it. Or find where in the engine code it sets vel to 0, and remove that. Although then you’ll complain that Velocity is in the wrong direction, I suspect.

@wab11

I never meet senior ue4 programmer which not said “Behavior Tree is very bugged”. I’m also work with behavior tree a lot, and from the simplest like reading bad values from BlackBoard variables to most advance like graph condition nodes always redirect same route - regardless of the values of the conditions provided.

I would love to see such an example.