What does TOOLMODE_PATHFIND_FOLLOW do with m_smoothPath?

[cadop]

I am having a hard time following the path generation logic. On certain inputs when I run the command (on dungeon.obj), there will be 0's on the y axis for some of the path vertices. However, these are not plotted/rendered in the example view.

I can keep stepping through to trace things, but figured others may have a similar question so it would be helpful to have an answer here.

Here is what I am seeing

There is an edge getting created under the navmesh, but it isn't connected to the path.

test coordinates:

	m_spos[0] = -13.27699852;
	m_spos[1] = 10.05246925;
	m_spos[2] = -23.09427643;

	m_epos[0] = -11.88256264;
	m_epos[1] = 0.37974429;
	m_epos[2] = -1.56740785;
	```

[cadop]

I spent some more time stepping through and found that there is some issue with edges being detected in getPolyHeight. I think during the check to see if it is in the polygon or not, "edge cases" cause it to return false incorrectly. There is a check at the end for a point on edges, but it doesn't reach that.

So instead I modified

recastnavigation/Detour/Source/DetourNavMesh.cpp

Line 692 in c2a0d94

if (!dtPointInPolygon(pos, verts, nv))

and it works without the weird edge problem.

	if (!dtPointInPolygon(pos, verts, nv))
	{
		// The point is not in the poly, but it might be on the edge
		float closest[3];
		closestPointOnDetailEdges<true>(tile, poly, pos, closest);
		if (closest)
		{
			*height = closest[1];
			return true;
		}
		return false;
	}

I'm not sure if this is a bug or I am misunderstanding the purpose. if its and issue ill let someone this discussion to and issue and I can make a PR