This page has been translated automatically.
Click here to view the original English version instead.
Getting Started
What's Inside?
Project Workflow
Migrating to Unigine
Migrating to Unigine From UnrealEngine
Migrating to Unigine From Unity
Programming Quick Start
1. Basic Scene Objects and Coordinate System
2. Logging and Printing Messages to Console
3. Saving and Loading a World
4. Closing the Application
5. Working with Smart Pointers
6. Creating and Deleting Nodes at Runtime
7. Creating and Setting Up a Camera
8. Creating and Setting up Light Sources
9. Creating, Applying and Deleting Materials at Runtime
10. Managing Existing Scene Objects
11. Performing Basic Transformations (Move, Rotate, Scale)
12. Making It in Time
13. Managing Intersections
14. Getting and Managing User Inputs
15. Implementing Game Logic and Using Properties
16. Creating User Interface
System Requirements
Principles of Operation
Virtual World Structure
World Management
Properties
Hierarchy and Inheritance
Custom Component System
Rendering
Rendering Sequence
Scattering
PSSM
Temporal Anti-Aliasing
Alpha Blending
Physics
Shapes
Collision Detection
Joints
Simulation of Physics
Bit Masking
Import System
File System
SDK Browser
Projects
Licenses
Add-Ons
Kinect2 Add-On
Tutorials Content Add-On
Vegetation Add-On
VRPN Add-On
UnigineEditor
Interface Overview
Layout Customization
Assets Workflow
Asset Types
Assets and Runtime Files
Organizing Assets
Copying Assets From Other Projects
Project Files
Version Control
Settings and Preferences
Editor Hotkeys
Global Physics Settings
Global Sound Settings
Working With Projects
Managing Worlds
Scene Navigation
Creating and Importing Nodes
Selecting and Positioning Nodes
Organizing Nodes
Exporting Nodes
Instancing Nodes
Adjusting Node Parameters
Transformation and Common Parameters
Visual Representation
Properties
Physics
Setting Up Materials
Organizing Materials
Setting Up Properties
Organizing Properties
Setting Up Cameras
Using Visual Helpers
System Menu
Landscape Tool
Creating a Terrain
Creating a Geo-Referenced Terrain
Generating Detail Masks
Generating Vegetation
Generating Spline Objects
Generating Vector Objects
Generating Point Objects
Generating Buildings
Procedural Refinement
Distributed Computing
Using Editor Tools for Specific Tasks
Capturing Screenshots and Frame Sequences
Adding Variations for a More Realistic Environment
Manual Terrain Modification
Mask Editor for Grass and Clutters
Bake Lighting
FAQ
Switching From the Previous Version of the Editor
Tools
Plugins for 3D Editors
Plugins for 3ds Max
Plugins for Maya
Performance Profiling Tools
Performance Profiler
Microprofile
ResourceEditor
MeshViewer
NormalCombiner
NormalMapper
AmbientMapper
AlphaMapper
ImageDDS
ImageTTF
USC Interpreter
Tileset File
Archiver
Resource
MeshImport
Upgrade Script
Built-in Node Types
Nodes
Node
Node Reference
Dummy Node
Layer
Pivot
Trigger
Objects
Dummy Object
Static Mesh
Skinned Mesh
Dynamic Mesh
Mesh Cluster
Mesh Clutter
Text Object
Sky
Cloud Layer
Effects
Particle System
Decals
Projected Decal
Orthographic Decal
Mesh Decal
Light Sources
Light Sources Parameters
Omni Light
Projected Light
World Light
Environment Probe
Voxel Probe
Geodetics
Geodetic Pivot
World Objects
World Layer
Sector
Portal
World Trigger
World Cluster
World Clutter
Switcher
World Expression
Sound Objects
Sound Source
Sound Reverb
Pathfinding Objects
Players
Player Actor
Player Dummy
Player Persecutor
Player Spectator
Programming
Fundamentals
Programming Overview
Engine Architecture
Typical Architecture of a Unigine-Based Application
Memory Management
Accessing Nodes and Files via Properties
Matrix Transformations
Setting Up Development Environment
Windows Development Environment
Linux Development Environment
Usage Examples
Custom Component System
Basic Object Movements
Creating and Attaching a Cloth
Creating a Car with Suspension Joints
Creating Mirrors Using Viewports (Rendering to Texture) or Materials
A Simple Mechanism Using Joints
Creating Routes
Creating Pylons and Wires Using Ropes
Dynamic Meshes
Enabling Selective Surface-Based Collision
Playing Sounds on Collisions
Intersections
Mesh Class
Working with Console
Sharing Data
UnigineScript
Creating UnigineScript Application
Adding Scripts to the Project
Script Debugging
Cache Files
C++
Creating C++ Application
Creating C++ Plugin
C#
Creating C# Application
C# API Reference
UUSL (Unified UNIGINE Shader Language)
UUSL Keywords
UUSL Common Intrinsic Functions
UUSL GBuffer Structure
UUSL Data Structure
UUSL Parameters
UUSL Textures
UUSL Semantics
UUSL Tessellation
UUSL Compute Shaders
Creating a Custom Shader for Deferred Rendering Pass
Creating a Custom Shader for Forward Rendering Pass
Creating a Custom Shader for Post-Processing
File Formats
Mesh File Formats
Property File Format
Spline File Format
Startup Command-Line Options
Console
Configuration File
Rebuilding the Engine and Tools
Rebuild in Windows via Visual Studio
Semi-automatic Compilation with Build Script
Manual Compilation with SCons
Preprocessor Macros for Rebuilding the Engine
Protecting Your Data with a Password
GUI
RC Files
Skin Layout
Usage Example
Double Precision Coordinates
Usage
Performance Analyzer
How to Generate Shader Cache
API
Containers
Container Functions
ArrayVector Class
Map Class
Set Class
Common Functionality
Async Class
Atomiclock Class
Blob Class
CallbackBase Class
Checksum Class
Compress Class
ConsoleVariableFloat Class
ConsoleVariableInt Class
ConsoleVariableString Class
Expression Class
ExternClass Class
FunctionBase Class
Hash Class
Hasher Class
Image Class
Interpreter Class
Json Class
Log Class
OS Functions
Path Class
Plugin Class
Property Class
Ptr Class
Reflection Class
RegExp Class
Resource Class
Stream Class
String Class
StringArray Class
StringPtr Class
StringStack Class
System Functions
Thread Class
Timer Class
TypeInfo Class
Unigine Namespace Items
Utils Class
Xml Class
Variable Class
Controls-Related Classes
Controls Class
ControlsApp Class
ControlsDummy Class
ControlsJoystick Class
ControlsSixAxis
ControlsXPad360 Class
Engine-Related Classes
App Class
Config Class
Console Class
Editor Class
Engine Class
EnginePtr Class
engine.system Functions
EnginePlugins Class
Game Class
GameIntersection Class
Memory Class
Profiler Class
Properties Class
Sound Class
Sounds Class
Splash Class
Visualizer Class
World Class
Filesystem Functionality
Dir Class
File Class
FileSystem Class
FileSystemAssets Class
AsyncQueue Class
File System Functions
Package Class
PackageUng Class
UGUID Class
GUI-Related Classes
Gui Class
UserInterface Class
Widget Class
WidgetButton Class
WidgetCanvas Class
WidgetCheckBox Class
WidgetComboBox Class
WidgetDialog Class
WidgetDialogColor Class
WidgetDialogFile Class
WidgetDialogImage Class
WidgetDialogMessage Class
WidgetEditLine Class
WidgetEditText Class
WidgetExternBase Class
WidgetExtern Class
WidgetGridBox Class
WidgetGroupBox Class
WidgetHBox Class
WidgetHPaned Class
WidgetIcon Class
WidgetLabel Class
WidgetListBox Class
WidgetManipulator Class
WidgetManipulatorRotator Class
WidgetManipulatorScaler Class
WidgetManipulatorTranslator Class
WidgetMenuBar Class
WidgetMenuBox Class
WidgetScroll Class
WidgetScrollBox Class
WidgetSlider Class
WidgetSpacer Class
WidgetSpinBox Class
WidgetSprite Class
WidgetSpriteNode Class
WidgetSpriteShader Class
WidgetSpriteVideo Class
WidgetSpriteViewport Class
WidgetTabBox Class
WidgetTreeBox Class
WidgetVBox Class
WidgetVPaned Class
WidgetWindow Class
Math Functionality
Predefined Constants
Geometry Class
Math Common Functions
Math 2D Functions
Math Exponential Functions
Math Matrix Functions
Math Random Functions
Math Trigonometrical Functions
bvec4 Class
dmat4 Class
dvec2 Class
dvec3 Class
dvec4 Class
half Class
hvec2 Class
hvec3 Class
hvec4 Class
ivec2 Class
ivec3 Class
ivec4 Class
mat2 Class
mat3 Class
mat4 Class
quat Class
vec2 Class
vec3 Class
vec4 Class
Node-Related Classes
Node Class
NodeDummy Class
NodeExtern Class
NodeExternBase Class
NodeLayer Class
NodePivot Class
NodeReference Class
NodeTrigger Class
Networking Functionality
Socket Class
Pathfinding-Related Classes
Navigation Class
NavigationMesh Class
NavigationSector Class
Obstacle Class
ObstacleBox Class
ObstacleCapsule Class
ObstacleSphere Class
PathRoute Class
PathRouteIntersection Class
Physics-Related Classes
Physics Class
PhysicsIntersection Class
PhysicsIntersectionNormal Class
Plugins-Related Classes
AppEasyBlendInterface Class
ColladaImport Class
OpenFlightImport Class
engine.grabber Functions
engine.kinect Functions
engine.oculus Functions
AppProjectionInterface Class
engine.surround Functions
engine.vive Functions
engine.wall Functions
CIGI Client Plugin
CIGI Client interface
IArticulatedPart Class
IComponent Class
IEntity Class
IViewBase Class
IView Class
IViewGroup Class
ICigiHostPacket Class
ICigiArticulatedControl Class
ICigiArticulatedShortControl Class
ICigiAtmosphereControl Class
ICigiCelestialControl Class
ICigiComponentControl Class
ICigiComponentShortControl Class
ICigiEntityControl Class
ICigiEntityClampedControl Class
ICigiEnvironmentControl Class
ICigiEnvironmentRequest Class
ICigiIGControl Class
ICigiMaritimeControl Class
ICigiRateControl Class
ICigiSensorControl Class
ICigiSymbolCircleDef Class
ICigiSymbolClone Class
ICigiSymbolControl Class
ICigiSymbolShortControl Class
ICigiSymbolLineDef Class
ICigiSymbolSurfaceDef Class
ICigiSymbolTextDef Class
ICigiTerrestrialControl Class
ICigiTrackerControl Class
ICigiViewControl Class
ICigiWaveControl Class
ICigiWeatherControl Class
ICigiViewDef Class
ICigiEarthModelDef Class
ICigiSegmentDef Class
ICigiTrajectoryDef Class
ICigiVolumeDef Class
ICigiHatHotRequest Class
ICigiIGPacket Class
ICigiStartOfFrame Class
ICigiAerosolResponse Class
ICigiHatHotResponse Class
ICigiHatHotExtResponse Class
ICigiLosResponse Class
ICigiLosExtResponse Class
ICigiLosSegmentRequest Class
ICigiLosVectorRequest Class
ICigiMaritimeResponse Class
ICigiPositionRequest Class
ICigiPositionResponse Class
ICigiSensorResponse Class
ICigiSensorExtResponse Class
ICigiTerrestrialResponse Class
ICigiWeatherResponse Class
Rendering-Related Classes
Camera Class
Ffp Class
Material Class
Materials Class
Mesh Class
Primitives Class
Render Class
RenderEnvironmentPreset Class
Renderer Class
RenderContext Class
RenderState Class
Shader Class
StructuredBuffer Class
Texture Class
TextureRender Class
Viewport Class
Content Creation
3D Models Requirements
Art Assets Conversion
Content Optimization
Materials
Hierarchy and Inheritance
Custom Materials
Samples
Tutorials
Adding Morph Targets
Setting Up Object LODs
Adding Impostors to Clutters
Video Tutorials
Interface
Interface Overview
The Scene Viewport
Essentials
Importing 3D Models
Instancing Nodes
Materials
Lighting
Tracker Tool
Global Illumination
Migrating to UNIGINE 2.7
API Migration
Console Migration
Content Migration
Old Editor Workflow Projects
Assets Workflow Projects
Table of Contents
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.

Working with Projects

In This Article:

A project is an independent entity that contains all the data on your application content organized in a set of directories. The .project file containing metadata is associated with the project.

Notice
One project can consist of several worlds. So, there is no need to create a separate project for each world.

Creating New Project

Before starting to create new projects you should have an SDK installed. Once you have the required version of the SDK, you can create a new project as follows:

  1. Open the Projects tab in the SDK browser.

  2. Click Create New. The new project creation window will be opened.
  3. Define the name of the project, choose a path to store project files and specify the SDK to be used.

    Notice
    The project will be created in the <project path>/<unigine_project> folder.
  4. Specify the required application and general settings.
  5. Specify the add-ons to be added (optional).
  6. Click Create New Project. The project will appear in the projects list.

Notice
You can change the project settings any time by clicking Other Actions -> Configure Project.

Application Settings

The project can be created with the following application settings:

API Programming language to be used for project creation. The following APIs are available:
  • UnigineScript only - UnigineScript will be used to implement the project.
  • C++ - C++ API will be used to implement the project. Depending on the OS, you can choose the following project patterns:
    • On Windows - Visual Studio 2013 or QMake.
    • On Linux - GNU Make.
  • C# - C# API will be used to implement the project. The Visual Studio will be used to compile a project.
Architecture The version of the release version of an application:
  • 32 bit - create the 32-bit release version of the application (_x86 postfix of the binary executable).
  • 64 bit - create the 64-bit release version of the application (_x64 postfix of the binary executable).
  • 32 and 64 bits - create the both 32-bit and 64-bit release versions of the application.
Notice
The libraries and binaries of the corresponding version will be copied to the bin directory of the project folder.
Precision The coordinates precision to be used:

General Settings

The project can be created with the following general settings:

GUI-based settings configurator Create a project with the launcher.

Click Video output options to specify the following:

NVIDIA 3DSurround 3-monitor stereo 3D (App3DSurround plugin) Render the application across 3 monitors using the NVIDIA 3D Vision technology and multiple GPUs.
Notice
The App3DSurround plugin is available on DirectX 11 only.
NVIDIA 3DVision stereo 3D (App3DVision plugin) Render the application onto 1 monitor using NVIDIA 3D Vision technology.
Notice
The App3DVision plugin is available on DirectX 11 only.
Oculus support (AppOculus plugin) Create project with the Oculus Rift virtual display support.
Notice
On Linux, there is no head tracking support.
Dual output stereo 3D (AppSeparate plugin) Output 2 separate images for each eye.
Notice
The AppSeparate supports DirectX 11 only.

Multi-projector output with edge blending and non-linear image mapping Create a project with the AppProjection plugin. All necessary files are copied and the launcher with the corresponding settings is generated.
3-monitor output (AppSurround plugin) Render the application across 3 monitors simultaneously.
Monitor wall (AppWall plugin) Render the application into the configurable number of monitors.

GPU Monitor GPU frequencies and temperature monitoring.

Add-Ons

The project can be created including any add-on available in the Add-Ons tab. All of the required add-ons can be added both on and after project's creation.

Specifying Add-Ons on Project's Creation

To create the project with an add-on, you should do the following:

  1. Download the required add-on in the Add-Ons tab by clicking Install.

    Notice
    Any amount of add-ons could be added to a project afterwards.
  2. On project creation, specify the add-ons to be included by clicking the Add-ons (0) button.

  3. Drop the required add-ons from the Available field to In Use. You can add any amount of add-ons to the project. After all add-ons are dropped, click Ok.

    Notice
    If you haven't downloaded the add-on, click Manage installed add-ons. You will be redirected to the page with available add-ons.
  4. Click Create New Project. To enable added add-ons in the project, you should follow instructions on each add-on.

Specifying Add-Ons for Existing Project

To extend an existing project with add-ons, do the following:

  1. Download the required add-on in the Add-Ons tab by clicking Install.

    Notice
    Any amount of add-ons could be added to a project afterwards.
  2. Click Other Actions -> Configure Project.

  3. Click the Add-ons (0) button and drag and drop the required add-ons from the Available field to In Use.

    Notice
    If you haven't downloaded the add-on, click Manage installed add-ons. You will be redirected to the page with available add-ons.
  4. Click Ok and then click Update Configuration.

Adding Existing Project

To add an existing project to the browser, do the following:

  1. Click Add Existing in the Projects tab.

  2. In the file dialog window that opens, specify the path to the project folder and click Import Project. The project will appear in the projects list.

    If the project is created on UNIGINE 1, you will have to specify the following information on the project:
    Project name The name of the project.
    SDK The version of UNIGINE SDK used to create the project.
    Edition The edition of UNIGINE SDK used to create the project.
    Type The type of UNIGINE SDK used to create the project.
    Architecture The version of the release version of an application (32 or/and 64 bit).
    Precision he coordinates precision used to create the project.
    This information is required to create the .project file containing metadata associated with the project.

Notice
If the added project was created in the SDK of a previous version, it will be marked with the Upgrade available label.

Upgrading Existing Project

Projects that require upgrade are marked with the Upgrade available label:

To upgrade your project to the newest installed version of UNIGINE SDK, do the following:

  1. Click this label or Other Actions -> Configure Project. The following form will open:

  2. Choose the newest installed version of the SDK and click Update Configuration.

  3. Specify a path to the backup folder into which the original project will be copied. Leave Migrate Content checked and click Upgrade Project.

The project will be upgraded automatically. You can also manually upgrade the project by running the upgrade script. In both cases, the same script will be used.
Notice
The source code should be upgraded manually by using the Migration Guide.

Running Project with Default Settings

There are several options of running project with default settings:

  • Run the project without the loaded editor by clicking Run:

  • Run the project with the loaded editor by clicking Edit Content.

Notice
You can also use launchers created by default in the project folder:
  • launch_debug - the launcher of the project's debug version.
  • launch_editor - the launcher of the project's with the loaded editor.
  • launch_release - the launcher of the project's release version.
  • launcher - the startup file for the launcher that provides a GUI to configure application options and run the application. This launcher can be customized and used in the release version of your project. To create a project with the launcher, check the GUI-based settings configurator box in the project's creation window.

Running Project with Custom Settings

There are also several options of running project with custom settings:

  • Run the project without the loaded editor by clicking an ellipsis under the Run button:

    In the Customize Run Options form that opens, set the required values and clickRun.
  • Run the project with the loaded editor by clicking an ellipsis under the Edit Content button:

    In the Customize UnigineEditor Options form that opens, set the required values and clickEdit.

Customize Run Options

Via this form the project without the loaded editor can be run with the custom settings.

Depending on the value of the Application option, different sets of options are available:

  • Default - the default main application (<project_name>_x*.exe) will be run:

    The default main application should be used when only UnigineScript is used to implement the project. In this case, the following options can be customized:
    Debug Indicates whether debug or release version of the application should be run.
    Architecture The version of the main application to run. Available values:
    • 32-bit - the 32-bit version of the main application.
    • 64-bit - the 64-bit version of the main application.
    Arguments Start-up command-line options.
    Remember Indicates whether to remember the specified custom settings for future run or not.
  • Custom - a custom main application will be run:

    This option should be chosen if the C++ or C# API is used to implement the project (besides UnigineScript). In this case, the following options can be customized:
    Binary Name of the custom main application. Here the name of the compiled binary executable located in the bin folder of the project should be specified. If the binary executable is located outside this folder, a path to it relative to the bin folder should be specified.
    Arguments Start-up command-line options.
    Remember Indicates whether to remember the specified custom settings for future run or not.

Customize UnigineEditor Options

Additional arguments Start-up command-line options.
Debug The editor version (debug or release) that will be used for project's editing.
Remember Indicates whether to remember the specified custom settings for future run or not.

Editing Project

To open the project for editing:

  • On Windows, click Edit Code:

    The project will be opened for editing in an associated tool. To change a tool, click an ellipsis under Edit Code. By default, the following form will open:

    Choose Custom in the drop-down list and specify a path to a custom tool (e.g. IDE or editor) with required arguments:

  • On Linux, click Open folder and then edit the code in an associated tool:

See the articles in the Programming Overview section to learn how to edit the opened project.

Assembling Project

To create the release build of the project:

  1. Click Other Actions:

  2. Click Assemble project. The following form will open:

  3. Specify the required settings (see below) and click Assemble.

Assembling Settings

Output folder The release build destination folder.
Warning
You shouldn't create this folder inside your project folder, as it may significantly increase its size.
Exclude files Files and folders that should be excluded from the release build. Use the wildcards patterns to exclude the required items.
Architecture The release build architecture type.
Custom config path The path to the custom configuration file for the release build (optional).
Compress to UNG Types of files (for example, .h, .cpp, .ui, .mat, .world, .node, etc.) that should be compressed to reduce hard drive memory usage. This won't influence the engine performance much. Use the wildcards patterns to include/exclude the required items. The maximum size of the archive is 2 GB.
Notice
Data streaming doesn't work for UNG/ZIP contents.
Strip binaries
Notice
This option is available on Linux only.
Delete all debug information from the build binaries. This will reduce the binaries size without any performance cost.

Other Actions

When clicking the Other Actions button, the following form opens:

Configure Project Change project settings.
Assemble Project Specify settings to be used for assembling the project.
Open Folder Open the project folder.
Delete Delete the project.

Updating Project Configuration

When clicking Other Actions -> Configure Project, the following form opens:

Via this form you can change settings of an existing project: the version of the release application, the coordinates precision and the general settings. Also this option should be used when you need to upgrade the existing project to the newest version of the SDK.

Moreover, you can restore the project's files that were corrupted, missed or mistakenly modified. For this, you should leave settings in the form unchanged and press the Update Configuration button. In this case, the following files of the project will be restored (they will be copied from the SDK):

  • Binaries
  • core.ung, editor.ung and scripts.ung
  • Launchers
Notice
If some of the files listed above are changed, the .modified postfix will be added to names of such files. At that, the files from the SDK will also be copied.
Last update: 2018-04-26
Build: ()