FYI had no report from RequestDirectMove as well (solved with eye height/nav mesh height)

[Brownie]

Just to finish this off - I stumbled onto this thread, which answers the question regarding the movetoactor and requestdirectmove relationship pretty fully:

Need more clear explanation of how MoveToActor and RequestDirectMove work together

You can easily view the definition of MoveToActor() by right clicking in Visual Studio and clicking Go To Definition. If you dig through you will find your answers. Since you want to be so verbose, in line 932 of PathFollowingComponent.cpp, you will find your call to RequestDirectMove(), which it calls on the referenced movement component. On line 1185 of PathFollowingComponent.cpp you will find where it gets the reference to our TankMovementComponent via FindComponentByClass<UNavMovementCompon…