World Management

There is a number of optimization techniques and practices relating to world management. They are used to decrease the rendering load without losing much of the image quality.

Smooth alpha-blended levels of details (LODs) are used to decrease geometry complexity of 3D objects, when these objects move away from the camera, making it possible to lighten the load on the renderer.

Lower-detailed meshes are manually created by artists and then exported into Unigine as different surfaces of the same mesh. When rendering the virtual world, these surfaces become visible one by one smoothly fading into each other: starting from the high-poly mesh and ending up with low-poly one seen from far away. Surface LODs are adjusted on the Surfaces tab of Node settings.

LODs can be switched abruptly or smoothly faded into one another using alpha dithering, if necessary.

Within visible distance

Within fade distance

Suppose, we have two LODs: high-poly surface_lod_0 and low-poly surface_lod_1, and we need to organize smooth transition between these two LODs.

1. We want the switching distance at 50 units. For that, we need to "dock" visible distances of surfaces to each other:
   • Our first LOD surface surface_lod_0 should be be always present when the camera is close to the object. So, the minimum visible distance is set to -inf. And 50 units from the camera will be the maximum visible distance for it.
   • Directly following it, comes the second LOD surface surface_lod_1. It is visible from 50 units (which is the minimum visible distance) - and up to infinity (the maximum visible distance = inf).
2. Now the LOds are switched but sharply rather then smoothly. To be smoothly blended, the symmetrical fade-out (for the 1st LOD) and fade-in (for the 2nd LOD) distances are set. Let's say, the fading region should be 5 units.
   • For the 1st LOD to fade-out, its maximum fade distance is set to 5.
   • For the 2nd LOD to fade-in, its minimum fade distance is also set to 5.

In the result, the LODs will be changed in the following manner:

See also: Tutorial how to export and set up LODs

Reference Object

There is one more LOD-related parameters: reference object to measure the distance to switch LODs. It specifies, whether the distances should be measured to the surface itself or to any of the surfaces or nodes up the hierarchy branch. There are two reference objects for each surface:

Min Parent

Minimum parent is a reference object to measure the minimum visible distance from: 0 means the surface itself 1 means the reference object is found one level up in the hierarchy: First, the surface hierarchy is stepped up (if any). Then the hierarchy of nodes is considered. For example, if the surface has no parent surfaces, 1 would mean the object it belongs to. As for higher numbers, they will simply move the reference object up through all the surface parents and then all the node parents.

Max Parent

Maximum parent is a reference object to measure the maximum visible distance from. The same principle is used to count it.

Let's take a model of the house, for example. When the camera is close by, the high-poly detail surfaces are seen, such as the door arch, stone corners, round window and roof tiles. When we move away, all these surfaces should be simultaneously changed by one united low-poly LOD surface.

Notice

Merging several surfaces into one reduces the number of objects to draw, hence, it reduces the number of DIP requests and speeds up rendering.

High-poly model

Low-poly model to be used as distant LOD

The problem is, all this detail surfaces have different bounding boxes. So if their distances are checked for themselves (0 as min and max parents), we can have a situation when LODs of different parts of the house are turned on (or off) unequally, because their bounding boxes will be closer to the camera. This may cause z-fighting artifacts. Here the distant corner has not yet switched to a more detailed LOD, while the close one is drawn twice: as a high-poly corner LOD and at the same time the united low-poly house LOD.

Measuring LODs distance to surfaces can cause artifacts: two LODs switched on at once

If we set a bounding box of the whole house to be a reference object (min and max parent to 1), all surfaces will switch on simultaneously no matter what side we approach the house from.

One more option is to use different reference objects when check. For example, the lower bound (minimum distance) is checked for the surface itself, and the upper bound (maximum distance) is checked for the parent. This may sound complicated, so take a look at the pictures below. The first picture shows a ring, which is split into surfaces according to levels of details.

Levels of details of a ring. Surfaces on the left are parents to surfaces on the right

Here, surfaces from the rightmost column will be displayed, when the camera is very close to them. The leftmost surfaces will be displayed, when the camera is very far from them. Merging of several surfaces into one reduces the number of objects to draw, hence, reduces the number of DIP requests and speeds up rendering.

Note that all of the minimum distances here are measured to the surface itself, but almost all of the maximum distances are measured to another reference object, a parent. One more picture will help you to understand, why it is so.

An example of using measurements of distances to different reference objects.

A star is the camera; it doesn't matter now what exactly the camera will be looking at. On both images, required surfaces are drawn according to the camera position and distances from the camera to the corresponding reference objects. For example, on the left image, the upper left part of the ring is a single surface, the upper right part is split in two separate surfaces, and the bottom part is also a single surface. On the right image, the whole upper part is divided into the smallest possible sectors.

Here, distances are measured to different reference objects to properly "turn off" smaller single sectors and display a larger sector instead. The maximum distance is calculated to the parent sector, because the distances to the neighboring subsectors may differ too much. The minimum distance is calculated to the current sector, because we need to show it, if the camera is too close to it.

Often, it is enough to create and display to the user only a part of an artificial world, in a form of a labyrinth-like series of rooms and passages between them. Parts of open space, if they are present and do not spread at infinity (if they are confined areas), can also be considered "rooms". These limitations make such world ideal for being viewed as a set of sectors and portals.

The whole space is partitioned into convex areas called sectors ("rooms"). If there is some opening-a-door or a window—between two adjacent sectors, through which one sector can be partially seen from another, this opening is called a portal. The sectors and portals help the renderer to determine, which areas and objects are visible from any given point in the world. Also, if a neighboring sector is seen through a portal, this portal is used as a viewing frustum for the area it leads to, allowing viewing frustum culling.

The techniques that are appropriate for indoor scenes, are not efficient when it comes to managing the vast landscapes. The rendering speed directly depends on the number of entities and polygons drawn in the scene, as well as physic computed for the objects, the count of which is usually very high in the outdoor scenes. So the main goal of the managing is to render only the regions that are seen while culling all the rest. If the world cannot be narrowed down to a set of closed areas, the approach called space partitioning becomes relevant.

In Unigine the space partitioning is implemented using the adaptive axis-aligned BSP trees.

A binary space partition is a method for dividing the scene along the axes into the regions that are dealt with individually and thus are more easily manageable. BSP tree is a hierarchical structure obtained by division and organizing all the scene data. The adaptive behavior allows to optimize the BSP algorithm by adjusting the regions size to the processed geometry and entity distribution in the world.

The BSP tree is built in the following way:

1. First of all, the root node is created. It is done by simply spanning an axis-aligned bounding box over the whole scene.
2. Then in each step, a BSP tree recursively subdivides the space in two regions by a partitioning plane that is perpendicular to one of the three major axes. As a result, two tree nodes are created, from each of which the branches are further descended until the whole scene geometry is represented. Each of these tree nodes are again enclosed in the axis-aligned bounding boxes that are easily tested against the view frustum.
3. The subdivision is stopped when the level with required number of editor nodes is reached. However, nodes can be also positioned higher in the tree hierarchy, if the partitioning plane splits them in two. It happens often when dealing with big and extensive nodes, like sky or huge buildings mesh. In this case, the editor nodes stays on level where it is not split, and does not slide down the tree hierarchy.
4. At rendering time, the engine loops through the BSP nodes to determine whether their bounding boxes are inside the viewing frustum. For each child that passes this tests, the same action is repeated until hitting a leaf node or a node that is not visible through the camera. For the visible regions all the necessary calculations are performed, while the rest of the scene, i.e. objects, their lighting and physics interactions with each other, is disregarded.
5. Each time the editor nodes are added, removed from the world, or change the status to collider or clutter objects, the tree is regenerated on the fly. If the frame does not bring any changes, the tree remains the same. This quality makes adaptive BSP efficient not only when rendering static geometry, but also for handling dynamic objects.

To provide effective management of the scene on the one hand and good tree balancing on the other, the separate trees are created for different editor node types:

• World tree handles all the sectors, portals, occluders, triggers and clusters.
• Objects tree includes all the objects except for the ones with collider and clutter flags.
• Collider objects form a separate tree to facilitate collision detection and avoid the worst case scenario of testing all the objects against all other objects. It is clear, that objects can intersect only if they are situated and overlap in the same region of the scene. This tree allows to drastically reduce the number of pair-wise tests and accelerate the calculation.
• Clutter objects are also separated as they are intended to be used in great numbers, which can disturb the balance of the main object tree.
• Light tree handles all the light sources.
• Decal tree handles the decals.
• Player tree handles all the types of players.
• Physical node tree handles all physical forces.
• Sound tree handles all the sound sources.

Mesh Partitioning

When the human eye views a scene, objects in the distance appear smaller than objects close by - this is known as perspective. While orthographic projection ignores this effect to allow accurate measurements, perspective definition shows distant objects as smaller to provide additional realism.

A viewing frustum (or a view frustum) is a field of view of the virtual camera for the perspective projection; in other words, it is the part of the world space that is seen on the screen. Its exact shape depends on the camera being simulated, but often it is simply a frustum of a rectangular pyramid. The planes of the viewing frustum that are parallel to the screen are called the near plane and the far plane.

As the field of view of the camera is not infinite, there are objects that do not get inside it. For example, objects that are closer to the viewer than the near plane will not be visible. The same is true for the objects beyond the far plane, if it is not placed at infinity, or for the objects cut off by the side faces. As such objects are invisible anyway, one can skip their drawing. The process of discarding unseen objects is called viewing frustum culling.

When the human eye looks at a scene, objects in the distance appear smaller than objects close by. Orthographic projection ignores this effect to allow the creation of to-scale drawings for construction and engineering.

With an orthographic projection, the viewing volume is a rectangular parallelepiped, or more informally, a box. Unlike perspective projection, the size of the viewing volume doesn't change from one end to the other, so distance from the camera doesn't affect how large an object appears.

Another popular practice is to remove objects that are completely hidden by other objects, for example, there is no need to draw a room behind a blank wall or flowers behind an entirely opaque fence. This technique is called occlusion culling. Portals and sectors and potentially visible sets are particular cases of occlusion culling. The former are described above. The latter divide the space in a bunch of regions, with each region containing a set of polygons that can be visible from anywhere inside this region. Then, in real-time, the renderer simply looks up the pre-computed set given the view position. This technique is usually used to speed up binary space partitioning.

Multi-threaded update of nodes (if enabled via world_threaded console command) can substantially increase performance. For example, this can be very handy when a big number of particle systems are rendered in the world.

• All nodes that have one root in the nodes hierarchy are updated in one thread. To parallel the jobs on nodes update, make sure that they do not use the same parent.
• Each Node Reference is handled as a root node without any parents (regardless of their position in node hierarchy). For example, this means that particle systems contained in node references are always optimized for multi-threaded update.