cant work AdaptivePathfindingSystem on my unreal engine project

Development Programming & Scripting Blueprint
,
1

Hi, im using

AdaptivePathfindingSystem: AI Navigation Plugin v2.06

on Unreal Engine Versión: 5.7.4-51494982+++UE5+Release-5.7

on Windows 10 Pro

The pawn is moving right with the custom NavData: RecastNavMesh. When i use APS_NavigationData the pawn doesnt move. He rotates to objetive, the nav preview shows but he doesnt move. Im using Behaviour tree. I even try with BTTask_blueprint to foce the AiMoveTo node but it doesnt works.

2

Rotating toward the target but never moving is the usual split where focus succeeded and the path did not. The controller can still turn the pawn to face the goal when Move To never receives a path it can follow. RecastNavMesh moving the pawn, and APS_NavigationData only showing a preview, means the query and the follower are not on the same nav data.

With both a RecastNavMesh and an APS_NavigationData in the level, the nav preview can be drawing the APS mesh while the stock Behaviour Tree Move To, and the AI MoveTo node, still query the default Recast data. An empty path, or a path on nav data the pawn’s path following component will not accept, is dropped immediately. The pawn turns and then stands there. Calling AI MoveTo from a blueprint task hits that same query, so it fails the same way.

Check these in order:

  1. While the task runs, watch the AI Controller’s Path Following status. If it drops straight back to Idle and the result is Invalid or Aborted, the path was rejected.

  2. In Project Settings > Navigation System, see which nav data is the default and which supported agent matches this pawn’s nav agent radius and height. APS only drives the pawn if that agent was built into APS_NavigationData. Rebuild paths after changing it.

  3. For a test, disable the Recast nav data so only APS_NavigationData exists, then rebuild. If the pawn starts moving, the two nav datas were splitting the preview from the query. If it still only rotates, the stock path follower is refusing APS paths.

  4. Adaptive Pathfinding System 2.x expects its own move task, not the engine Behaviour Tree Move To. The stock task asks the engine navigation system and will not follow an APS-only path. Use the plugin’s move task if it ships one. A custom nav data that previews but never drives the character is almost always this mismatch.

  5. Log the path point count from the move request. Zero points with a valid-looking preview means the preview and the query are different nav datas.