I have a large agent (2-story building sized) that for some reason will not find a valid path to a node unless it’s within range of it’s current area. I don’t expect this agent to change from that area, and yet, when I increase the Max Nearest Node Distance to 1000 or even 10000, it doesn’t affect it’s ability to find that node- despite the node being within range of that area’s nearest node.
If I shift the node about 10 or 20 units toward the area it’s currently on, it will find the path. However, I would expect it to find the nearest node. Am I missing something in how it’s finds a point?
The terrain and destinations are constructed at runtime, so pre-placing them won’t suffice.
Path Failed : Computation Time 28.922 ms Searched Nodes 20577
Error: Searched all reachable nodes, but could not find target. This can happen if you have nodes with a different tag blocking the way to the goal. You can enable path.calculatePartial to handle that case workaround (though this comes with a performance cost).
Path Number 167 (unique id)
UnityEngine.Debug:LogWarning (object)
I’m not currently using any tags on the graph they’re using, nor on their seeker.
The agent’s graph isn’t updated other than it’s initial scan when it’s created.
There are some nodelink2 updates that occur as a result of a moving graph. However, they connect to a different graph than the one that this agent is moving on.
The Path Failed warnings seem to occur before those updates are (re)applied (they only get updated if the local graph has moved beyond a threshold, which in this case they hadn’t).
These are the graphs and settings.
The ‘LG’ graph is the one this unit is on, and doesn’t update/change.
The ‘SM’ does have nodelink2’s that connect to it to the ‘LOCAL’ graph (via the point graph).
