Building NavMeshes in separate thread?

Does the new NavMeshSurface ("Components for Runtime NavMesh Building") supports asynchronous NavMesh building, or everyting must be created in Unity thread?
Is it possible to fire BuildNavMesh as async task and do not stall main thread?

 

Did you ever find out if there is an async operation? I know theres UpdateNavMesh() but that only works after the navmesh has already been built...

Also appears you can't use static batching gameobjects with navmeshsurface...?

 

I would also like to know if this is possible, but it seems that the navmeshbuilder api (https://docs.unity3d.com/ScriptReference/AI.NavMeshBuilder.html) - requires using UnityEngine.AI to work!

could potentially be thread-safe depending on how used

 

Navmesh build is async by default but needs to be called from the main thread.

 

Ah think I figured it out.

Just startcoroutine and pass the navmeshsurface to the coroutine.

Code (csharp):

1.  
2.         // called by startcoroutine whenever you want to build the navmesh
3.         IEnumerator BuildNavmesh(NavMeshSurface surface)
4.         {
5.             // get the data for the surface
6.             var data = InitializeBakeData(surface);
7.  
8.             // start building the navmesh
9.             var async = surface.UpdateNavMesh(data);
10.  
11.             // wait until the navmesh has finished baking
12.             yield return async;
13.  
14.             Debug.Log("finished");
15.  
16.             // you need to save the baked data back into the surface
17.             surface.navMeshData = data;
18.  
19.             // call AddData() to finalize it
20.             surface.AddData();
21.         }
22.  
23.         // creates the navmesh data
24.         static NavMeshData InitializeBakeData(NavMeshSurface surface)
25.         {
26.             var emptySources = new List<NavMeshBuildSource>();
27.             var emptyBounds = new Bounds();
28.  
29.             return UnityEngine.AI.NavMeshBuilder.BuildNavMeshData(surface.GetBuildSettings(), emptySources, emptyBounds, surface.transform.position, surface.transform.rotation);
30.         }
31.  

 

No, coroutines are not seperate threads. They are run on the main thread.

 

Running a wrapper in parallel makes no sense unless BuildNaVmeshData runs in parallel
BTW :- Coroutines and Async run on main thread

 

you better add

surface.RemoveData();

if you need multiple rebuild navmesh

 

Any solution yet ? I have multiple navMeshSurfaces each for a chunk of infinite terrain, the terrain data generation works on another thread but I need to know if I can do the same with navMeshData.