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
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.


In terms of Unigine, all of the objects added into the scene are called nodes. Nodes can be used both directly or as reference nodes to which the other nodes refer.

Nodes and Node References

Nodes and node references are fundamental objects that form the world:

  •   Node is a generic entity representing any object that is positioned and stored in the world.
  •   Node Reference is a node that refers to an external file on the disk, which contains a pre-fabricated node (or a hierarchy of nodes) with all the material and property libraries that are required for its rendering.

The node reference should be used instead of the node if there are a lot of identical objects repeated in the world: it will enable to avoid manual editing each object if you need to make the same changes in all of these objects. For more details, read the article on Node Reference.

There are also the following differences between nodes and node references:

  • To create a node, you need to simply add any object to the scene. To create a node reference, you will need to export a node from UnigineEditor into a .node file and then specify it to be a node reference.
  • All changes made for the node are saved in the .world file and affect only one specific node. All changes made for the node reference are saved in the source .node file and affect all the nodes referenced to this file.

Base Nodes

Base nodes are invisible and perform the following:

  •   Dummy Node is used to organize the other nodes into a hierarchy.
  •   Layer enables to save all its child nodes into a separate .node file.
  •   Pivot serves as a pivot point for its child nodes.
  •   Trigger fires callbacks when it is enabled/disabled or its transformation has been changed.
Last update: 2017-07-03
Build: ()