From what I can tell, doing some various tests, placing a new NavModifierVolume in the persistent level and then moving it to a sub folder of that level, makes it stop working. It will seem to work while in the editor view port, but when you play test, it doesn’t actually work.
Having done some various tests now I found that, creating new volumes works just fine. But it seems as soon as you move them either to a new streaming level, or just a sub folder within the persistent level, they stop working. I think the problems I had with BlockingVolumes are related to this. Possibly the same bug affects them both.
Unfortunately i’m not seeing this on my end. I used a NavModifier (null) volume and it seems to still be nullifying the navmesh when I move it into a sublevel or subfolder of the world outliner. Do you have any steps I can take to reproduce this on my end?
Ok, I’m sorry I screwd up. I tested with my 2 projects, my main project and my test project and both originally had broken volumes in them. So if I created a new volume and moved it to where the broken one is, folder or level, it seems it also gets broken. But cleaning out the scene of any broken volumes before adding new ones and moving anything, it seems to work. Even collision volumes work now.
I’ve been redoing all my volumes in my main project, got rid of all the broken ones, and that seems to make the difference now. I went in with the new ones in there, having cleaned out all the old ones, and moved things around now multiple times to folders and levels, back and forth, and it works.
This morning is so long ago now, I was almost sure I tested by cleaning out the scene on my test scene but I guess I did not.
Really sorry, I don’t know, I screwd up on that one.
I’m gonna keep an eye on the volumes, just be double sure, but I guess, that bug is already fixed, and was probably the same thing going wrong on any volume with regards to the problems I had with BlockingVolumes and then also NavModifiers. So it seems the only catch is, if the volumes got broken at some point, you should get rid of all of them, or things can keep going wrong.
I’m happy to hear this isn’t occurring for you any longer. I’m going to mark this thread as answered for tracking purposes. If this error appears again please comment here with new steps and I’ll be more than happy to take another look.