My map voxelstorm11 has incomplete navmeshes for small classes

[sweet235]

For example, do

/navedit enable level0
/setviewpos 1730 8874 3853

Strangely, reducing the cellSizeFactor in voxelstorm11.navcfg can give complete navmeshes. But the tiles are so small that the search is far too slow at bot runtime.

The map is here: https://users.unvanquished.net/~sweet/pkg/map-voxelstorm11_1.dpk

Notice that the map is big, but not very huge.

[sweet235]

Here is a screenshot of the level4 navmesh at this place:

And here is the level0 navmesh:

Notice how the level0 navmesh ends at the upper right corner in this image.

[DolceTriade]

Is this an artifact of the stair size? is this something that happens in all maps with stairs?

[sweet235]

Is this an artifact of the stair size? is this something that happens in all maps with stairs?

I have no idea about the exact cause. But I am convinced it is not the stair size.

Something similar happens at some maps with considerable vertical extent, like map-cube.

In situations like this, we can simply use the level4 navmesh for all classes. This is not optimal, but not too bad either: one simply copies the file voxelstorm11-level4.navMesh to voxelstorm11-level0.navMesh. But at some point in the future, the server will overwrite these files.

Notice how we moved the responsibility for this from the mapper to the server.

[sweet235]

In nav.cpp, there is

d_->tcparams.maxTiles = d_->tw * d_->th * EXPECTED_LAYERS_PER_TILE;

Multiplying this by 4 seems to solve these problems. What is the proper value?