...
Although highly recommended, it is not necessary to also put the scene in a networked path; it is enough if the Monitor can access it through the open file dialog. In addition, if the “Send Dependencies” checkbox is on (default), the scene-dependent materials do not need to
be in networked paths, as they are sent from the Monitor to the Rendernodes. This option is faster and has several advantages, but it requires that the Monitor that submitted the job remains on until all nodes start.
However, if the “Send Dependencies” checkbox is off, the scene-dependent materials should be located in a networked path accessible from all the Render Nodes, that will pick them all as they need them. The output image paths should be network paths accessible from the Manager, which is the machine that is going to save the final output there.
This option (“Send Dependencies” disabled) produces a slower file transfer, but it can be useful when you need to switch off the Monitor that submitted the job, or when you have a fast repository server for scenes and textures. You should leave this option checked unless you have a very fast file server. If you wish to restart a network render, the Maxwell network will check if the files are already on the Render Node and will not transfer them again.
...
Once launched, the Manager sends the necessary files to the nodes, that perform the calculations.
When a node finishes a render, it sends the final image to the Manager, that stores it in your desired output folder, and the node gets available for receiving a new job.
You can watch the progress of the work in the display. You can stop the process, remove any job, add more jobs to the queue, and display the images that are being computed by the network using the Monitor interface.
...
| Tip |
|---|
First make some simple tests in your network before attempting a real project or final rendering to ensure that all the Render Nodes can connect and the output is written properly. |
...