Illegal pathfinding movement

Help and Feedback Scripting Support
, , , ,
#1

Hi, I am having a problem with my AI. It uses PathfindingService and it moves THROUGH walls. I have the character set to CanCollide false. I made barriers that have
a PathfindingModifier inside of it (marked by the black spots in the image).

Here is an image showing the problem I am having, I have Navigation Mesh turned on to see what is happening and as you can see, the Path that it is trying to take, is going THROUGH the barrier.
image

The yellow dots are waypoints represented by the navigation mesh, and as shown in the image; two of the waypoints have a barrier inbetween them. Which should not be possible. The AI should pathfind around the barrier instead. It works with some barriers but this combination of Start → End positions, lead to this movement.

These are the Agent Paramaters I use for my AI:

AgentRadius = 2.7;
AgentHeight = 8;
AgentCanJump = false;
AgentCanClimb = false;
Costs = {
	Wall = math.huge;
};

I have tried so many things but I cant get it to work.

If you have any idea on why this might happen, please say so because I have been sat here for 3 hours trying to fix it.

#2

Make sure you make the Character follow the Waypoints and not directly to the position

#3

The yellow dots are the waypoints that the pathfinding made. And the character is following them. And as shown in the image the two points have a barrier in between them, and that should not be possible. It should pathfind around the barrier.

#4

Questions:

  1. Is the "illegal " Pathfinding area a Barrier as in a Part?

  2. Is The Said Part Completely Invisible?

  3. If not a Part, is it a Void?

  4. Can you show a video?

#5
  1. Yes, Its a transparent part with a PathfindingModifier named “Wall” in it.
  2. Yes

FYI; the barrier does have a collision group so that it only collides with the character, but since the character is CanCollide false. I don’t think that matters really.

#6

image
image785×421 33.3 KB

There are also some other bugs I am noticing with the pathfinding. As seen in this image, he takes a route that goes in to the table. Which is not neccessary and it’s not intended behaviour. In a normal situation the route would be to go around the table instead of going in to it, and then backing out again just to go in the same direction.

I have no idea if this is my fault, it only happens occasionally.