Project Workflow

Working with content includes the following:

1. Placing your assets in Unigine native runtime formats inside the data directory of the project folder or importing FBX models via UnigineEditor.

   The following runtime formats are supported:

   • *.mesh file format for static and skinned geometry.
   • *.anim file format for storing animation for skinned mesh.
   • *.dds file format for textures.
   • *.oga, *.ogg file formats for audio files.
   • *.ogv file format for video files.

   You can convert your assets into these formats by means of Unigine SDK:

   • Textures can be converted into the *.dds format by using the ImageDDS tool.
   • Textures can be converted automatically, if they are placed in the data/uncompressed folder.
     Notice

     When importing an FBX model with materials, all textures are converted automatically. The model itself is also automatically converted to a mesh.
   • 3D models can be directly exported from 3D editors or loaded into the engine from the intermediate formats (FLT, DAE) via Unigine plugins.
2. Assembling the scene via UnigineEditor, namely: placing objects, setting up materials, properties, lighting and physics.
   Notice

   Unlike the other engines, Unigine provides its own material system with predefined shaders for materials organized in libraries. You can adjust settings of the provided materials via UnigineEditor in order to get the required result.

   See also the article on World Management.

Unigine provides the following APIs for implementing the application logic:

• UnigineScript API for fast scripting with no code recompilation.
• C++ API for maximum performance of the application.
• C# API for integration with the existing C# code base.

You can use any of these APIs to implement your application. Each of them provides access to the engine modules and the content.

If you implement your application purely in C++ or C#, rebuilding of the application or its parts is required during development to check how changes made in the code affect the result.

• Articles in the section Programming Overview
• Article on Execution Sequence
• Article on Typical Architecture of a Unigine-Based Application