This can be done either via projection matrix or frustum angles. The key idea is that the user explicitly sets a view frustum for a particular viewport.įor stereo rendering, two frustums are required. The same reasoning applies to the mesh policy below.Īs a generic solution for those calibration systems that are not yet supported by nDisplay, a new manual projection policy was introduced. That is why the camera must be set manually via Blueprints or C++ API. This way, any config file can be used with any application. One of the main ideas behind the configuration file is to completely separate the nDisplay topology from the application and its content (Assets). This policy allows you to map a view of any UE4 camera to the nDisplay viewport. Since it is impossible to get a view from a regular Unreal Engine camera or cine camera with nDisplay, the camera policy was introduced. In the example above, we define a projection screen that is located 2 meters ahead of the nDisplay root. id='proj_simple_demo' type='simple' screen='scr_demo' The rectangle ( screen) must be defined in the config file, then referenced in the simple projection policy: This policy requires a rectangle in 3D space to be used to build camera frustum. Simple refers to the standard policy used to render on regular 2D flat displays.

Here are the currently supported projection policies:

After much research, we found the following technologies to help us achieve our goals for scaled displays.

As part of the development strategy for new features, Epic Games is constantly evaluating existing tools that could add functionality to Unreal Engine (UE4).

Dataton watchout 5 manual