Move Navmesh agent onto Navmeshsurface from outside the surface

Is there any way I can accomplish this seemingly easy task that actually seems to be quite difficult?

I have a bunch of units on a boat, I move the boat until it hits land (Navmeshsurface), then they disembark. However, since the boat is not a Navmeshsurface, I cannot tell the agent to move.

Is there some way this can be solved that Im not thinking of? I cannot findany material on it and have not had any accuess myself.

 

As agents can only be moved on a NavMesh, you could do the following.
Add a

NavMeshModifier

or

NavMeshModifierVolume

to your boat and set to "unwalkable". As soon as your boat reaches the shore, set the

NavMeshModifier

to "walkable" and update your NavMesh.

 

You mean that will merge to boat navmesh into the "main" navmesh? I guess if they are on the same layer that might work. Since if the game thinks they are 2 different navmeshsurfaces, I would need a navmeshlink I think.

I dont even have to set it to unwalkable, I can just wait to activate the units agents until the boat reaches the shore

I was thinking to that some kind of magic with navmesh link might work too, but havent had time to try it yet, and not sure if I can modify it at runtime. Your way seems easier.

 

Yes, in a best case scenario it would only be one NavMesh.
If the boat and the terrain are on different height you might need a NavMeshLink. It's very much depending on your NavMeshSurface bake settings.

 

For anyone coming here for an answer.

I ended up adding a navmeshlink as children of my boat, then I activate them when the boat hits ground, this worked surprisingly well.

I use 2 navmeshsurfaces, one for my ground, and one for my boats, mainly so I do not have to generate the entire navmesh every time a boat lands, then I just use surface.BuildNavmesh() when the boats hit land, and send my units to theri destination

 

I would recommend to rebuild your navmeshes in game asynchronously with

NavMeshBuilder.UpdateNavMeshDataAsync

. This enables you also to rebake big NavMeshes without any remarkable hiccups.

 

Thanks, although in me scenario the navmesh has to be baked before the next command is called, so guess that could cause some issues.