In order to run your application with Multipipe capabilities, you have to define a typical ScaleViz configuration file defining the “pipes” properties. For example, the following configuration defines a 4 pipes tiled scene rendering.
Figure 3.12. ScaleViz configuration file
The following defines a 2 pipes depth compositing scene rendering:
ScaleVizConfig {
name "4 Pipes"
DepthComposer
{
display “:0.0”
}
DepthComposer
{
display “:0.1”
}
DepthComposer
{
display “:1.0”
}
DepthComposer
{
display “:1.1”
}
}
|
 |
Notes:
These configurations are quite similar to a cluster tile and depth compositing configuration file. The single difference is that the SoMasterConfig SoMasterConfig SoMasterConfig node is not used.
On UNIX/Linux platforms, set the display fields of the TileComposer/DepthComposer nodes to the ids of the displays where the GPUs are connected. (You may need to configure your X Server in order to get independent displays. A Xinerama desktop configuration using several GPUs, does not allow using full MultiPipe capabilities, since only one display exists (:0.0)
On the Windows platform, display specification is automatically managed by ScaleViz. It is not necessary to set the display field. However if you need to force the use of a certain GPU, the display field can be specified using the syntax “:0” ( ‘:’ followed by an integer identifier in the range [0, GPU count – 1] ). Note: If the number of actual GPUs is less than the number of TileComposer nodes, a warning is displayed but rendering will still be done. In this case some GPUs will render more than one TileComposer.
By default, on QuadroPlex plartforms, ScaleViz uses the NVIDIA CompleX library (if available) to do depth compositing. But it is possible to force ScaleViz to not use CompleX, by defining the SCALEVIZ_MT_RENDERMODE environment variable to MT instead of MT_NVCOMPLEX (the default).
Multipipe rendering mode can be enabled or disabled dynamically through the common ScaleViz connection/disconnection process.