From bbbdc0ec6439704882363c7f4ecf1e74397bb6b8 Mon Sep 17 00:00:00 2001 From: Krom Stern Date: Sat, 29 Aug 2015 17:22:35 +0300 Subject: [PATCH] Updated dtFindPathOptions description and options "Options for dtNavMeshQuery::FindPath" is not correct, the option is used in SlicedFindPath only DT_FINDPATH_LOW_QUALITY_FAR is not used anywhere I would also add, that even though raycast considers costs, does so not very well :-( --- Detour/Include/DetourNavMesh.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Detour/Include/DetourNavMesh.h b/Detour/Include/DetourNavMesh.h index 1060845..46071c6 100644 --- a/Detour/Include/DetourNavMesh.h +++ b/Detour/Include/DetourNavMesh.h @@ -118,11 +118,10 @@ enum dtStraightPathOptions }; -/// Options for dtNavMeshQuery::findPath +/// Options for dtNavMeshQuery::initSlicedFindPath and updateSlicedFindPath enum dtFindPathOptions { - DT_FINDPATH_LOW_QUALITY_FAR = 0x01, ///< [provisional] trade quality for performance far from the origin. The idea is that by then a new query will be issued - DT_FINDPATH_ANY_ANGLE = 0x02, ///< use raycasts during pathfind to "shortcut" (raycast still consider costs) + DT_FINDPATH_ANY_ANGLE = 0x02, ///< use raycasts during pathfind to "shortcut" (raycast still consider costs) }; /// Options for dtNavMeshQuery::raycast