Feature request: Improve logging for Path Failed messages

Most A* users will be quite familiar with this warning:

Path Failed : Computation Time 1.00 ms Searched Nodes 1055
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 as a workaround (though this comes with a performance cost).

Sometimes it can be hard to track down which agent is causing the issue and specifically where the issue was as it can point to either behaviour logic issues and/or navmesh issues.

Having some more details like target position, origin, the FollowerEntity that is related etc would be super helpful.

Hi

Have you tried setting a* inspector - settings - debug - path log mode to Heavy?

It doesn’t give you all you ask for, but at least some things.