Installation. In Unity Package Manager, open My Assets, select Nav 3D Pro, download it and choose Import. Import the supplied .unitypackage into Assets/Nav3D. Editor commands are under Tools ▸ Nav3D; older screenshots and tutorials show the former Nav3D top menu. Assets ▸ Create ▸ Nav3D is unchanged.
Project content. Keep your own scenes, scripts and configuration assets outside Assets/Nav3D so a product update cannot overwrite them. Back up edited demos and resources before importing an update.
Updates and removal. Download and import updates through My Assets. Follow the release migration notes and re-bake existing obstacles after this update. Keep one installed copy of Nav 3D to avoid duplicate C# classes, assemblies and asset GUIDs. Remove the separately imported Formations adapter before its vendor dependencies; preserve your own content before removing Assets/Nav3D.
All asset classes you need to work with are contained in the Nav3D.API namespace. That namespace is served by four assemblies — Nav3D.API (the components), Nav3D.Common (Nav3DAgentConfig, Nav3DWorldSettings, PathfindingRequest, PathfindingResult and the enums), Nav3D.Pathfinding (Nav3DPath) and Nav3D.SpaceProcessing (IObstacleAdditionProgress). Scripts in the default Assembly-CSharp reach all four without any setup; if your own code lives in an assembly definition of your own, add the ones you use to its references.
In play mode, Nav 3D will create several MonoBehaviour objects on the scene that it needs for internal use. These GameObjects are created with the DontDestroyOnLoad flag. Keeping managers when loading another scene can be useful if, for example, you use a separate loading scene in which you initialize Nav 3D.
Movement of agents (Nav3DAgent) executes inside the FixedUpdate event.
All time-consuming computational operations are performed on the CPU outside the main thread.
All callbacks provided in the Nav 3D API are executed on the main thread.
The package includes eleven scenes under Assets/Nav3D/Demo. Showcases holds eight single-mechanism scenes — LocalAvoidance, MotionModes, PointVsVolumetric, ResolutionRegion, RuntimeObstacles, Evaders, SphereShell and ExternalPID — and Playable holds Foundry, Skyline and Skyrift. Each scene is authored in edit mode, so its setup is visible before Play. Demo materials convert on import under URP/HDRP; after switching pipelines, use Tools ▸ Nav3D ▸ Convert Demo Materials To Active Render Pipeline. In the references below, Demo means Assets/Nav3D/Demo. New in 3.0.0
If you work with an AI coding assistant, point it at Assets/Nav3D/AI/Skills/ once. The folder holds six skill documents — setup, obstacles and baking, agent movement, pathfinding queries, local avoidance, troubleshooting — that let the assistant use Nav 3D correctly instead of guessing from the API surface. Assistants do not discover the folder on their own. New in 3.0.0