I’m just trying to wrap my head around this, and i’m not sure this is a bug, or ‘by design’.
But when we calculate a navmesh and get the NavMeshPathStatus, it will often return PathComplete, but have a length of 0 corners, which in my opinion should return NavMeshPathStatus.PathInvalid.
Now the workaround is easy, but it does require checking for both the status and the corner length, which can’t be good performance wise (though debatable is of course whether or not his would even measure in the whole navigation logic of our script given that a navmesh path calculation is already rather heavy performance wise.)