Unexpected navigation data when using NavModifiers

Development Programming & Scripting AI
, ,
1

After adding a NavModifier Component to one of my classes I’ve found that the navigation data that gets built around those classes isn’t anything close to what I expect.

When I place a sphere in my level what I see is

70136-weirdnavigation.png
70136-weirdnavigation.png673×551 263 KB

which is a much larger unwalkable space than I would expect the sphere to have.

If I delete the NavModifier (leaving everything else the same) I instead get

70137-expectednavigation.png

which is closer to what I would expect to get. I wouldn’t use the NavModifiers except I need the NavMesh to get regenerated at runtime and what I’ve found through searching says that using NavModifiers means it gets rebuilt faster. Is the expected behavior for NavModifiers to be such a large AABB or is there some other thing that I’m doing wrong?

2

I have exactly the same problem in 4.15! Have you found any solutions?

3

I didn’t. I ended up removing the NavModifiers from the objects because my performance wasn’t getting hit too hard without them and we aren’t going to be spawning them too often during gameplay.