disconnected navmesh

[ghost]

This map have several disconnected navmeshes:

Backside of alien base (fixed by #6)

Details of first problem, now fixed

Here, no class can go through (no idea what prevents the navmesh to be generated though, it might be something on the map, or something from the generator):  This is the most problematic bug, since this makes it very easy to humans to attack undefended alien base. Fixing it would also drastically increase the chances for tyrants to move of alien base.

Unconnected top of stairs

Tyrants can't go outside of alien base (this is likely due to the size of margins. Not that tyrants would not be able to leave anyway because there's a bug a bit after on that map with the handling of the stepsize by bots):

Some passage over the void

Small aliens and humans don't know how to reach the other side. (Tyrants are not affected, though, and human players do not need to jump to reach the other size, momentum is enough to avoid falling in the hole. I'd even say, it's almost impossible to use that hole, making it of dubious interest, a bit like some yocto's).

Note that all of those problems can be worked around simply by placing navcons.

[ghost]

@illwieckz , @slipher : do you think adding navcons to maps would be acceptable fixes? Would they work inside a .dpk?
If yes, I can provide fixes for the most problematic things I'm aware of.

[necessarily-equal]

I updated this issue's description to make it more clear what there is still to fix

[necessarily-equal]

I think navcons could be a good workaround for now

[illwieckz]

Perseus from Unvanquished 0.54.0 is shipped with navcons from https://github.com/sweet235/navcon

If those navcons had links for those parts then it's fixed.

[necessarily-equal]

I haven't seen one for the tyrant step at least

[ghost]

IMO using navmeshes for the place where there is a hole is an acceptable workaround to close this problem.
Area near the entrance though are affected by a bug (misconfigured feature) in the navmesh generation code. I guess it would be ok to move this issue to another tracker though, as this is not solely a mapping error.
To describe the bug in few words, the problem is that recast generates margins to avoid agents to fall or to go too close to walls. This feature generates the same kind of problems as discussed here on few other non-official maps, and does not even prevents bots to fall off the cliff in chasm.
Here, the problem is that this passage requires a tyrant to force it's way against geometry, that is, tyrants are (slightly) bigger than the passage, and I believe (I have not investigated this particular situation, this is just guessing) the margins prevent recast to connect the areas despite the fact it is possible to navigate.

[ghost]

IMO using navmeshes for the place where there is a hole is an acceptable workaround to close this problem.

Obviously, I mean offMesh connections, aka navcon in unvanquished's parler.

[ghost]

Remaining problems have been fixed by autojump, except for the void passage, which needs a navcon.

[ghost]

marauders (not advanced), mantis, dretch, and humans are still affected by the "void" problem. This can be fixed by navcons only.