The false color and the white balance post processes can only be saved in the LDR simulation (PNG file). When the post processed output is in false colors, the false color scale can be saved with the simulation :

• Using the engine overlay, the scale is saved with the simulation if the "Display Scale" option is selected on the optical instrument component (section Post Pipeline/False Colors),

• Using the engine view, the scale is saved with the simulation if the option "Export false color scale with renders" is selected in the UVR preferences, section Engine Interface.

You can save Predict Engine simulations for different configurations of the scene and a set of camera transforms using the Batch Renderer window. Via this interface, you can select a camera, define a set of transforms for it, and create different scene configurations with a combination of pickers from the scene.

The Batch Renderer is available via the menu "PredictSuite/Engine/Batch Renderer".

The first step defines which optical instrument in the scene must be rendered and in what position(s). All Cameras and Physical Sensors can be rendered, even if they are disabled in the Hierarchy.

The scene can be rendered for a set of Transforms. The Transforms can be defined by :

• A Single Position : only one Transform is rendered, the Transform of the selected optical instrument,

• A Transform Picker : the scene will be rendered for each Transform listed in the picker (see the Pickers section for more details). It is also possible to compute Transforms linearly interpolated between the given Transforms to create animation frames,

• An Animation Clip : the scene will be rendered for each frame of the clip (only the Transform properties of the clip will be evaluated). A Preview button enables you to preview the animation in the scene view,

• A Spinner : the optical component will be placed on a sphere defined by its origin O and its radius (or distance to the origin). The inclination (theta) and azimuth (phi) of the position P are regularly spaced in the given ranges, every given step. In the example here against the Transform will be computed with theta in {50,70,90} and phi in {0,180,360}

The third step defines how the output simulations should be named. Each file name is the combination of different parameters. The parameters you can combine are :

• Scene : the scene name,

• Camera : the selected optical instrument name,

• Camera Transform ID : the Transform ID, each Transform has its own unique ID,

• Setup ID : the configuration ID, each configuration has its own unique ID,

• Frame ID : the frame ID, each combination {Transform + Configuration} has its own unique ID,

• Theta/Phi : when the Transforms are defined using a Spinner, the inclination and azimuth,

• Clip Name : when the Transforms are defined using an Animation Clip, the name of the clip,

• {Picker} ({Picker type}) : for this picker, the name of the selected option (name of the material, name of the GameObject, name of the skybox,... depending on the picker type).

Each frame file name must be unique. As long as you have not selected a combination of elements that can differentiate each frame, the warning here against will be displayed and you will not be able to proceed to the next step.

A file name will be unique if it contains the frame ID or enough parameters to differentiate the configuration (configuration ID, pickers options) and the Transform (Transform ID, theta/phi, Camera Transform picker options) for this frame.

The fourth step defines the format of the output simulations and their resolution. The available formats are the same as when exporting the simulation from Unity (see section above).

The LDR processed frames (PNG files) can also be compiled to a movie.

The Predict Engine is a path tracer, this algorithm computes the illuminance incoming at every single point on the surface of the objects of a 3D scene. This calculation takes time and will be more and more accurate, less and less noisy, with an increasing amount of render time. The quality of a simulation can be defined by the amount of time the simulation was given to render, or by the average number of samples that were run for each pixel.

When computing a batch of frames, a completion criteria must be defined to know when a frame is ready and the renderer can move on to the next frame. The completion criteria is either defined in seconds (total render time) or in samples per pixel (SPP, average number of samples for each pixel).

It is also possible to save intermediate simulations : while the simulation is being rendered, intermediate frames are saved to see the evolution of the simulation. Frames can be saved every n SPP or every n seconds.