R5Reloaded/r5sdk
1
0
Fork 0
mirror of https://github.com/Mauler125/r5sdk.git synced 2025-02-09 19:15:03 +01:00
Code Issues Packages Projects Releases Wiki Activity

Recast: remove cell height offset from poly mesh verts

Browse Source 
The reason why the BVTree's appeared under the polygon was because we were rendering and calculating them incorrectly. After fixing this, they now appeared above the polygons. This offset is not necessary as it causes BVTree's to build incorrectly.
This commit is contained in:
Kawe Mazidjatari 2024-10-15 15:43:49 +02:00
parent b5527cff5b
commit 272818ade0
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/thirdparty/recast/Recast/Source/RecastMeshDetail.cpp vendored
View File

@ -1405,10 +1405,15 @@ bool rcBuildPolyMeshDetail(rcContext* ctx, const rcPolyMesh& mesh, const rcCompa
verts[j*3+0] += orig[0];
verts[j*3+1] += orig[1];
// note(amos): the offset appears to be necessary, otherwise BVTrees
// note(amos): the offset appears to be necessary, otherwise BVTree's
// are built below the polygon.
// see https://github.com/recastnavigation/recastnavigation/issues/647
verts[j*3+2] += orig[2] + chf.ch; // Is this offset necessary?
// note(amos): this offset actually appears unnecessary, the BVTree's
// appeared under the polygon as we were rendering them incorrectly,
// and at the time of the initial comment, the BVTree wasn't computed
// correctly after the coordinate system conversion. Commented out
// the cell height offset.
verts[j*3+2] += orig[2]/* + chf.ch*/; // Is this offset necessary?
}
// Offset poly too, will be used to flag checking.
for (int j = 0; j < npoly; ++j)