This page has been translated automatically.
Interface Overview
Assets Workflow
Settings and Preferences
Working With Projects
Adjusting Node Parameters
Setting Up Materials
Setting Up Properties
Landscape Tool
Using Editor Tools for Specific Tasks
Extending Editor Functionality
Setting Up Development Environment
Usage Examples
UUSL (Unified UNIGINE Shader Language)
File Formats
Rebuilding the Engine Tools
Double Precision Coordinates
Common Functionality
Controls-Related Classes
Engine-Related Classes
Filesystem Functionality
GUI-Related Classes
Math Functionality
Node-Related Classes
Objects-Related Classes
Networking Functionality
Pathfinding-Related Classes
Physics-Related Classes
Plugins-Related Classes
IG Plugin
CIGIConnector Plugin
Rendering-Related Classes
Warning! This version of documentation is OUTDATED, as it describes an older SDK version! Please switch to the documentation for the latest SDK version.
Warning! This version of documentation describes an old SDK version which is no longer supported! Please upgrade to the latest SDK version.

Navigation Sector

3D navigation feature is experimental and not recommended for production use.

A navigation sector is a cuboid-shaped navigation area that enables the following:

  • Both the 2D and 3D routes can be calculated within navigation sectors.
    • In case of 2D routes, a point moves in a lower plane of the navigation sector (Z coordinate is not taken into account). If the height or radius set for this point is greater than the size of the navigation sector, such sector is discarded from pathfinding.
    • In case of 3D routes, a point moves in three dimensions. If the radius set for this point is greater than the size of the navigation sector, such sector is discarded from pathfinding.
  • Routes can be calculated within several intersecting navigation sectors. The intersecting sectors are treated as a single navigation area.
    In case of 2D routes, the height difference between the intersecting sectors must not exceed the maximum height set for the 2D route; otherwise these sectors are discarded from pathfinding.

See also#

  • The NavigationSector class to manage navigation sectors via API
  • The PathRoute class to create 2D and 3D routes inside navigation sectors
  • The article on Creating Routes
  • A set of samples located in the <UnigineSDK>/data/samples/paths folder:
    • route_00
    • route_01
    • route_02
    • sector_00
    • sector_01
    • sector_02

Creating Navigation Sector#

To create a navigation sector via UnigineEditor:

  1. Run UnigineEditor.
  2. On the Menu bar, click Create -> Navigation -> Navigation Sector.

  3. Click somewhere in the world to place the navigation sector.

    A navigation sector
    A new navigation sector is added to UnigineEditor and you can edit it via the Parameters window.

The created navigation sector only provides an area within which 2D and 3D routes are calculated. The routes themselves should be created from the script.

Editing Navigation Sector#

In the Node tab of the Parameters window, you can adjust the following parameters of the navigation sector:

Navigation mask The navigation mask of the navigation sector must match the navigation mask of the route that is calculated within it. Otherwise, the sector does not participate in pathfinding. By using the navigation mask, you can specify sectors that must be ignored during pathfinding.
Quality Quality of optimization for route calculation. This value specifies the number of iterations that are used to find the shortcut. The higher the value, the longer the route calculation will take.
Velocity Scaling factor for velocity of the point that moves inside the navigation sector along the calculated route.
Dangerous Danger factor that indicates if a moving point should try to avoid the navigation sector.
If the danger factor exceeds the maximum danger factor set for the route, the navigation sector is excluded from pathfinding calculations.
Size Size of the navigation sector's box along the axes.
Last update: 2020-07-31
Build: ()