Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When this option is on, any textures and extra files (HDR, IOR, IES etc.) needed for the render are sent by the Monitor to all the Nodes. When off, each node takes the files it needs directly from a networked folder which all nodes must have direct access to. In general, it is recommended to leave this option disabled in all cases, unless you are on multi platform networks mixing OSX and non-OSX computers, when path format conflicts can arise. In pure Windows, pure OSX, pure Linux or mixed Windows / Linux networks this option should be left disabled. The differences between having this option on and off are:

  • Send dependencies OFF: For general purposes. In  In this case, any textures/files used in the MXS file must point to a network location, accessible directly by all the nodes. The benefit can be that there are no file transfers at all and the render process starts immediately, but when the render starts all the nodes have to load the MXS file and textures from a network path at the same time. This could create a bottleneck in some cases, if for example 20 nodes are eventually accessing to the same large file simultaneously. However if the file server is fast enough this option can be perfectly valid and you skip the file transfer process time. 
  • Send dependencies ON: Only recommended This option is a must in mixed networks including OSX and non-OSX computers and is generally recommended. Here, the Monitor sends the MXS file and all scene dependencies to Node A. When the transfer finishes, the Monitor starts sending dependencies to Node B, while Node A sends dependencies to Node C and so one. This follows a Peer-to-Peer approach. Moreover, in animations, when most of the dependencies are the same for all the frames the Manager keeps track of which nodes already have each texture so these aren't sent again. When the render starts, each node loads the scene and its files from its local hard drive. This broadcast approach has been designed to prevent some path format conflicts that can arise when there are OSX and non-OSX computers networked together but can also optimize nodes access to textures.

 

Dependencies path

Since we recommend to have Send dependencies unchecked if you are running a network with non OSX computers, you must specify here a UNC path to a networked folder which all nodes have access to. If however Send dependencies is checked, there is no need to specify a path here - Monitor will search for the files using the paths of the textures/files already specified inside the MXS file.

...