[This is preliminary documentation and is subject to change.]
Assembly: cai-nav (in cai-nav.dll) Version: 0.4.0.0 (0.4.0.0)
XNA Framework Only
.NET Compact Framework Only
|PathCorridor(Int32, Int32, NavmeshQuery, NavmeshQueryFilter)|
The straight path corners for the corridor. (The string-pulled path.)
The query filter used by the corridor.
Finds the corners in the corridor from the position toward the target. (The straightened path.)
Loads the corridor data into the provided PathCorridorData buffer.
Obtains a copy of the corridor path.
The number of polygons in the corridor path.
True if the object has been disposed and should no longer be used.
Checks the corridor path to see if its polygon references remain valid.
The corner point for the specified index.
|LoadLocals(PathCorridor, NavmeshPoint, NavmeshQuery, NavmeshQueryFilter)|
Sets the specified resources and resets the corridor.
The maximum number of corners that the corner buffer can hold.
The maximum path size that can be handled by the corridor.
Moves the position and target from their curent locations to the desired locations.
|MoveOverConnection(UInt32, array<UInt32>(), Vector3, Vector3)|
Moves over an off-mesh connection.
Moves the position from its current location to the desired location, adjusting the corridor as needed to reflect the new position.
Moves the target from its curent location to the desired location, adjusting the corridor as needed to reflect the change.
Attempts to optimize the path using a local area search. (Partial replanning.)
|OptimizePathVisibility(Vector3, Single, Boolean)|
Attempts to optimize the path if the specified point is visible from the current position.
The position within the first polygon of the corridor.
The query object used by the corridor.
Released the references to the query and filter.
Immediately frees all unmanaged resources allocated by the object.
Resets the corridor to the specified position.
Resizes the corner buffers.
The type of unmanaged resource used by the object.
|SetCorridor(Vector3, array<UInt32>(), Int32)|
Loads a new path and target into the corridor.
The target within the last polygon of the corridor.
The corridor is loaded with a path, usually obtained from a NavmeshQuery FindPath call. The corridor is then used to plan local movement, with the corridor automatically updating as needed to deal with inaccurate client locomotion.
Example of a common use case:
- Construct the corridor object using the NavmeshQuery and NavmeshQueryFilter objects in use by the navigation client.
- Obtain a path from a NavmeshQuery object.
- Use Reset(NavmeshPoint) to load the client's current position. (At the beginning of the path.)
- Use SetCorridor(Vector3, array<UInt32>(), Int32) to load the path and target.
- Use Corners to plan movement. (This is the straightend path.)
- Use the MovePosition(Vector3) to feed client movement back into the corridor. (Or Move(Vector3, Vector3) if the target is dynamic.) The corridor will automatically adjust as needed.
- Repeat the previous 2 steps to continue to move the client.
The corridor position and target are always constrained to the navigation mesh.
One of the difficulties in maintaining a path is that floating point errors, locomotion inaccuracies, and/or local steering can result in the client crossing the boundary of the path corridor, temporarily invalidating the path. This class uses local mesh queries to detect and update the corridor as needed to handle these types of issues.
The fact that local mesh queries are used to move the position and target locations results in two beahviors that need to be considered:
Every time a move method is used there is a chance that the path will become non-optimial. Basically, the further the target is moved from its original location, and the further the position is moved outside the original corridor, the more likely the path will become non-optimal. This issue can be addressed by periodically running the OptimizePathTopology(Boolean) and OptimizePathVisibility(Vector3, Single, Boolean) methods.
All local mesh queries have distance limitations. (Review the NavmeshQuery methods for details.) So the most accurate use case is to move the position and target in small increments. If a large increment is used, then the corridor may not be able to accurately find the new location. Because of this limiation, if a position is moved in a large increment, then compare the desired and resulting polygon references. If the two do not match, then path replanning may be needed. E.g. If you move the target, check the polygon reference of Target to see if it is as expected.