From .obj to .navmesh

[namreeb]

You should be creating a tiled mesh. I don't know if there is really anything else in Detour anymore, anyway. There are many tiles. If you're doing 1 tile per ADT, you'll have several hundred tiles, and the (x, y) you give to Detour would be the ADT (x, y).

[hamburger12]

Yes until here i got it. What i mean is, do you have only ONE tile per ADT? Or is your tile splited up in smaler tiles. Its all i thing of difination xD

[namreeb]

I think it's a question of poor English on your part. That may be what you meant, but that's not what you said. It's up to you whether you want to have 1 tile = 1 ADT. It's certainly a good place to start.

[guizmows]

if you create only 1 tile per ADT, you will have problem with zone having a complex geometry (cities, ...)

I use to use 4 tiles per ADT, and now I'm using 16 (4*4) per ADT, because I want to be able to "rebuild" my tile faster if I want to add an obstacle.

[hamburger12]

So your files look like this ? :

tile_x_y_1
tile_x_y_2
tile_x_y_3
......

or is it still tile_x_y but the peaces for an adt are stored in a header?

(ADT = 533.333.. x 533.333.. Right)??

[guizmows]

I've one file per ADT (easier to find witch file to load) but this contains 16 tiles.
I use these values :

GRID_SIZE = (float)(533.0 + (1.0 / 3.0));
GridDiv = 4;
TileWidth = (TileVoxelSize / GridDiv) + (BorderSize * 2);
TileSize = (GRID_SIZE / GridDiv);

[Bananenbrot]

*dazzled by PHP radiance*

You can store multiple tiles in one file. I 256 mcnk-sized tiles in one file, resulting in one file per adt.
Just read the demo code -.- It is not any harder than ordinary reverse engineering, you know...

[Millow]

what size should the mesh be approximately for 1 ADT ?
for 32_48 in azeroth I have 505k, seems pretty small considering that the .obj is 4Mb.

[namreeb]

That's actually rather large, if memory serves. But my code had optimizations for discarding WMOs which don't actually land on the tile boundaries.

[hamburger12]

So if i use the Demo Code and try to call addTile it only add the first part. Problem seems to be the addtile func. Becouse it checks if there is allready a tile loaded and then it returns an error .

[guizmows]

each tile has a dtNavMeshCreateParams. in this param you've to set correct titleX and tileY value. Detour use this value in order to know where is located your map in the whole map.

[hamburger12]

Yeah and thats finaley my Problem .
Do you use a System like this :

Adt_10_20

Recast:

Tile 100_200
Tile 100_201
...

So 10 the adtx and 0 the first tile Praxis if code?

[guizmows]

no

you've to calculate your tile X adn Y according to your mesh origine (center of your continent for example)

pseudo code

centerX = (tileRealCoordXMin + tileRealCoordXMax) / 2; 
tileX = (centerX - globalMeshCenterX) / TileSize;

[hamburger12]

So this is my funktion to save a mesh.

void Sample_TileMesh::saveAll(const char* path, const dtNavMesh* mesh)
{
	int TileX = 40;
	int TileY = 33;

	int tileTempStartX = (TileX * 4) -3;
	int tileTempStartY = (TileY * 4) -3;

	int size = 4;

	int TempCountX = 0,TempCountY = 0;
	int iA = 0;
	int iB = 0;

	if (!mesh) return;
	
	FILE* fp = fopen(path, "wb");
	if (!fp)
		return;

	ofstream myfile;
	myfile.open ("Log.txt");
	
	// Store header.
	NavMeshSetHeader header;
	header.magic = NAVMESHSET_MAGIC;
	header.version = NAVMESHSET_VERSION;
	header.numTiles = 0;
	for (int i = 0; i < mesh->getMaxTiles(); ++i)
	{
		const dtMeshTile* tile = mesh->getTile(i);
		if (!tile || !tile->header || !tile->dataSize) continue;
		header.numTiles++;
	}
	memcpy(&header.params, mesh->getParams(), sizeof(dtNavMeshParams));
	fwrite(&header, sizeof(NavMeshSetHeader), 1, fp);

	// Store tiles.
	for (int i = 0; i < mesh->getMaxTiles(); ++i)
	{
		const dtMeshTile* tile = mesh->getTile(i);
		if (!tile || !tile->header || !tile->dataSize) continue;

		NavMeshTileHeader tileHeader;
		tileHeader.tileRef = mesh->getTileRef(tile);
		tileHeader.dataSize = tile->dataSize;

		tile->header->x = tileTempStartX + TempCountX;
		tile->header->y = tileTempStartY + TempCountY;

		myfile<<"LogId: "<< i << "TileX: "<<tile->header->x<<" TileY: "<<tile->header->y<<" CounterX: "<<TempCountX<<" CounterY: "<<TempCountY<<"\n";

		if(TempCountY == size -1)
		{
			TempCountX += 1;
			TempCountY = 0;
		}

		if(iB == size -1)
		{
			TempCountY = 0;
			iB = 0;
		}
		else
		{
			TempCountY += 1;
			iB += 1;
		}

		fwrite(&tileHeader, sizeof(tileHeader), 1, fp);

		fwrite(tile->data, tile->dataSize, 1, fp);
	}

	fclose(fp);
	 myfile.close();
}

But it still don't work o.O

[guizmows]

check :

dtNavMesh::getNeighbourTilesAt and dtNavMesh::calcTileLoc I hope it will help you to understand how Detour find neighbour tiles, and you will find how you have to name your tiles.