Roblox pathfinding can only compute path within limited range

Help and Feedback Scripting Support
#1

Hi there, I’m working in a large maze with one monster that’s designed to navigate and constantly compute a path to the player. The issue is, is that if I am too far from the monster, path.Status returns NoPath. I’ve tested this by setting spawn points incrementally further from the monster within the same accessible path of the maze, and found that at some point of distance, it returns NoPath. I couldn’t find any other post relating to this and wanted for help.

In the image below, the part selected is the spawnpoint

image
image1367×809 64.6 KB

Note: AgentRadius is completely unrelated.
Snippet below:

connection = task.spawn(function()
			while task.wait() do

				path:ComputeAsync(bot.HumanoidRootPart.Position,hrp.Position)

				bot.Nextbot.WalkSpeed = 45
				print('CHASING')					
				for i,v : PathWaypoint in ipairs(path:GetWaypoints()) do
					bot.Nextbot:MoveTo(v.Position)
					bot.Nextbot.MoveToFinished:Wait()
				end
#2

Also, I am 100% sure the path isn’t blocked by some part as I’ve navigated from the spawnpoint to the centre myself.

#3

I took one of big mazes I can find in toolbox (Why not) And the pathfinder seems to work smoothly (In far ranges) I’m not sure what’s the issue. You could try using one of the modules I use SimplePath - Pathfinding Module
And check navigation mesh to see if it’s the nav mesh.

#4

As in, constantly following the player?

#5

Yeah, Probably try without chasing and use a goal block as a test, If it works in far ranges then must be the your targetting.

#6

Alright.

#7

Alright so I did a test. I removed the maze and it returned Success. I hate this maze.

#8

Can you try SimplePath with your script? It’s gonna cause you less work and works perfectly.

#9

Alright.

#10

Same issue. I even removed the maze and stood from my spawnpoint and it did not pick up. When moving closer to the bot however, it did pick up and startec chasing me

#11

Not sure what’s happening either, Maybe someone could help you. It probably has to do with the function’s limit/ Target limit

#12

I’ll try inserting a completely new r6 rig and use the same script

#13

Hm so this is weird. I remade a script for the pathfinding, moved the maze up and re-ran the code with my original bot too. It worked.

local pfs = game:GetService('PathfindingService')
local path : Path = pfs:CreatePath()

local bot = script.Parent
local spawnlocation = workspace.SpawnLocation

path:ComputeAsync(bot.PrimaryPart.Position,spawnlocation.Position)
print(path.Status)

for i,v : PathWaypoint in ipairs(path:GetWaypoints()) do
	bot.Humanoid:MoveTo(v.Position)
	bot.Humanoid.MoveToFinished:Wait()
end

It’s definitely something with my maze.

#14

I may have to experiment with pathfinding more, I don’t wanna make bunch of words since I’m using a phone right now but, Does pathfinding really only working around baseplate height? (Default map)