NavMesh2D is a tool to generate and navigate navmeshes for 2D projects. It is designed to work very similarly to the built in Navigation tool which unfortunately doesn’t work in 2D.
It is quick and easy to set up your navmesh with NavMesh2D. You can generate your navmesh in 3 steps - specify which layer contains your floors, specify which one contains your walls and hit bake.
Features
Seamless Integration
The tool does not use any special colliders or ‘helper scripts’ that need to be attached to objects around your scene. It works with Unity’s built in colliders (Box/Circle/Polygon). Your gameobjects will get processed if they are a 2D collider on either the floor or wall layer. Thats all there is to it!
Tolerant
NavMesh2D is extremely tolerant of overlapping colliders and ‘messy’ scenes. You don’t have to be ‘pixel perfect’ with all your placements. NavMesh2D will collect all of your colliders and crunch away on that data to spit out a clean navmesh.
Full Control
You have full control over how much padding should be applied to the navmesh and you can also pick from 3 different corner/edge types. You can also bake a grid with a specified resolution into your navmesh to improve path finding results.
No, NavMesh 2D will be top down only. In the near future, we do have plans to release a tool (called Node Networks) that allows you to easily create node networks manually/by hand in the editor. It will use the exact code that we have layered NavMesh 2D on top of. Node Networks won’t generate a navmesh for you, but you can place down nodes on the platforms and connect them up together yourself to form your ‘navmesh’. It is still in the works, however, and we plan to release that separately (and for free!).
Currently, no. You need to bake the navmesh into the scene, same as with Unitys 3D navmeshes. We do have plans to go down that route as it would be nice feature to have for endless runner or rouge like games. We need to overcome a few technical hurdles first before we make the functionality available at runtime. For example, we need a way of stitching navmeshes together. Until then you will have to prebake all your navmeshes into the scene
I do have a question though, I wonder if there is a way to find a path, even if I try to reach outside the generated navmesh. Of course it will never each, but I wonder if I can somehow try to “go as close as you can” to the point in the end position?
I actually managed to modify the code to find the solution I needed n_n.
Here it is in case you might want to add it to the system :).
This doesn’t work when trying to reach in a place that has a blocker inside though, only when outside the collision mesh… I guess some more experimenting and might make it work with internal colliders :p.
/// <summary>
/// A smoothed path from start to end. will attempt to get as close as posibile
/// </summary>
/// <param name="startPosition">The Start position</param>
/// <param name="endPosition">The End position</param>
/// <returns>A list of points, order from start to end</returns>
public static List<Vector2> GetClosestSmoothedPath(Vector2 startPosition, Vector2 endPosition)
{
if (instance == null)
{
Debug.LogError("NavMesh2D: Scene does not contain a 2D NavMesh");
return new List<Vector2>();
}
List<Vector2> resultingPath = new List<Vector2>(0);
NavMesh2DNode startMesh2DNode = GetNavMeshObject().ActualClosestNodeTo(startPosition);
NavMesh2DNode endMesh2DNode = GetNavMeshObject().ActualClosestNodeTo(endPosition);
if (startMesh2DNode != null && endMesh2DNode != null)
{
resultingPath = instance.SmoothedVectorPath2D(instance.GenerationInformation.ColliderPadding, startPosition, endMesh2DNode.position, instance.GetPath(startMesh2DNode, endMesh2DNode));
}
return resultingPath;
}
EDIT: Managed to make moving as close as possible when inside collisions work as well. You an do ti by removing the layer collision checks in NodeIndexQuadTree.cs. Of course the best approach is to duplicate the methods and create your own ClosestSmoothedPath version or something, so you don’t destroy anything coded inside
