...
While rendering, all involved nodes will render the same frame with a different starting “seed”. They will get almost identical images of the same scene, only the noise distribution is different between them (due the different random seed they used). When the job is finished, the Manager will collect these results and merge them into a single output file, resulting in one cleaner image.
Preview a cooperative job
It is possible to preview Cooperative jobs while rendering by selecting the job tree and pressing the Preview button. The Monitor will send a request to the Manager for merging the contribution of all the nodes and display the resulting image in the Preview window as soon as the Manager collects, merges and sends the image to the Monitor.
Merging Manually
If the network fails or crashes at some point and the merging of MXI files is not completed (you can check the Monitor nodes and manager for error messages), you can manually merge the cooperative MXI files created during the render process. All the Render Nodes save the current MXI file in their temp folder (accessible through File>Open temp folder from each Node). The Manager also stores all the MXI files from the nodes in its temp folder, creating a subfolder for each job so it is easier to find the set of MXI files you are looking for and merge them manually.
In order to make a cooperative render work, each MXI file must have a different starting “seed” so that each render has a slightly different noise pattern. This random seed value is given automatically by the -idcpu command; you should not specify it yourself.
...
| Tip |
|---|
Always check the logs of the Manager and Nodes first of all if something went wrong during a network render. The Monitor logs are the least informative. You can set the level of logging from File>Preferences in Manager/Node |