From 3d2aa7b8fa4442fa4ce0e6a85f2c872776c7de35 Mon Sep 17 00:00:00 2001 From: smix8 <52464204+smix8@users.noreply.github.com> Date: Wed, 1 Jun 2022 17:02:12 +0200 Subject: [PATCH] Document that NavigationAgent height offset is mostly a placebo Document that NavigationAgent height offset is mostly a placebo. (cherry picked from commit b1d98534154dafa208076e8f8d7c93e4a43726f9) --- doc/classes/NavigationAgent.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/classes/NavigationAgent.xml b/doc/classes/NavigationAgent.xml index 1da8777dc..ee94d57a5 100644 --- a/doc/classes/NavigationAgent.xml +++ b/doc/classes/NavigationAgent.xml @@ -99,7 +99,7 @@ - The agent height offset to match the navigation mesh height. + The NavigationAgent height offset is subtracted from the y-axis value of any vector path position for this NavigationAgent. The NavigationAgent height offset does not change or influence the navigation mesh or pathfinding query result. Additional navigation maps that use regions with navigation meshes that the developer baked with appropriate agent radius or height values are required to support different-sized agents. If [code]true[/code] the agent is registered for an RVO avoidance callback on the [NavigationServer]. When [method set_velocity] is used and the processing is completed a [code]safe_velocity[/code] Vector3 is received with a signal connection to [signal velocity_computed]. Avoidance processing with many registered agents has a significant performance cost and should only be enabled on agents that currently require it.