Summary
When using the standalone Get Path Length node (without referencing a NavigationPath object), the node returns abnormal/invalid path length values when the End Location is placed diagonally relative to the NavMesh grid/polygons.
What Type of Bug are you experiencing?
AI
Steps to Reproduce
1.Set up a level with a generated NavMesh.
2.Call the standalone Get Path Length node where the End Location is located orthogonally (up, down, left, right) relative to the Start Location on the NavMesh grid.
3.Call the same standalone Get Path Length node with the End Location placed diagonally (crossing adjacent polygon corners/edges) relative to the Start Location.
4.(Optional comparison) Call Get Path Length from a NavigationPath object generated via Find Path to Location Synchronously using the same Start and End locations.
Expected Result
The standalone Get Path Length node should calculate and return the correct path distance to the End Location regardless of the relative angle or diagonal placement on the NavMesh polygons, matching the behavior of the NavigationPath-derived Get Path Length node.
Observed Result
The standalone Get Path Length node returns correct values for orthogonal target locations, but returns abnormal/extreme values (or invalid distances) when the target location is situated diagonally across NavMesh polygon corners. In contrast, obtaining Get Path Length via Find Path to Location Synchronously returns the correct path length for the exact same diagonal locations.
Affects Versions
5.7
Platform(s)
Windows
Additional Notes
This was observed in UE 5.7.4 using GASP v5.7 on Windows. Please note that this issue may be condition-dependent or environment-specific and might not be reproducible under all NavMesh configurations.