|PathEngine home||previous: ||next: |
Most of the API methods dealing with positions use the cPosition
This explicitly specifies a position on the surface of a ground mesh in such a way as to enable operations relating to that position to be performed efficiently and unambiguously. (See
The following methods provide the general form of this functionality:
The positionFor3DPoint methods are provided for converting from 'anchor' style representations.
The positionNear3DPoint method is provided for converting clicked positions or other arbitrary 3d positions such as positions of objects that have been placed freely in 3d.
The following methods provide the same functionality, but enable the resulting point to be restricted to to a specified 'section' of the mesh:
The following method is then an extended version of the positionNear3DPoint() methods, providing similar functionality to positionInSectionNear3DPoint(), but with the posibility to obtain multiple points when there are multiple (locally unconnected) pieces of ground mesh near the query position:
The following method is also supplied to support the specific case of 'anchor' resolution at content time in cases where terrain stand-in geometry is being used and there is no access to the terrain detail at that point:
Sections can be set up with the PE_FaceAttribute_SectionID face attribute.
When a particular sectionID value is known to contain only non-overlapping geometry
(i.e. geometry with only one Z value per horizontal position),
After a position has been found with this method the obstacle shape coordinates can be modified to enable the obstacle to be rooted at the found position.
It is important to be aware that the methods for resolving positions from 3D space all return a position on the pathfinding ground surface, but with the possibility for this resolved position to then be obstructed (either by the mesh external boundary expansion, or by expanded placed obstacles).
In many cases, for example when you want a position to start pathfinding or for use as a pathfinding target, it is necessary to find a position that is both on the pathfinding ground surface and inside pathfinding unobstructed space.
(For more explanation of the difference between pathfinding ground, and unobstructed space, see
In addition to position resolution on the ground mesh, PathEngine then also provides methods for finding nearby positions within pathfinding unobstructed space, for this purpose.
Please refer to
The following methods enable positions on the ground to be generated randomly:
You can also build cPosition instances based on known start positions and linear traversals through the ground mesh.
In each case the cell value can then be used, in conjunction with the horizontal target coords, to manually construct a cPosition instance for the target position.
The following methods enable ground height to be determined at a given position on the ground:
It some cases it may be necessary to choose a scale for PathEngine coordinates that differs from the
scale used for general world coordinates in game.
In this case scaling and translation can be applied at the same time as converting to and from PathEngines position representation.
Because PathEngine's cPosition representation is unambiguous with respect to placement on overlapping layers of geometry, it is preferable to maintain agent positions in this representation and just generate a 3d position when this is needed for rendering, physical interactions, and so forth.
A 'terrain callback' mechanism is provided
for ground meshes that include terrain areas with a lot of height detail,
enabling the heightAtPosition queries to be directed back to client supplied
terrain callback functions for queried positions that fall on terrain areas.
These client supplied functions can take advantage of the specific nature of client side terrain representations such as faces being organised in a grip, and so on, to provide the best possible performance for mapping ground positions back to world coordinates.
In cases where ground meshes include a lot of height detail,
and for some reason the terrain callback mechanism cannot be used,
you can tell PathEngine to generate additional partitioning information to speed up the heightAtPosition queries.
To do this just set the 'partitionTranslationTo3D' option to 'true' when calling loadMeshFromBuffer_WithOptions().
For a mesh with lots of height detail this option was measured to reduce times for the heightAtPosition queries by 88%, at the cost of a 7% increase in memory use when loading the mesh.
|Documentation for PathEngine release 6.00 - Copyright © 2002-2016 PathEngine||next: |