UnigineEditor
Interface Overview
Assets Workflow
Settings and Preferences
Adjusting Node Parameters
Setting Up Materials
Setting Up Properties
Landscape Tool
Using Editor Tools for Specific Tasks
FAQ
Программирование
Fundamentals
Setting Up Development Environment
Usage Examples
UnigineScript
C++
C#
UUSL (Unified UNIGINE Shader Language)
File Formats
Rebuilding the Engine and 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
Networking Functionality
Pathfinding-Related Classes
Physics-Related Classes
Plugins-Related Classes
CIGI Client Plugin
Rendering-Related Classes

Migrating to Unigine

This section covers the basic aspects of transferring your experience with other engines to UNIGINE.

When you decide to switch to a more advanced technology there are a lot of issues that might give you some second thoughts or sometimes even prevent you from doing so. Misunderstandings and lack of information may lead to a wrong conclusion, that certain technology is difficult or impossible to use. That's why we created this section and will further extend it in the future.

Notice
Please consider our hardware requirements.

Below are the typical scenarios of migration to Unigine:

Last update: 13.04.2018