Graphics Reference
In-Depth Information
drive r: . For Linux machines, you should mount the share at /render , with full read, write, and execute
permissions. For OS X, try to mount the share at /Volumes/farmerjoe , once again with the ability to read,
write, and execute. Navigate the command line to that directory and execute the slave OS's specifi c command:
For Windows: farmerjoe.exe --slave
For OS X: ./Farmerjoe.osx --slave
For Linux: ./Farmerjoe.linux ---slave
Just so everyone knows where they stand, the terminal will display something like:
# Welcome 9
YOU ARE NOW A SLAVE
And that's it for setting up a slave. You just need to mount the share and execute the “farmerjoe.xyz --slave”
command. As long as the Blender binaries have been placed in the proper directories, you are ready to create
and submit a job.
While Farmerjoe comes with an integrated Python job submission tool, using it requires you to run an
instance of Blender, open the BLEND fi le in question, run a Python script, make some settings and hit “sub-
mit.” It also limits you to using certain formats when saving renders, none of which are OpenEXR. Instead,
jobs can be submitted from a command line.
Within the master farmerjoe directory, create a new directory called jobs. This jobs directory becomes the
base directory for your animation project. All asset directories that we prepared to move in the previous sec-
tions go here. So you end up with a directory structure like the one shown in Figure 15.69, each directory
populated with the models, textures, and animation shots you have created so far.
Figure 15.69 All of your hard work, ready to be rendered
Search WWH ::




Custom Search