This page has been translated automatically.
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
Programming
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
Objects-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.

Players

Players are cameras creating viewports into the world. The cameras available in Unigine Editor are:

  •   Player Actor is a player with a rigid physical body that can only walk on the ground.
  •   Player Dummy is a simple viewport into the world that has no physical properties and cannot collide with objects.
  •   Player Persecutor is a free flying camera without a physical body that follows the target node at the specified distance. It can collide with objects but cannot interact with them.
  •   Player Spectator is a free flying camera without a physical body that is used to create a spectator mode. It can collide with objects but cannot push or interact with them.

There are other types of cameras not present in the Editor. These camera types can be controlled by the code.

See Also

Common settings#

For all players listed above, there is the set of common settings. They can be changed on the Node tab of the Parameters window:

Vertical player parameters

Physically-based player parameters

Main Player Defines whether the player is used as the default camera at run time. If several players have this flag enabled, the last one in node hierarchy will be used.

Setting bit masks#

A set of bit masks available for the player:

Viewport Mask Controls rendering of objects, decals, and lights into the camera's viewport.
Reflection Mask Controls rendering of the environment probe's and planar dynamic reflections into the camera's viewport.
Source Mask Specifies what sound channels are played for this camera.
Reverb Mask Specifies what reverberations are played for this camera.

Viewing frustum parameters#

FOV Mode Depending on the FOV Mode, parameters defining a player's viewing frustum differ:
  • Vertical FOV is used for the standard player. In this case, the FOV is set in degrees.
  • Physically-Based Camera is used for the physically-based player with the horizontal FOV. In this case, the FOV is calculated depending on the film gate and focal length of the player according to the formula:

    FOV = 2 * atan(film_gate / (2 * focal_length)) * UNIGINE_RAD2DEG

FOV Degrees The camera's vertical field of view, in degrees.
Focal Length Focal length of the physically-based camera lens, in millimeters. Determines the area that can be seen in the camera's viewport.
Film Gate Horizontal size of the film gate for the physically-based camera with horizontal FOV, in millimeters. Determines the area that can be seen in the camera's viewport.
Near Clipping Distance to the near clipping plane of the player's viewing frustum, in units.
Far Clipping Distance to the far clipping plane of the player's viewing frustum, in units.

Postprocess materials#

In the Post Materials parameter field, you can add postprocess materials to the camera. These materials will be applied after all other postprocesses (such as HDR, DOF, etc.) are applied.

To add a postprocess material, click and select a material from the dialog window that opens.

If you want to use several postprocess materials at the same time, separate their names by a comma with no whitespace, and these materials will be rendered in the order they are positioned in the field.

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