Skip to main content

Troubleshooting

Common issues and their fixes. Most map back to one of the rules in Tuning.

"Path Not Found" every time​

Cause: the drone's collision blocks the navigation trace channel, so every query self-hits. Fix: make the drone transparent to the channel — see Required: Drone Collision Setup. This is the most common issue by far.

"Path Not Found" only sometimes / near edges​

Cause: the start or goal is outside any nav volume, or further than MaxSearchDistance from the nearest node, so it can't snap onto the graph. Fix: extend a BP_DroneNavVolume to cover that airspace and re-bake. Use DrawNearestNodeSearch? to see where the snap is searching.

The drone clips wall corners​

Cause: clearance is set to roughly the agent radius with no margin; path smoothing pulls the route tight to that boundary at corners. Fix: raise TraceRadius and NodeClearanceRadius to agent radius + ~25–30 (e.g. ~105 for a ~75 drone), keep them equal, and re-bake. See Tuning → Clearance.

Lots of red (isolated) nodes / the path routes oddly​

Cause: a fragmented graph — usually MaxConnectionDistance below the √3 floor, or clearance set so high that corridors get pruned. Fix: ensure MaxConnectionDistance ≥ GridSpacing × 1.732 (ideally 1.7–2.0 ×). Heed the bake-time ratio and isolated-node warnings. Confirm with Show Nav Graph.

The path goes through a wall​

Cause: the baked graph doesn't know about that wall — it was added/moved after the last bake, or it isn't solid to the trace channel in the editor (e.g. a dynamically-revealed object). Fix: make sure the wall has collision on the nav channel in-editor, then re-bake. Verify with Show Nav Graph that no links cross it.

The drone wedges against a wall​

Cause: AcceptanceRadius is smaller than the drone's body, so the planner threads it through a gap narrower than it is. Fix: set AcceptanceRadius to roughly the drone's bounds (~100).

Patrol won't start / drone ignores the path​

Cause: marker spline positions weren't computed, or the PatrolPath reference isn't set. Fix: confirm the BP_AIDrone's PatrolPath is assigned, SnapMarkersInEditor? is on, and the Markers array has no empty entries. Nudge any property on the path to re-run its Construction Script. See Patrol.

Changes to a preset don't take effect​

Cause: presets are stamped at bake time, not read live. Fix: after editing a DroneNavConfig, re-apply it (manager Apply Nav Config, or Auto Apply Config on the bake widget) and re-bake.

Still stuck? Join the Discord for support.