Newbie to pathfinding, need help, waypoints don't get created

Help and Feedback Scripting Support
#1

I basically took one of the starting templates and attempted to modify it to have a constantly pathfinding NPC.

Why does this constantly return no waypoints?

There are no errors in console.

local PathfindingService = game:GetService("PathfindingService")
local PATROL_DELAY = 1

local enemy = script.Parent
local humanoid = enemy.Humanoid
local humanoidRootPart = enemy.HumanoidRootPart
 
while wait(PATROL_DELAY) do
	local currentDestination = workspace.hallowCore
	
	-- Make variables for the start and end of the path
	local startingPosition = humanoidRootPart.Position
	local goalPosition = currentDestination.Position
	
	-- Find a path to the enemy's current destination
	local path = PathfindingService:FindPathAsync(startingPosition, goalPosition)
	local waypoints = path:GetWaypoints()
	
	-- Loop through all of the waypoints in the path
	for waypointIndex, waypoint in pairs(waypoints) do
		print(waypoint.Position)
		local part = Instance.new("Part")
		part.Position = waypoint.Position
		part.Size = Vector3.new(1, 1, 1)
		part.Anchored = true
		part.Parent = game.Workspace
		
		local waypointPosition = waypoint.Position
		-- Make the humanoid move to the current waypoint
		humanoid:MoveTo(waypointPosition)
		-- Wait until the humanoid has reached its target
		humanoid.MoveToFinished:Wait()
	end	
end
#2

So path:GetWaypoints() is returning an empty table?

#3

Does printing path.Status print Success, ClosestNoPath, or ClosestOutOfRange?

1 Like
#4

Yes.

#5

It prints Enum.PathStatus.NoPath.

#6

Weird issue, doesn’t make sense at all. Have you tried turning on the navigation mesh to see what pathfinding in your world would look like?

1 Like
#7

I have, yes. It appears as though the navmesh is fine.

image
image929Ă—493 130 KB

Is it possible that the brick is too far away?

#8

So despite the navmesh being valid, the pathfinder couldn’t seem to find a valid path through the viable navmesh. I solved it by placing a dud brick for it to seek instead of the actual target. :confused:

1 Like
#9

If the finish position was too far from the start position, then the path’s status would be ClosestOutOfRange.

Would you mind providing the place file where this issue is occurring so I can try to find a solution?

#10

ClosestOutOfRange is deprecated. FindPathAsync() does not limit the range of the path.

Not sure if this is your case, but path requests could fail if either start and/or end locations are too far from the navmesh.
If you have a repro place I could investigate this further.

3 Likes
#11

I can see about making a repro.

I think the issue was that I wanted the NPC to pathfind to a large ball’s position, which isn’t exactly possible cause the center is unreachable (if that makes sense).

1 Like
#12

Ah, path finding, my favorite topic! Where are the start and goal positions being set to relative to the ground and nearby objects when you don’t use a proxy part? I’ve gotten this error when the points are too high or too close to a Mesh with a weird invisible collision mesh.

#13

It could potentially be that the target part of the pathfinding was considered to be an obstacle so the path was returning invalid – although that means that the returned Enum might be different. Oh well. Pleased that you found a solution anyway :wink:

1 Like
#14

A sphere about 5 studs off the ground, reachable by a set of stairs. Presumably the sphere was too big though.

#15

Ah yes, both the height and sphere were probably issues. I probably should have read a bit more carefully, as I see you already mentioned that as a possibility. I’m a simple man: I see a pathfinding topic, and I post! Even if it is already solved… :stuck_out_tongue: