About getting the cost of path travelled/found!

[johnwon2007]

Hello, so i know how to set areas and its cost so that we can find the best lowest costing path. but I was wondering if it would be possible to get the actual cost of found path. I have no clue since the cost is not being returned by NavMeshQuery.findpath().

Thank you.

[rob-myers]

Hey, why do you need the internally computed cost... would it be sufficient to just sum the edge-lengths?

Technically speaking, dtNavMeshQuery stores the costs inside the "nodes".

https://github.com/recastnavigation/recastnavigation/blob/bd98d84c274ee06842bf51a4088ca82ac71f8c2d/Detour/Source/DetourNavMeshQuery.cpp#L1459

You could fork the repo recastnavigation with a method exposing this information for the final node, and then fork recast-navigation-js to expose the method. It's a bit involved, but I've been doing it for better control of offMeshConnections.

[johnwon2007]

Hey, thanks for the suggestion and taking the time to respond. I’ll definitely give that approach a shot.

I need access to the internal path cost not just for calculating the raw distance, but for factoring in things like area-specific costs, including slope angles, to reflect traversal effort more realistically. This lets me estimate things like travel time based on both agent speed and the difficulty of terrain. So it’s not just about edge length, I want the cost to reflect actual effort if that makes sense.

If anyone else has alternate ideas, I’d love to hear them. And again, thanks @rob-myers for pointing me in the right direction.