This page has been translated automatically.
Video Tutorials
Interface
Essentials
Advanced
How To
UnigineEditor
Interface Overview
Assets Workflow
Settings and Preferences
Working With Projects
Adjusting Node Parameters
Setting Up Materials
Setting Up Properties
Lighting
Landscape Tool
Sandworm
Using Editor Tools for Specific Tasks
Extending Editor Functionality
Built-in Node Types
Nodes
Objects
Effects
Decals
Light Sources
Geodetics
World Objects
Sound Objects
Pathfinding Objects
Players
Programming
Fundamentals
Setting Up Development Environment
Usage Examples
UnigineScript
C++
C#
UUSL (Unified UNIGINE Shader Language)
File Formats
Rebuilding the Engine Tools
GUI
Double Precision Coordinates
API
Containers
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
Content Creation
Content Optimization
Materials
Art Samples
Tutorials
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.

Obstacles

An obstacle is an invisible object which is placed inside a navigation area and is bypassed during pathfinding.

Notice
If you change obstacle transformation, route will be automatically recalculated in order to avoid the obstacle.

The obstacles can be added to the scene:

  • As a single node to indicate an area or a node that should be avoided during pathfinding. However, if you change transformation of the node, the obstacle transformation won't change.
  • As a child node of a node that should be bypassed. In this case, transformation of the obstacle will change together with the node transformation and a route will always be calculated correctly.

There are 3 types of the obstacles:

You should choose the most appropriate type depending on the form of the node that should be bypassed during pathfinding.

Usage Example#

Supposing, you need to add a node that changes its transformation each frame and should be bypassed during pathfinding. In this case, you should do the following:

  1. Place the required node inside the navigation area within which routes will be calculated.

    A cuboid-shaped ObjectMeshDynamic node placed inside the Navigation Sector
  2. Add the obstacle of the required type to the scene and combine its position with the node's position.
  3. Set the required size for the obstacle.

    The obstacle box and the node.
  4. In the World Hierarchy window, drag the obstacle node to make it a child of the required node.

    Notice
    This will enable to simultaneously change transformation of the node and the obstacle. You can also perform it via code.
  5. Now you can create a route from the script. The route will be automatically recalculated when the node transformation changes.

In the result, the route will be calculated as follows (the route is highlighted with white):

The route that bypasses the node marked as the obstacle box

See Also#

Last update: 2021-04-29
Build: ()