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
Networking Functionality
Pathfinding-Related Classes
Physics-Related Classes
Plugins-Related Classes
CIGI Client Plugin
Rendering-Related Classes
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.

Simulation of Physics

When simulated, physics calculations are done in a number of stages. It can be done in two modes:

  • Single-threaded - all stages go one after another
  • Multi-threaded - some of the operations are performed in parallel.
Physics performance profiler enables real-time tracking of simulation performance. However, it can be used only in a single-threaded mode.

To show the physics performance profiler that reports statistics on different physics simulation aspects, press 1 hotkey three times or type show_profiler  3 in the console.

Rate of Physics Simulation

Unigine physics module performs all its calculations during the render stage of the execution sequence. There are few things to point out about physics.

  • It is simulated with its own fixed FPS, which does not depend on the rendering framerate. (The rendering FPS can also be capped by the physics one).
    Do not set physics framerate too high; otherwise, it can cause rendering lags. If physics takes more than 40  ms, further calculations are skipped.
  • During each tick, a number of calculation iterations can be performed. This includes the full cycle of physics simulation:
    1. flush() from the world script is called
    2. Collision detection is performed
    3. Joints are solved
    There is no point in setting the number of iterations too high. Unigine checks whether the next iteration can be performed within a 40 ms limit, and if not, simply skips it.

Stages of Physics Simulation

Simulation of physics goes through a number of stages when it is updated each iteration. They are as follows.

  1. Physics flush
  2. Broad phase of collision detection
  3. Narrow phase of collision detection
  4. Simulation
  5. Synchronization of physics

In the performance profiler, the total time of physics simulation is displayed by the Physics counter.

1. Physics Flush

  1. Before anything else, a spatial tree is updated. After we have the up-to-date data regarding how all objects with physical bodies are positioned, it would be safe to transform them or calculate collisions.
  2. C++ API Plugin flush() is called, if there is such a function.
  3. Physics module calls the flush() of the world script. Here you can call all functions that handle physics simulation and interactions (and not only that, see the details on flush() usage and limitations).

2. Collision Detection: Broad Phase

After the script-based changes have been made (bodies with their shapes and joints were transformed according to game logic, physics-based callbacks were set, etc.), physics can be simulated.

  1. All objects that have physical bodies are found within the Physical distance. They will be simulated during the current physics tick. Make sure that the physical distance in your Unigine-based application is not too small, because physical interactions outside of it are not calculated, so objects freeze up. (However, even if one body from the island is found within the physical distance, the whole island will be simulated).
    You can force to update nodes that are outside the Physical distance using addUpdateNode() function.
  2. During the broad phase potentially colliding objects are found based on a fast and rough tests.
  3. Unigine physics is deterministic. Bodies, shapes and joints are sorted inside islands. By that, we ensure that contacts will always be solved in the predefined order and visualization of physics in the world is fully repetitive (one one computer).

In the performance profiler you can find:

  • The total time of broad phase is displayed by the PBroad counter.
  • The number of islands is shown by the PIslands counter.
  • The number of bodies is shown by the PBodies counter.
  • The total number of joints is shown by the PJoints counter.

3. Collision Detection: Narrow Phase

During the narrow phase, exact collision tests are performed. In a single-threaded mode (when there are none or one separate physics thread) the simulation continues in the following way.

Collisions are found for bodies inside each island:

  • Shape-Shape collisions - between the physical objects.
  • Shape-Surface collisions - between the physical objects and static surfaces.
The found contact points are represented by their coordinates, normals, depth of shapes penetration, relative velocity (between two bodies), relative friction and restitution. This stage collects all the data required to calculate objects iteration.
If a body is frozen and no contacts are found that would push it out of its frozen state with strong enough impulse, such body is not simulated in the current tick.

Continuous Collision Detection

If a sphere or a capsule participates in the contact with any other shape or surface, continuous collision detection (CCD) is performed. Unigine takes velocities of the body, radius of its shape and calculates what contacts this body will have (during the current physics tick), assuming it continues its current trajectory. So, unlike the simple collision detection, contacts are analyzed not discretely, once per physics tick, but rather found for the whole frame.

In the performance profiler you can find:

  • The total time of this narrow phase stage is displayed by the PNarrow counter.
  • The number of contacts is displayed by the PContacts counter.

4. Simulation

When a collision has been detected, collision response is calculated, so that the bodies would gain new velocities.

  1. Right now bodies are prepared to participate in collisions: their found contacts are cached together with contacts from the previous frame — to ensure that they interact with each other properly.

    In the performance profiler, the time of this stage is displayed by the PUpdate counter.

  2. Collision response for each body is calculated. Based on the gathered contact points data, Unigine computes the impulse a shape gets by collision. Contact points are solved in a pseudo-random order to achieve simulation stability and reproducibility.
  3. When contact responses are calculated, joints constraining relative motion of bodies are solved. Joints as contact points are also solved in the pseudo-random order.
    Within one physics iteration, joints can be solved several times. The high number of joint iterations increase the precision of calculations, as well as computational load.

    In the performance profiler, the total time of both collision response and joint solving stages is displayed by the PResponse counter.

  4. The results of contact and joint solving are accumulated and, finally, are applied to bodies. The coordinates of the bodies change according to their new linear and angular velocities.

    In the performance profiler, the time of this stage is displayed by the PIntegrate counter.

In the performance profiler, the total time of simulation stage is displayed by the PSimulation counter.

5. Synchronization of Physics

Synchronization is the final stage of physics simulation. During the swap() in the Unigine main loop, physics module calls its internal flush() function. Bodies set their calculated transformations to objects. In the next frame, objects will be rendered in their new physics-based positions.

Physics simulation goes in parallel to the actual rendering process. This is the reason calculated physics is visible only in the next following frame.

If visualizer options are enabled, shapes, joints or contacts of non-frozen bodies will be rendered.

Multi-Threaded Physics Simulation

Multi-threaded simulation of physics is run only when there are two or more physics threads (controlled through physics_threaded console variable).

  1. flush() from the world script is always performed in the main physics thread.
  2. After that, Unigine takes advantage of multiple CPUs during the narrow phase and simulation stage.
    • As islands have been created, they can be safely handled in separate threads, because there are no contacts between them.
    • Exact shape-based collisions are found in available threads.
    • Then threaded islands are synchronized in the main physics thread to exchange data about the current contacts and ones from the previous frames. It will ensure proper physical behavior of bodies.
    • From there on, collision response and joints solving are again calculated per island in separate threads.
  3. Before physics is synchronized with the world, the engine waits for all threads to finish their calculations. When thread synchronization happens (during the swap stage of the Unigine main loop), physics is applied to nodes.

Do not use performance profiler in the multi-threaded mode, because the displayed information is not valid.
Last update: 2018-08-10
Build: ()