Goals cannot be registered on a layer of a navigation mesh; they will all project down onto the highest level. This prevents the office scenario from actually being done in 3D.
Related, identity goals would cause an agent to move from where they start if they are not on the highest level when the identity goal is created.
Planning on the navigation mesh doesn't properly respect clearance. If one of the polygons is a long skinny triangle, only the triangle edge lengths are considered and not whether or not an agent could actually traverse it.
Planning is done w.r.t. the polygon's centroid. For large polygons, or polygons with strange aspect ratio, this becomes a bad approximation of the actual length of the path.
Teleportation see related issues
Implementation
The creation of the navigation mesh from the file description requires casting pointers as unsigned ints. This is not a good trick and has compilation issues on different compilers.
Error handling (if positions/agents/goals/whatever be placed on the mesh). See related issue.
TODO: provide some examples that show these weaknesses.
Related issues:
4 - Teleportation doesn't work on navigation meshes.
2 - Silent crash when agents can't be placed on the navigation mesh.
The navigation mesh still has several issues:
Features
Implementation
TODO: provide some examples that show these weaknesses.
Related issues:
4 - Teleportation doesn't work on navigation meshes.
2 - Silent crash when agents can't be placed on the navigation mesh.