NavMesh Modifiers are completely ignored

NavMesh Modifer and NavMesh Modifier Volume components are doing exactly nothing.
I have read entire docs on them, and they should work, but they don`t.

This is NavMesh Modifier Volume:

- modifier area set to Non-Walkable
- clicking Bake generates nav-mesh, but ignores both Modifier
- NavMesh Modifer with mesh does not work as well




Any ideas what is happening?

Yes here it seems everything is working just fine:

 

Stupid suggestion, but are the objects with the modifier volumes set to navigation static?

 

Do you mean GameObject’s “static” property? Or some other component/setting in Navigation?

 

Okay got it, it has to be marked as Navigation Static.
How would you go about changing areas in runtime? Is it necessarily to bake the entire mesh again? Since small nav mesh obstacles can carve holes in runtime without huge performance costs... it should be same with carving new areas, right?

 

I'm honestly not quite sure, but the obstacles are possibly using different means to carve themselves out.
You might indeed have to rebake, but if I remember correctly the NavMeshBuilder does keep track of the changed parts and only rebuilds those, so it is more performant than one might initially fear.
If it turns out the areas change in realtime without any further work, then they might just automatically trigger a rebuild when changed this way and you shouldn't worry about things.

 

encountered this same problem. here's how I was able to resolve it in Unity 2019.3

1. Create a NavMesh Surface (GameObject > AI > NavMesh Surface)
2. In the Hierarchy, transfer existing GameObjects with a NavMeshModifierVolume component to the NavMesh Surface created in step 1 (i.e. make them child objects of the NavMesh Surface from step 1)
3. Bake the navmesh again. (note: I did this from the Inspector window, not the Navigation window. In the Hierarchy, select the NavMesh Surface created from Step 1 and there should be a Bake button in the Inspector window)
4. Delete the old navmesh surface by going to the folder of your current scene and deleting the old NavMesh file (the new navmesh has a suffix '-NavMesh Surface', the old one doesn't)

 

I'm really sorry to necro this thread but I've been running into the same problem lately: when creating a NavMesh dynamically at runtime, the NavMeshSurface goes ahead and creates the NavMesh for all corresponding GameObjects (itself and its children) like it is supposed to. However, I've added a NavMeshModifier component to one GameObject, that's a child of the NavMeshSurface GameObject, and set it to "Override Area --> Not Walkable". The resulting NavMesh does include this GameObject whereas I would expect it to be "cut out".

I tried following the steps described in the post above but that didn't fix anything either. I'd be more than grateful if anybody has an idea what I'm doing wrong.


Thank you in advance!


//Edit: My project runs on Unity version 2019.3.5f1 in case that's important.

 

If you are still on this, using a NavMeshObstacle might be a better use for that. Or NavMeshModifierVolume.

Check to make sure you don't have any other modifiers that could be screwing it up. From the docs:

The NavMesh Modifier affects GameObjects hierarchically, meaning the GameObject that the component is attached to as well as all its children are affected. Additionally, if another NavMesh Modifier is found further down the transform hierarchy, the new NavMesh Modifier overrides the one further up the hierarchy.​

 

I am also having this problem with NavMeshModifierVolume. I have a small cube which is Navigation Static and Not Walkable. I have added a NavMeshModifierVolume and made it much bigger than the cube and set it to Not Walkable. I then Baked and got the following:



You should see that the mostly buried cube is not walkable, but that the volume (which also intersects the Ground Plane) remains Walkable.

Unity 2020.3. Any ideas?

 

So I have played around with this some more and discovered that if I Bake my `NavMeshSurface` using it's own Bake button rather than the general Navigation Window one it works - I get a hole carved in the NavMesh.

It seems that their are two systems - wither I use the NavMesh Window and set the require objects to `Navigation Static`, or I use the individual NavMeshSurface components which rely on their `Collect Objects` property rather than `Navigation Static`. This second method seems to include the `NavMeshModifierVolume` whereas the first does not.

 

Another thing to check is the layer that the NavMeshModifierVolume is in. If it isn't in the Default layer you may need to go to your NavMeshSurface and adjust the included layers.

That's what it was for me, I'd moved a prefab to a custom layer while testing out a new feature and then completely forgot to move it back.

 

Thank you very much, nscarrci! This exactly was the problem I ran into -- changed the layer of some objects and navmesh modifier was ignored.