support for larger index ranges about recastnavigation HOT 2 CLOSED

Actually, I did that so my open world engine would stream a huge parts of world.

DetourNavMesh.cpp :

255 - m_saltBits = dtMin((unsigned int)31, 32 - m_tileBits - m_polyBits);
255 + m_saltBits = dtMin((unsigned int)sizeof( dtPolyRef )*8 - 1, sizeof( dtPolyRef ) * 8 - m_tileBits - m_polyBits);

DetourNavMesh.h

30 -typedef unsigned int dtPolyRef;
30 +typedef unsigned long long dtPolyRef;

34 -typedef unsigned int dtTileRef;
34 +typedef unsigned long long dtTileRef;

It doesnt change the m_tileBits m_polyBits politicy, bu adds 64bit poly refID. It dynamicly scales salt Bits also. Thanks to that in my project I can use like ~30k tile meshes each one with a couple of K polys.

But it brokes the saving to data and readig from buffor ready tiles ( in case You saves ready tile meshes somewhere - not compatable with 32bit poly ref ID ).

from recastnavigation.

Added a #define support for compiling Detour with 64bit dtPolyRefs, check the latest version. Let me know if you ran into any problems with it.

With the change, the bits used for tiles, polygons, and salt are fixed (as there are so many bits to spare), you don't need to specify max polygons when you init the navmesh, but you'll need to define max tiles at it is also used for allocating the tile stubs.

As noted, you will need to rebuild all your tiles when you change to 64bit indices as some of the fields in the tile data use polyrefs. Yes, I do regret this choice :)

--mikko

from recastnavigation.