Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  • Single job: to make a non-cooperative render queue with each node working on an independent frame.
  • Cooperative job: several computers work on the same image, which will be merged at the end of the process.
  • Animation job: select a scene and the frame range, and the frames will be distributed among the available nodes. Remember that you can also render single frames from the same sequence by using a semi-colon ";" when typing. For example: 1-10;12;20-23 This will render frames 1 through 10, frame 12, and finally frames 20 through 23. Any padding number is allowed.
  • Batch job: This option allows you to select multiple scenes to be rendered. All the scenes are rendered using their own settings and output paths. You can perform changes in the rendering settings (render time, SL, resolution, camera, etc), and this changes are applied to all the scenes added. An interesting feature is that in this mode you can choose the Batch Type, between Cooperative type (all render nodes work together in the same scene before starting with another) or Single type (each render node renders a scene separately).

   

Image Removed

Choose the job type
Center
Wiki Markup
{center}
!network_jobtypes.jpg!

h6. Choose the job type
{center}

Step 5

Select the networked path of the scene to the output files. Set the frame range (for animations), and set the Render Options (Time, Sampling Level). You should also specify an MXI output, not just the image output. It is possible to select bit depth and file format independently for each render channel. They can be saved in the same folder.

   

Wiki Markup
Center

Image Removed

Set the render settings
{center}
!network_wizard.jpg!

h6. Set the render settings
{center}

Choose a networked path to locate the source files of the project (scenes, textures, materials, etc). It is highly recommended to use networked paths for your project files, especially for the output files.

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" “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" “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" “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.

...

Choose the computers you want to work in this job.
   

Image Removed

Assign the nodes you want to work on this job
Center
Wiki Markup
{center}
!network_nodeslist.jpg!

h6. Assign the nodes you want to work on this job
{center}

You can also check the "Use any render node available" checkbox, and the Monitor will use any node in your farm as soon as they get available.
   

Wiki Markup
Center

Image Removed

Use any render node available
{center}
!network_nodeslist_any.jpg!

h6. Use any render node available
{center}

Step 7

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.

...