From 5955ac7864528f4ab52aec2fbf094fa3ef6c5b52 Mon Sep 17 00:00:00 2001 From: Kawe Mazidjatari <48657826+Mauler125@users.noreply.github.com> Date: Thu, 11 Jul 2024 09:20:55 +0200 Subject: [PATCH] Recast: fix incorrect comment (XZY -> XYZ) Raycast ignores the z-value after the XZY to XYZ change, previously it was the y-value. --- src/thirdparty/recast/Detour/Source/DetourNavMeshQuery.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/thirdparty/recast/Detour/Source/DetourNavMeshQuery.cpp b/src/thirdparty/recast/Detour/Source/DetourNavMeshQuery.cpp index a1ab7d39..6c616207 100644 --- a/src/thirdparty/recast/Detour/Source/DetourNavMeshQuery.cpp +++ b/src/thirdparty/recast/Detour/Source/DetourNavMeshQuery.cpp @@ -2387,7 +2387,7 @@ dtStatus dtNavMeshQuery::getEdgeMidPoint(dtPolyRef from, const dtPoly* fromPoly, /// /// Use Case Restriction /// -/// The raycast ignores the y-value of the end position. (2D check.) This +/// The raycast ignores the z-value of the end position. (2D check.) This /// places significant limits on how it can be used. For example: /// /// Consider a scene where there is a main floor with a second floor balcony