How to Count Seats and Channels

The image demonstrates two types of arrangement. Simulation 1 requires only 1 VR Channel to run the application, and there's no network connection. A complex network of Simulations 2-4 and one PC with two monitors has 10 running PCs (instances of the application) in total, and therefore requires 10 channels. Considering the network connection available, these 10 are VR Channels.

Depending on your project's requirements and the final setup, your application may have several different views to render, such as:

• Out-the-window view for the cockpit having 4 windows each represented by a separate monitor
• Electro-Optical/Infra-red (EO/IR) sensor
• Radar
• Dashboard with simple gauges and instruments
• Rearview mirror
• Instructor Operator Station (IOS)

But how many channels is that?

Each runtime (instance of the released application) that requires a separate computer to render a certain view or a part of a view (in case of multi-monitor/multi-projector setup) requires its own individual Channel. If you use the Wall plugin, then one instance is one PC, on which the application with this plugin is running (not the number of monitors used).

Simply put, we should define how many separate views we want to have. For example, a simple plane simulator with a three-screen out-the-cabin view, with a dashboard, radar, and an IOS (Instructor Operator Station) will be implemented by running 6 application instances. For a rear-view mirror or a simple additional camera producing a low-resolution image no additional channel is instance - that is implemented by an additional camera with a viewport. Thus, for such a setup we require 6 channels. And these channels should be IG Channels, as synchronization between them is required to render coherent images.

Of course, it is possible to combine several views and render them on a single PC, but only if the rendering load won't get too heavy (e.g. sensors and gauges displaying data rendered in low resolution or a rearview mirror rendered as a picture-in-picture). If rendering load becomes too high, a single computer might become unable to provide the required image at the required framerate, in this case the channel has to be split. An attempt to save on additional channels may result in performance and quality degradation, so please be aware that choosing an appropriate number of channels is essential for the successful implementation of your project. For example, if the truck simulator setup has four 4K monitors (two for the windshield and one for each side window) that'll end up with 16K pixels to be rendered, which might be too much for a single channel (a single PC with the Wall plugin used).

Decide on your setup, define what and how you plan to visualize - count all instances with significant rendering load (generation of high-resolution images for out-the-window views, high-resolution radar, and so on). Each of these instances should be rendered by a separate computer (otherwise too heavy load may lead to lags, which is totally unacceptable for a simulator).

Seats are required for developers and can be compared with an office chair for simplicity: if two persons work in different shifts they can share the same workplace.

Some developers (such as artists) only need the Editor for work: they just assemble scenes and don't develop any logic. For such cases, there's Editor Seat, an option that allows working in the Editor.

To use both Developer Seats and Editor Seats, SDK Browser should be installed and running on the PC, and the corresponding version of SDK should be downloaded and activated.

Thus, if you team has 1 artist and 3 programmers, one of which is working a night-shift, 2 Developer Seats and 1 Editor Seat might be enough for you.

Testing the Application

#

Let us review some typical examples of simulator setups and count channels for them.

Railway Simulator

#

Simple Helicopter Simulator

#

VR Classroom

#