This page has been translated automatically.
Video Tutorials
How To
Professional (SIM)
Interface Overview
Assets Workflow
Version Control
Settings and Preferences
Working With Projects
Adjusting Node Parameters
Setting Up Materials
Setting Up Properties
Using Editor Tools for Specific Tasks
Extending Editor Functionality
Built-in Node Types
Light Sources
World Nodes
Sound Objects
Pathfinding Objects
Setting Up Development Environment
Usage Examples
UUSL (Unified UNIGINE Shader Language)
File Formats
Materials and Shaders
Rebuilding the Engine Tools
Double Precision Coordinates
Animations-Related Classes
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
VR-Related Classes
Content Creation
Content Optimization
Material Nodes Library
Art Samples

Licensing and License Types

In UNIGINE, licenses are available for the use of Engineering and Sim SDK editions to develop an application, and in some cases — to use instances of created applications.

To have a clear understanding of license products in UNIGINE, we need to adopt the following notions:

Seat Major version used by developers to create a new project, write code, add content in the Editor, compile and build the project, run debug and release versions, i.e. the full application programming cycle.
Editor Seat Stripped-down version that allows only running an already created project in the Editor. It is designed for artists, who don't work with code and only create scenes in the Editor — add 3D models and configure them, set the environment, shadows, reflections, etc.
Channel Permission to run one instance of a final application (a finished product that doesn't require running any developer tools). Channels are required for applications that use networking, IG, VR, or any multi-window implementation. Regular desktop applications that don't use any additional features do not require a channel for running.


A Seat is a type of license required for developers to run an SDK (Software Development Kit), in which the development process takes place. This is a major version used by developers to create a new project, write code, add content in the Editor, compile and build the project, run debug and release versions, i.e. the full application programming cycle. Seats are used by programmers and artists to create a project, add code and content, and run a development/test version. It makes sense to buy Seats based on the number of developers simultaneously working on the project.

To install SDK to be used with the Seat license, see this guide.

To activate the Seat license, see this article.

Editor Seat#

Editor Seat allows only working in Editor with already existing projects. You cannot create a new project with this type of license — you can only modify an already existing project. This type of license is designed for artists who won't perform any programming and debugging, but just modify a project in Editor (add or delete 3D models, configure light and use other options available in Editor).

Installation and activation instructions for the Editor Seat are provided here:

After you have activated the Editor Seat, run the editor launching file in an already existing project (keep in mind that you won't be able to create any new project with this type of license).

When we say an already existing project, we mean a project that has been created using a Seat. You might have created it earlier having a full-fledged license or downloaded it from a repository using a VSC, or in some other way.

By the editor launching file we imply a script commonly available in the project folder, such as launch_editor.bat or Sometimes, there are no such files in the project folders or they are named differently. In any case, the project folder should contain project_folder/bin/Editor_x64.exe or project_folder/bin/Editor_double_x64.exe that you'll be able to run and work uninterrupted using this type of license.


Channels are required to run a final application: one (1) Channel for one (1) PC. Channels differ depending on the plugins used:

  • IG channel is a fully-featured license that is suitable for applications using networking (CIGI/HLA/DIS/Syncker) or high-level IG (Image Generator) system available in the SDK. It can also be used to run a VR app.
  • VR channel is a license suitable for applications using any head-mounted display (VR headset). It can't use any networking or IG tools available in UNIGINE SDK.

The table below lists the plugins available in the base configuration of Sim Per-Channel SDK Edition and the plugins that require either VR or IG Channel.

(no channel required)
VR Channel IG Channel
Base plugins Base + VR plugins
GPUMonitor Oculus SpiderVision
CadImporter Varjo Separate
FbxImporter OpenVR Surround
GLTFImporter TeslaSuit Syncker
Ultraleap LeapMotion IG
Kinect Geodetics CIGIConnector
Steam ARTTracker DISConnector
VrpnClient HLAConnector
  • All per-channel licenses purchased prior to UNIGINE 2.12 shall be treated as IG Channels.

Every instance of the application requires a license for running. It means that if you developed an application that requires 10 PCs to run it, you'll need 10 licenses. Or if you want your application to run on 10 different PCs at the same time, you'll also need 10 licenses.

See here how to activate the Per-Channel license.

Last update: 2024-07-12
Build: ()