Up to date
This page is up to date for Redot 4.3
.
If you still find outdated information, please create an issue.
NavigationPathQueryParameters3D¶
Experimental: This class may be changed or removed in future versions.
Inherits: RefCounted < Object
Provides parameters for 3D navigation path queries.
Description¶
By changing various properties of this object, such as the start and target position, you can configure path queries to the NavigationServer3D.
Tutorials¶
Properties¶
|
||
BitField[PathMetadataFlags] |
|
|
|
||
|
||
|
||
|
||
|
||
|
||
|
Enumerations¶
enum PathfindingAlgorithm: 🔗
PathfindingAlgorithm PATHFINDING_ALGORITHM_ASTAR = 0
The path query uses the default A* pathfinding algorithm.
enum PathPostProcessing: 🔗
PathPostProcessing PATH_POSTPROCESSING_CORRIDORFUNNEL = 0
Applies a funnel algorithm to the raw path corridor found by the pathfinding algorithm. This will result in the shortest path possible inside the path corridor. This postprocessing very much depends on the navigation mesh polygon layout and the created corridor. Especially tile- or gridbased layouts can face artificial corners with diagonal movement due to a jagged path corridor imposed by the cell shapes.
PathPostProcessing PATH_POSTPROCESSING_EDGECENTERED = 1
Centers every path position in the middle of the traveled navigation mesh polygon edge. This creates better paths for tile- or gridbased layouts that restrict the movement to the cells center.
flags PathMetadataFlags: 🔗
PathMetadataFlags PATH_METADATA_INCLUDE_NONE = 0
Don't include any additional metadata about the returned path.
PathMetadataFlags PATH_METADATA_INCLUDE_TYPES = 1
Include the type of navigation primitive (region or link) that each point of the path goes through.
PathMetadataFlags PATH_METADATA_INCLUDE_RIDS = 2
Include the RIDs of the regions and links that each point of the path goes through.
PathMetadataFlags PATH_METADATA_INCLUDE_OWNERS = 4
Include the ObjectID
s of the Objects which manage the regions and links each point of the path goes through.
PathMetadataFlags PATH_METADATA_INCLUDE_ALL = 7
Include all available metadata about the returned path.
Property Descriptions¶
The navigation map RID used in the path query.
BitField[PathMetadataFlags] metadata_flags = 7
🔗
void set_metadata_flags(value: BitField[PathMetadataFlags])
BitField[PathMetadataFlags] get_metadata_flags()
Additional information to include with the navigation path.
The navigation layers the query will use (as a bitmask).
PathPostProcessing path_postprocessing = 0
🔗
void set_path_postprocessing(value: PathPostProcessing)
PathPostProcessing get_path_postprocessing()
The path postprocessing applied to the raw path corridor found by the pathfinding_algorithm.
PathfindingAlgorithm pathfinding_algorithm = 0
🔗
void set_pathfinding_algorithm(value: PathfindingAlgorithm)
PathfindingAlgorithm get_pathfinding_algorithm()
The pathfinding algorithm used in the path query.
float simplify_epsilon = 0.0
🔗
The path simplification amount in worlds units.
If true
a simplified version of the path will be returned with less critical path points removed. The simplification amount is controlled by simplify_epsilon. The simplification uses a variant of Ramer-Douglas-Peucker algorithm for curve point decimation.
Path simplification can be helpful to mitigate various path following issues that can arise with certain agent types and script behaviors. E.g. "steering" agents or avoidance in "open fields".
Vector3 start_position = Vector3(0, 0, 0)
🔗
The pathfinding start position in global coordinates.
Vector3 target_position = Vector3(0, 0, 0)
🔗
The pathfinding target position in global coordinates.