TileCache offmesh conenctions. about recast4j

[ppiastucki]

TileCacheMeshProcess is just an interface, you can pass whatever implementation you like. It may set flags and areas to whatever you want. There is no need to pass flags and areas as separate arguments as they are already available as fields in NavMeshDataCreateParams class, even in C++:
See: https://github.com/recastnavigation/recastnavigation/blob/05b2b8da80037887d3e79af8a59a8f0f8ed02602/DetourTileCache/Source/DetourTileCache.cpp#L735

NavMesh::addTile is a totally different method than TileCache::addTile.TileCache holds precomputed heightfields and to turn them into nav mesh tiles TileCache::buildNavMeshTile is invoked, see https://github.com/ppiastucki/recast4j/blob/d7c652d82e58f4fa768c395efeb13a0877cd0704/detourtilecache/src/main/java/org/recast4j/detour/tilecache/TileCache.java#L480.

I hope the info is helpful.

[mitm001]

as they are already available as fields in NavMeshDataCreateParams

Yes, Area types are set when buildSolidHeightfield is called from TileLayerBuilders getHeightfieldSet.

I had to make some changes to those since my navmesh has multiple area types and your current implementation expects a single mesh with a single area modification. I changed them to accept triangle lengths paired with an area modification so I can mark triangles in buildSolidHeightfield.

This was something Mikko said he intended to do eventually but then he lost interest in his project before implementing it.

I am almost done implementing the offmesh connections for tile cache. This is a little more difficult to do since I call TestTileLayerBuilder.java#L64 to build the mesh rather than the AbstractTileLayersBuilder build.