Warnings like this are spammed into the console: Path Failed: Computation Time 0.00 ms Searched Nodes 0.
This occurs because the MaybeRecalculatePath function is called for FollowerEntities that have neither a destination nor a current path. As a result, an attempt is made to find a path from the current point to the current one (the destination is equal to the current position).
If you’re trying to get the warning to go away, you can change the logging level in the AstarPath settings section. Are you suggesting something, like, not showing them for MaybeRecalculatePath if it doesn’t try to do one? If so I can tag this as a suggestion.
Yes, I suggest not trying to find a path when it’s not necessary: from a point to the same point. Not finding a path when this search was not requested. Not loading the processor with useless work.
This can actually be important. For example, if a graph update has just made the ground under the agent unwalkable, the path calculation will inform it of that. In other cases, a path calculation from a point to itself is very cheap and not really a performance problem.
I’m not sure why it sould say path failed in this case, though… I’ll have to look into that.