So navigation points / navmeshes typically take collision and solid walls into account. What is causing problems with our is when the compile has to "stitch" together the navmesh between a socket / component and the main terrain. It in the least technical terms freaks out at times. So this is why I mentioned its a topic being discussed.



I don't know.

I hate phones limits how much I type lol

My issue with nav mesh is it does not react to changes events which is why u have stitches problem and rdv freak out. My thought was to simply allow the rdv to plot their own paths as they are spawned in rather than rely Oon predefined paths that could end up crashing into each other.

Will make a bigger post when I get home lol

Technically it does plot its own path. It uses the navmesh to know "where its safe to plot a path". The problem is the navmesh doesn't always create the best options for the RDV because of the stitching. The navmesh looks like a giant web of interconnected points. It's not just lines that we draw. Its job is to tell the RDV where it "can go" and "can not go". The RDV picks its options from all those possible path lines.

Given your experience in level design, would you say that it's operating less than, equal to or greater than your expectations? Honestly, considering the complexity of it, from a design standpoint it sounds amazing that it works as well as it does.

Less than of course. It really should not be bumping into buildings, or dropping vehicles on top of buildings when it should go on the ground. I believe if we stick with the current method the level designers need to be given more control of certain circumstances. I have suggested in the past that we can use volumes that tell the navmesh not to be built in certain places so the RDV just completely ignores the area (like an entire building, or a pit, things like that).

To answer another question I saw, one suggestion that was brought up ( I don't believe any decisions have been made, this was just a suggestion from a Game Designer) is that they just spawn right above you or nearby and drop it straight down rather than flying some distance. However the argument for that was it takes away from the immersion.

Either way, we are clearly aware of some of these issues and are discussing how to best resolve them.

Another question for feedback. Right now we call them in but don't really know where they will land to be honest. We have zero control over it. Would it be possible to throw a flare and have the RDV drop off at that exact location? Or at least close nearby to it?

So could space out the drop-off spots to be more careful, at least as a temp ban-aid fix.

I suppose that doesn't fit into the current system of picking it from a menu... you could have the flare appear in your hand once you choose what you want called in?

Most likely, the biggest change would be addition of some doors at the top so it doesn't look silly. This wouldn't be published until we push a content update again either.

I dont see a problem with it currently.Its a good spot for uplinks as well.

Yeah, I was surprised the turret on that small socket wasn't fixed last patch, but I figured it was cuz y'all were busy getting us a Caldari socket set ready.

I want to get a list of the known issues consolidated here. Please feel free to have me add to the list if it is relevant. This includes all the supporting sockets and the large outpost. We want actual bugs.

Research Facility (Large Socket)
-Top of both sets of stairs under the main research building is just a dead end. (Funny thing this. Artists forgot to put fake doors up there, we also intended to block those stairs off with infamous crates)
-Road posts / bumpers are popping in too late.
-Gate structure you can walk through the railing in a corner. (Fixed internally)