Link not detected if its in a specific position

[Javier]

I have two areas of my level connected by NodeLink2. My agents use Seeker to follow the player. In some areas of the game, the agents can’t find a path towards the player when it jumps over, ignoring the links I set. If I move a little the link, in fact, 0.001 units in the X axis, the agents find the path and jump over the gap. It seems to work perfectly unless the position is exactly (42, 3, 77) as seen in this example:

I’m confused because I think the links should be detected in the position they currently have. Is there something I’m doing wrong, or do I need to share more info?

[tealtxgr]

Floating point precision calculation issues possibly? This gets absolutely into the territory of “deep programmer stuff” that I’m not very good with though. I know it comes up here and there though

From some other threads:

@aron_granberg

I would recommend having a slightly higher max slope than 0. That might make some surface unwalkable just because they have a tiiiiny slope (or just floating point errors).

@Jesse_Moreland

Aw I figured it out. The issue is my ToVector3Int() function just floors all coordinates, including the z coordinate. Adjusting that to always return 0 instead of the potential -1 due to floating point numbers… it works now.

[Javier]

I’ve found the problem. The short answer is my links had “Everything” in the Graph Mask. Specifying the graph I wanted fixes the issue, in this case, Graph 0.

I have another GridGraph, (Graph 1). The long answer is that I’ve discovered the center position of this graph affects whether my Graph 0-exclusive Seekers detect the links. I don’t understand why, but at least I found a solution that works for me, since I don’t need the links in Graph 1.

Thanks for the reply!

[tealtxgr]

Ahhhh, I see Thanks for the update!