modo Plug-in Guide
- 1 modo Plug-in Guide
You can submit jobs from within modo by running SubmitModoToDeadline.pl script, or you can submit them from the Monitor.
To submit from within modo, follow these steps:
- Under the system menu, choose Run Script
- Choose the SubmitModoToDeadline.pl script from [Repository]\clientSetup\Modo\
- Alternatively, you can also copy this script to your local machine and run it from there
- modo File: The scene file to render.
- Pass Group: The pass group to render, or blank to not render a pass group. This option is only available for modo 6xx or later.
- Render Threads: The number of render threads to use. Specify 0 to use automatic render threads.
- Version: The version of modo to render with.
- Build To Force: You can force 32 or 64 bit rendering with this option.
- Output Folder: Specify an output folder. Note that specifying the output is optional unless you want to use tile rendering.
- Output File Prefix: If specifying an output folder, specify the prefix for the output file name (extension is not required).
- Output Format: If specifying an output folder, specify the format of the output images.
- Tile Rendering Options: Setup a modo tile rendering job. Note that this requires you to override the output file.
Network Rendering Considerations
This Article provides some useful information for setting up modo for network rendering.
Cross-Platform Rendering Considerations
In order to perform cross-platform rendering with modo, you must setup Mapped Paths so that Deadline can swap out the Scene and Output file paths where appropriate. You can access the Mapped Paths Setup in the Monitor while in super user mode by selecting Tools -> Configure Repository. You'll find the Mapped Paths Setup in the list on the left.
You must also ensure that your modo project file is on a network shared location, and that any footage or assets that the project uses is in the same folder. Then when you submit the job to Deadline, you must make sure that the option to submit the scene file with the job is disabled. If you leave it enabled, the scene file will be copied to and loaded from the Slave's local machine, and thus won't be able to find the footage.
You can configure the Mod plug-in settings from the Deadline Monitor. While in super user mode, select Tools -> Plugins Configuration and select the modo plug-in from the list on the left. To get a description of each setting, simply hover the mouse cursor over a setting and a tool tip will be displayed.
- Is modo supported by Deadline?
- Yes, modo 302 and later is supported.
- When rendering with modo on Mac OSX, the Slave icon in the Dock changes to the modo icon, and the render gets stuck.
- This is a known problem that can occur when the Slave application is launched by double-clicking it in Finder. There are a few known workarounds:
- Start the Launcher application, and launch the Slave from the Launcher's Launch menu.
- Launch the slave from the terminal by simply running 'deadlineslave' or 'deadlinelauncher -slave'.
- Use 'modo' as the render executable instead of 'modo_cl'.
- When tile rendering, each tile is rendered, but there is image data in the "unrendered" region of each tile.
- This happens when there is a cached image in the modo frame buffer. Open up modo on the offending render node(s) and delete all cached images to fix the problem.
Plugin Error Messages
This is a collection of known modo error messages and their meanings, as well as possible solutions. We want to keep this list as up to date as possible, so if you run into an error message that isn't listed here, please email Deadline Support and let us know.
Currently, no error messages have been reported for this plug-in.