User Manual

Table Of Contents
To disable Verbose mode:
Choose Misc > Verbose Logging from the Render Manager’s menu bar.
Using Third-Party Render Managers with Fusion Studio
You can make use of third-party render manager software to control network rendering. This
allows for efficient sharing of your computer resources between the many applications that may
make use of them. Examples of such managers are Smedge from Uberware LLC, Rush from
Seriss, and Deadline from GetRender. Generally, these render managers use a command line
renderer. By default, Fusion’s Render Nodes operate as a service to the Fusion internal render
manager. However, you can also run the Render Nodes via the command line for third-party
render managers.
Keep in mind that using a third-party render manager will prevent the use of some of Fusion’s
network rendering features, such as the ability to create network rendered Flipbook Previews
and disk caches.
Command Line Rendering
For studios using third-party render farm managers like Deadline, Smedge, or Rush, the Fusion
Render Node can be called via command line passing arguments and file paths. In this
Windows example, a Render Node is called to load a composition called exampleV001, and
render 10 frames:
//pathtoRN/FusionRenderNode.exe //pathtoProject/exampleV001.comp -render -start
101 -end 110 -quit
This would start up, render frames from 101 to 110, and then quit.
The following table lists additional command line features.
Command Description
“Fusion Server -i
Installs the license server as a service or daemon,
launching it on startup before user login.
Fusion Server -S” (capital S)
Causes the Fusion Server to run persistently in the
background, until force-quit.
<filename.comp>
Full path and comp name, like
/storage/project/episode/shot/filename.comp.
-render
Tells the Render Node to render.
-frames <frameset>
Passes a series of frame ranges to be renderede.g.,
101..110,120,121,130..150.
-start <frame>
Sets the start frame of the render.
-end <frame>
Sets the last frame of the render.
-step <step>
Normally set to 1, step skip frames for rendering.
Forinstance, 2 would render every second frame
-quit
Causes the Render Node to quit after the render is
complete.
-join <host>
Prompts the node to connect to a manager at
<hostname,IP>, and (re)join any ongoing renders.
Chapter – 55 Rendering Using Saver Nodes 1054