This page has been translated automatically.
Interface Overview
Assets Workflow
Settings and Preferences
Adjusting Node Parameters
Setting Up Materials
Setting Up Properties
Landscape Tool
Using Editor Tools for Specific Tasks
Setting Up Development Environment
Usage Examples
UUSL (Unified UNIGINE Shader Language)
File Formats
Rebuilding the Engine and Tools
Double Precision Coordinates
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
CIGI Client Plugin
Rendering-Related Classes
This version of documentation is OUTDATED! Please switch to the latest one.

Engine Main Loop

This article describes in detail the steps taken by the UNIGINE engine when the Engine::update(), Engine::render(), and Engine::swap() functions are called. For other steps and general information about execution sequence, see the Execution Sequence article.

Each stage of the main loop is initiated by the application window created during the Initialization stage.

In the performance profiler, the total time the main loop has taken, is displayed by the Total counter.


The update part of the execution sequence in the single-threaded mode includes the following:

  1. The FPS value starts to be calculated.
    Calculation of FPS starts only with the second rendered frame, while the very first one is skipped.
  2. All pending console commands that were called during the previous frame are executed. The commands are executed in the beginning of the update() cycle, but before the scripts are updated, because otherwise they may violate the current process of rendering or physical calculations.
  3. If the video_restart console command was executed previously (not in the current update stage), world shaders are created.
    When video is restarted (for example, when the video mode is changed), the application window calls the destroy() methods of the world, system, and editor logic and plugins. However, it is performed not in the current update stage, but earlier.
  4. A plugin update() function is called. What happens during it, solely depends on the content of this custom function.
  5. The editor logic that handles all editor-related GUI and logic is updated.
  6. The system logic is updated. The default system script update() function performs the following:
    • The system script handles the mouse. It controls whether the mouse is grabbed when clicked (by default), the mouse cursor disappears when not moved for some time (set by the MOUSE_SOFT definition), or not handled by the system (set by the MOUSE_USER definition, which allows input handling by some custom module).
    • The main menu logic is updated (if the MENU_USER definition is not set).
    • Other system-related user input is handled. For example, the world state is saved or restored, or a screenshot of the current UNIGINE window contents is made, if required.
    • If the GPU Monitor plugin is initialized (the HAS_GPU_MONITOR definition is set), the plugin output is displayed in the application window and additional console commands become available.
  7. Ambient sound sources timers are updated.
  8. If the world is loaded (it can be done from the console or via the system logic), the world logic gets updated. In the world logic update() function, you can code frame-by-frame behavior of your application (see details here).
    Physics, if any, and continuous operations (pushing a car forward depending on current motor's RPM, simulating wind blowing constantly, performing immediate collision response, etc.), can be implemented separately in the flush() function. This function is called with a fixed frame rate (while the update() function is called each frame).
    The world and its world logic are updated in the following order:
    1. The world logic update() function is executed: node parameters are updated, transformations for non-physical nodes are set and so on.
    2. The state of nodes existing in the world is updated (mostly for visible nodes): skinned animation is played, particle systems spawn new particles, players are repositioned, and so on. Triggered world callbacks are added to a stack (they will be executed later).
    3. World Expressions are updated. Code in World Expressions can be written via UnigineEditor.
    4. The world logic render() function is called.
  9. The system logic render() function is executed, if necessary (see details here). It can access the updated data on node states and correct the behavior accordingly in the same frame.
  10. The postUpdate() function of all plugins is called.
  11. The world spatial tree is updated.
  12. GUI is updated.

In the performance profiler, the total time of update stage is displayed by the Update counter.

Update in Multi-Threaded Mode#

In the multi-threaded mode, the update stage is implemented differently at some points:

  • The engine uses all available threads to update visible nodes, instead of updating them one by one. The world_threaded command sets the mode: multiple-threaded or single mode.
    Child nodes under 1 parent are always updated in 1 thread. To benefit from the advantages of multi-threading, computationally heavy nodes (like particles systems) should have different or no parents.
    As each Node Reference is handled as a root node without any parent, it is automatically optimized for multi-threading.
  • At the end of the update stage, multi-threaded physics and pathfinding start to be updated in their separate threads. Then they perform their tasks on all available threads in parallel to rendering. Use physics_threaded and pathfind_threaded commands to select the mode of the calculations.
    Nodes with computationally heavy bodies (like clothes and ropes) should not have one parent; otherwise, they will be updated in one thread.


As soon as the update stage is completed, UNIGINE can start rendering the world. In parallel, physics calculations and pathfinding are performed. This approach enables to effectively balance the load between CPU and GPU, and thus allows for higher framerate in the UNIGINE-based application.

Here is how the render stage works in the single-threaded mode:

  1. The editor logic render() function is called.
  2. The render() function of plugins is called, if they exist.
  3. UNIGINE renders the graphics scene (the world) and the sound scene, as they should be in the current frame. The graphics scene is sent to GPU, while the sound scene is sent to the sound card. As soon as the CPU finishes preparation of data and feeds rendering commands to the GPU, the GPU becomes busy with rendering the frame.

    In the performance profiler, the total time of rendering stage is displayed by the Render counter. After that, the CPU is free, so we can load it with calculations we need.

  4. The physics module calls the plugin flush() function, if it exists.
  5. The physics module calls the world logic flush() function. In the flush() function, you can modify physics.

    The flush() function is not called each frame. The physics module has its own fixed framerate, which does not depend on the rendering framerate. During each of such physics frames (or ticks), a number of calculation iterations are performed (flush() is called before each iteration).

  6. The physics module is updated: internal physics simulation starts. During this step, Unigine performs collision detection for all objects that have physical bodies and collision shapes.
    In the performance profiler, the total time of flush() together with physics simulation is displayed by the Physics counter.
  7. The pathfinding module is updated. In the thread performance profiler, the total time of pathfinding is displayed by the PathFind counter.
  8. The gui() function of plugins (if any) is called.
  9. At last and atop of all, GUI is rendered, if required. In the performance profiler, the total time of interface rendering is displayed by the Interface counter.


The swap stage is the last one in the main loop.

In the single-threaded mode, it includes the following:

  1. If the video_grab console command is executed previously, on this stage, the taken screenshot is saved in folder where all application data is stored.
  2. The plugin swap() function is called, if it exists.
  3. Synchronization of physics with the rendered world. Results of the physical calculations are applied to the world. That is, on the previous step we have calculated how physical bodies with collision shapes have changed their position and orientation (due to our flush-based logic or interaction). Now these transformations can be finally applied to nodes, i.e. rendered meshes.
    As synchronization of physics follows the rendering stage, applied physical transformations will be visible on the screen only in the next frame.
  4. Values shown in the performance profiler are updated.

After the swap() is completed, the application window initiates GPU buffers swapping as described here.

Swap in Multi-Threaded Mode#

Complementary to the steps described above, the swap stage in the multi-threaded mode includes waiting for all additional threads to finish their tasks. After that, physics and pathfinding threads are synchronized and calculations are applied to the world.

Last update: 2019-08-16
Build: ()