maxTiles value in the navmesh initialization parameters

[UltraEngine]

I used this code from the demo to set up my navmesh creation parameters:

int tileBits = NavMesh::rcMin((int)NavMesh::ilog2(NavMesh::nextPow2(tw * th)), 14);
if (tileBits > 14) tileBits = 14;
int polyBits = 22 - tileBits;
params.maxTiles = 1 << tileBits;
params.maxPolys = 1 << polyBits;

recastnavigation/RecastDemo/Source/Sample_TileMesh.cpp

Line 254 in ddaa361

int tileBits = rcMin((int)ilog2(nextPow2(tw*th)), 14);

This is resulting in maxTiles equaling 64. Whenever we go over that value, a DT_OUT_OF_MEMORY error is returned by dtnavmesh::addTile. If I don't use the code above, then dtnavmesh->init produces an DT_INVALID_PARAM error.

Does recast allow navmeshes with more than 64 tiles?

[UltraEngine]

Rubber-ducking wins again. I think in that code, tw and th should be the number of tiles in the X and Z directions of the mesh.