DoN's 3D Pathfinding for Flying A.I. [Support Thread]

[Dirtsleeper]

@VSZ;751119

I would still recommend the same debug strategy: You need to see what is happening inside your pawn’s Add Movement Input code and why it is not responding to movement requests for this case.

Going by your description that a) the path is generated successfully and b) The Fly To node is busy/active in the behavior tree. If both of these conditions are indeed satisfied, the plugin’s work pretty much ends there and it is up to the pawn to do the rest. That’s why you need to check what your pawn’s Add Movement Input is doing.

Now if the path was not generated, then there are other factors to consider like insufficient clearance area above the floor for either your pawn or for its goal (which can be solved by nudging the height of the goal/etc). However that’s likely to happen only for large bots and if something like that did happen, the logs would have definitely told you why pathfinding did not occur. In your case the logs are clean, so the issue is likely elsewhere.

Ok I added the interface and implemented the "Add Movement Input Custom but I’m still getting the same results. If there is no obstacle between the flying unit and it’s goal, it flies towards the goal and the expected output comes from the event. However, if I move the obstacle between the flying unit and goal, there is no output from the event.