This page has been translated automatically.
Setting Up Development Environment
High-Level Systems
UUSL (Unified UNIGINE Shader Language)
File Formats
Rebuilding the Engine and Tools
Double Precision Coordinates
Core Library
Engine Classes
Node-Related Classes
Rendering-Related Classes
Physics-Related Classes
Bounds-Related Classes
GUI-Related Classes
Controls-Related Classes
Pathfinding-Related Classes
Utility Classes
This version of documentation is OUTDATED! Please switch to the latest one.

Creating Routes

Unigine has a built-in pathfinding system that includes navigation areas, obstacles and functions of the PathRoute class that are used to calculate the optimal routes among obstacles within navigation areas.

Via UnigineEditor, you can only add a navigation area (a sector or a mesh) to the scene and place obstacles. The 2D or 3D route that is calculated within the navigation area should be created from the script.

Creating a Route within Navigation Area

To create a route within a navigation area, in which no obstacles are placed, you can use the following:

Source code(UnigineScript)
// create a new route
PathRoute route = new PathRoute();
// set a radius for the point which will move along the route

// declare points between which the route should be calculated
Vec3 p0 = Vec3(-60.0f,-60.0f,5.0f);
Vec3 p1 = Vec3( 60.0f, 60.0f,5.0f);

// create a 3D route
You can create a 2D route the same way by calling the create2D() function.

To visualize the calculated route, call the renderVizualizer() function of the PathRoute class:

Source code(UnigineScript)
To visualize the navigation area, call the renderVizualizer() functions of the Node class:
Source code(UnigineScript)

You can affect route calculation via UnigineEditor by adjusting parameters of the navigation sector or mesh.

Creating a Route within Navigation Area with Obstacles

Creation of the route within a navigation area with obstacles is the same as creation of the route within an empty navigation area. Moreover, the route will be recalculated if the obstacle change its transformation.

If the obstacle is connected with a dynamically changing node that should be bypassed, this node should be set as a parent node for the obstacle. This will enable to simultaneously change transformation of the node and the obstacle. For example:

Source code(UnigineScript)
ObstacleBox box;
ObjectMeshStatic mesh;
PathRoute route;

Vec3 offset = Vec3(0.0f,0.0f,0.0f);
Vec3 p0 = Vec3(-60.0f,-60.0f,5.0f) + offset;
Vec3 p1 = Vec3( 60.0f, 60.0f,5.0f) + offset;
int init() {
	// create a navigation sector within which pathfinding will be performed
	NavigationSector navigation = new NavigationSector(vec3(128.0f,128.0f,8.0f));
	// remove the script ownership and add the node to UnigineEditor
	navigation.setWorldTransform(translate(Vec3(1.0f,1.0f,5.0f) + offset));
	// create a mesh that should be bypassed
	mesh = new ObjectMeshStatic("samples/common/meshes/box.mesh");
	// remove the script ownership and add the node to UnigineEditor
	// create an obstacle
	box = new ObstacleBox(vec3(1.2f,1.2f,1.2f));
	// remove the script ownership and add the node to UnigineEditor
	// add the obstacle as the child node to the mesh in order to change their transformation simultaneously
	// create a new route
	route = new PathRoute();
	// set a radius for the point which will move along the route
	return 1;
int update() {

	float ifps =;
	float angle = ifps * 90.0f;
	// change transformation of the mesh
	mesh.setTransform(mesh.getTransform() * rotateZ(angle));
	// recalculate the route in the current frame and render its visualizer
	return 1;
In the example above, the route is recalculated each frame. However, it is not recommended to do. You can calculate the route, for example, once per 10 frames.

In the result, you will have a simple navigation sector, in which the dynamically changing obstacle box is placed.

Here the obstacle is highlighted with red
Last update: 2017-07-03
Build: ()