Pathfinding:ComputeAsync() returning NoPath when the destination is far away

Help and Feedback Scripting Support
, , ,
1

Hello everyone,

My game consists of a maze and a big NPC that chases the player.

When there is no player to chase, the NPC finds a path through the maze to return to its original position (a part in the workspace).

When the part is close to the NPC it finds a path just fine, however when its even just a little further away the function returns PathStatus.NoPath.

For Example, when trying to find a path from 1 to 2:

image
image1081×523 46.7 KB

No path is found. But finding a path from 3 to 4:

image
image1081×523 49 KB

Is possible.

The NavMesh looks fine:

image
image996×656 37.1 KB

Anyone had this problem before or know what could be causing this? Thank you in advance.

1 Like
2

this is reallly urgent! (bump)

3

image
image1174×670 133 KB

Okay i dont know if its very clear in the image but the navmesh breaks here.
when i place the npc after the split it works fine. how do i join the mesh back together??
Also, its only on this specific part, and its full of cracks. its like every 5 studs or so

4

:ComputeAsync doesn’t return anything instead you need to use path itself on who you called method computeasync

5

Thats what im doing, sorry if i wasnt clear. My code is not the problem, i believe this is an engine bug.

1 Like
6

Maybe it has some invisible walls where you need to add PathfindingModifier | Documentation - Roblox Creator Hub?

7

No, theres nothing in the way.

8

What have you got set for the Agent Parameters? And when you say the NPC is big how many studs tall/wide is it?

9

I tested again with a regular R6 rig with default parameters and this still occurs.

10

After some sleep it seems like the whole navmesh erased itself.

image
image1330×584 42.5 KB

This only happens at runtime

11

Is this with PathfindingUseImprovedSearch set to Enabled or Disabled in the Workspace?

12

Set to Default.

CHARRRRAACTER Limmimitt

Should i close this and move to the bug report?

1 Like
13

Try changing it to see if you get different behavior. Default I believe is still the same as Disabled, AKA old algorithm.

14

No changes in behavior.

carrracter loimit

15

How far apart are the positions? It could be failing a raw distance check.

16

376.1518249511719 studs apart

dawdadwdawdaw

17

image
image1256×575 95.9 KB

The NavMesh is completely ruined.

18

The Navigation Mesh doesn’t need to be everywhere, that would be very very costly for performance. It seems like it’s trying to generate in a line from the start to the end with a certain radius, and then failing because the hallway diversions are too long.

19

Should I split the hallways into different parts?

20

For people in the future reading this:

Roblox’s NavMesh generation is limited to a 32-stud radius around the pathfinding agent’s position by default. This means if you try to pathfind to or from a location far away from the agent, the NavMesh won’t generate in those distant areas. it’s done for performance reasons.

Placing a bunch of dummy parts around your map each 32 studs from eachother and calculating the NavMesh at their position is a temporary solution:

local dummy = script.Parent

local preloadPath = game.PathfindingService:CreatePath()
preloadPath:ComputeAsync(dummy.Position, dummy.Position)

-- Wait a short time for navmesh to generate
task.wait(1)

dummy:Destroy()