[SOLVED]
Loading precomputed navmesh is a lot quicker .
…
It takes more than 30 secs on a 6 core amd processor to compute navmesh on a :
-2000x2000 size plane
-242 faces …
Is there a way to precompute navmesh and save it in any format ?
When the scene or node containing the NavigationMesh is saved / loaded (Save / SaveXML / Load / LoadXML / Instantiate / InstantiateXML) the navigation data is carried along as a binary blob without recomputation.
You can also try calling NavigationMesh’s SetNavigationDataAttr() and GetNavigationDataAttr() functions manually to set or retrieve the binary blob.
However just for level design sanity I believe you should tweak your navmesh parameters or break it up to several smaller navmeshes to fix the computation time.
[quote=“cadaver”]
However just for level design sanity I believe you should tweak your navmesh parameters or break it up to several smaller navmeshes to fix the computation time.[/quote]
Setting up navmesh on a node instead of scene doesn’t work apparently(sample 39_CrowdNavigation substituting scene with planeNode) .
Will it work by setting up the scene with more nodes and passing the whole scene to navmesh as for breaking it up to smaller navmeshes ?
That could be a bug, will verify.
If there’s a single navmesh component, the amount of nodes that comprise the level geometry don’t matter, because all navigable geometry in the hierarchy below the navmesh will be collected into it as triangles, then calculated as one.
Navmesh on scene works fine .
I can’t grasp how it scales with mesh size (voxels and stuff parameters), is there an idiot’s guide reference somewhere ?
Verified that you don’t have to put navmesh to the scene root. But you must ensure that all navigable geometry, that you want under a certain navmesh, resides in child nodes of the navmesh node, and is marked with the Navigable component, as usual.
[SOLVED] DynamicNavigationMesh has to be set on Scene, while Node is set to Navigable ( planeNode->CreateComponent() ) .