Navmesh of SubLevel?

[Jesse_Valar]

@BakerSophia

I’d invite any more experienced user to correct me if I’m wrong about this, because I’m brand new to unreal engine, but I spent an entire day getting navigation working in my own vr world, and I’d like to share my insights with any other newbie users who may be having difficulty with this.

1. Both the persistent level and the sub level needs a nav mesh
2. The nav mesh in the persistent level needs to fully encompass the space that all the sub levels are placed in. The sub level nav mesh only needs to encompass the space of the sub level.
3. All levels need to be set to visible, then navigation needs to be rebuilt before play testing. Depending on the size of your game, this could take a long time, so I’d recommend only building the persistent level and whatever sub levels you’re play testing, then rebuilding the entire thing when you’re ready to actually publish.

I hope this helps. After struggling for nearly an entire day, this method got navigation working in my entire vr world.

I can confirm that it’s working, one small detail is that persistent level needs to be set to invisible when building navmesh for all levels. Otherwise navmesh won’t build - it will show progress and will take a long time, but navmesh itself won’t be there.

One limitation of this method is that it might not be possible for big worlds. Works fine for my 16 test tiles, but thousands of tiles? It’ll probably fail to load in editor. If building navmesh for each level separately there’s a disconnect between tiles. I’m not sure yet how bad it is, probably I’ll need some way to move AI actors between tiles that doesn’t depend on navmesh.

Or maybe just improvise and build as navmesh pieces as big as possible and also create natural looking obstacles where navmesh disconnects?

I’m surprised there’s no documentation about static streamable navmesh for world composition. Seems like nearly every game project with big world needs it.