This page has been translated automatically.
Click here to view the original English version instead.
Getting Started
What's Inside?
Terminology
Project Workflow
Hardware Requirements
Principles of Operation
Virtual World Structure
World Management
Rendering
Rendering Sequence
Scattering
Alpha Blending
Shading
HDR Rendering
Temporal Anti-Aliasing
Postprocessing
Panoramic Rendering with AppPanorama Plugin
Projections with AppProjection Plugin
Current Viewport Grabbing with AppGrabber Plugin
Hiding Shading Artifacts with AppBorder Plugin
DirectX 11 Software Rendering with AppLevel Plugin
Physics
Shapes
Collision Detection
Joints
Simulation of Physics
Bit Masking
File System
Tools
SDK Browser
Projects
Licenses
UnigineEditor
Overview
Controls
Managing Worlds
Scene Navigation
Setting Up Cameras
Importing Nodes
Selecting and Positioning Nodes
Organizing Nodes
Rendering Settings
Camera Effects
Setting Up Materials
Setting Up Properties
Setting Up Physics
Terrain Editor
Terrain Grabber
System Menu
Video Grabber
Mask Editor
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
Launcher
Launcher Structure
Launcher Customization
Browser Functions
JS Functions
Log Functions
USC Interpreter
Archiver
Resource
Terrain
MeshImport
Upgrade Script
Built-in Objects
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
Effects
Particle System
Decals
Projected Decal
Orthographic Decal
Mesh Decal
Light Sources
Light Sources Parameters
Omni Light
Projected Light
World Light
Environment 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
Fundamentials
Programming Overview
Engine Architecture
Typical Architecture of a Unigine-Based Application
Memory Management
Setting Up Development Environment
Windows Development Environment
Linux Development Environment
Mac OS X Development Environment
UnigineScript
Creating UnigineScript Application
Adding Scripts to the Project
Script Debugging
High-Level Systems
Basic Utilities
Unigine::Schemer
Unigine::Skinner
Input System
Character System
KeyLine System
Dialogs Script
Cache Files
C++
Creating C++ Application
Creating C++ Plugin
C#
Creating C# Application
C# API Reference
UUSL (Unified UNIGINE Shader Language)
UUSL Data Types and Common Intrinsic Functions
UUSL Parameters
UUSL Textures
UUSL Semantics
UUSL Tessellation
Creating of Custom Shader for Deferred Rendering Pass
Creating of Custom Shader for Forward Rendering Pass
Creating of Custom Shader for Post-Processing
File Formats
Mesh File Formats
Material File Format
Startup Command-Line Options
Console
Rebuilding the Engine and Tools
Rebuild in Windows via Visual Studio
Rebuild in Mac OS X via Xcode
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
API
Core Library
Containers
Tree::ConstIterator Class (C++)
Tree::Iterator Class (C++)
Tree< Key, Data > Class Template (C++)
Map Class (C++)
ArrayMap Class (C++)
ArrayMap::Iterator Class (C++)
Vector::ConstIterator Class (C++)
Vector::Iterator Class (C++)
Vector< > Class Template (C++)
ArrayVector Class (C++)
Engine Classes
Engine Class (UnigineScript)
Engine Class (C++)
App Class
Config Class
Console Class
Editor Class
Filesystem Class
Game Class
Materials Class
Memory Class (UnigineScript)
Memory Class (C++)
Physics Class
Profiler Class
Properties Class
Sound Class
Splash Class
Visualizer Class
World Class
Unigine Namespace Functions (C++)
Node-Related Classes
Node Class
NodeDummy Class
NodeExtern Class
NodeExternBase Class
NodeLayer Class
NodePivot Class
NodeReference Class
NodeTrigger Class
Rendering-Related Classes
Render Class
Renderer Class
RenderState Class
Material Class
Shader Class
Texture Class
TextureRender Class
Mesh Class
Camera Class
Viewport Class
FFP Class
Physics-Related Classes
PhysicsIntersection Class
PhysicsIntersectionNormal Class
Bounds-Related Classes
BoundBox Class (UnigineScript)
BoundBox Class (C++)
BoundFrustum Class (UnigineScript)
BoundFrustum Class (C++)
BoundSphere Class (UnigineScript)
BoundSphere Class (C++)
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
Controls-Related Classes
Controls Class
ControlsApp Class
ControlsDummy Class
ControlsJoystick Class
ControlsSixAxis
ControlsXPad360 Class
Pathfinding-Related Classes
Navigation Class
NavigationMesh Class
NavigationSector Class
Obstacle Class
ObstacleBox Class
ObstacleCapsule Class
ObstacleSphere Class
PathRoute Class
PathRouteIntersection Class
Utility Classes
TypeInfo Class (C++)
Thread Class (C++)
Stream Class (C++)
StreamBase Class (C++)
Timer Class (C++)
Resource Class (C++)
Ptr< Type > Class Template (C++)
FunctionBase Class (C++)
CallbackBase Class (C++)
Checksum Class (C++)
Compress Class (C++)
ExternClass< Class > Class Template (C++)
Variable Class (C++)
ConsoleVariableFloat Class (C++)
ConsoleVariableInt Class (C++)
ConsoleVariableString Class (C++)
Package Class (C++)
GameIntersection Class
Path Class
Property Class
Content Creation
Content Pipeline
3D Models Requirements
Art Assets Conversion
Content Optimization
Materials
Hierarchy and Inheritance
Custom Materials
Tutorials
Adding Morph Targets
Setting Up Object LODs
Adding Sun, Sky and Clouds
Adding Impostors to Clutters
Unigine Demos
Migrating from UNIGINE 2.1.1 to UNIGINE 2.2
API Migration
Startup CLIs Migration
Console Migration
Content Migration
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.
    • On Mac OS X - Xcode or 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. On OS X, head tracking is available only for the 64-bit application version.
Dual output stereo 3D (AppSeparate plugin) Output 2 separate images for each eye.
Notice
The AppSeparate supports DirectX 11 only.

Panoramic rendering with a single output device (AppPanorama plugin) Render 180 degree panorama on one monitor. Several monitors are also supported.
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.
Notice
The AppWall plugin is not available on OS X.

GPU Monitor GPU frequencies and temperature monitoring.
Renderer Enable the ability to fire world script callbacks on API Renderer callbacks.
Notice
You cannot use any rendering mode in conjunction with the Renderer plugin.
AppGrabber Current viewport grabbing (AppGrabber plugin).

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.
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 click Run.
  • 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 click Edit.

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 and Mac OS X, 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 and Mac 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: 2017-07-03
Build: ()