This plugin enables Prism to submit render and other jobs to the AWS Deadline rendermanager.
Jobs are usually submitted from the render or export states in the Prism State Manager.
Different Prism plugins like Houdini or USD can have additional options available for job submissions. See the plugin pages for more details.
Configuring Deadline to run Python Jobs¶
Prism submits Python jobs to Deadline in different situations, for example to update master versions (if enabled in the projects settings) or when rendering using Redshift or 3Delight scenedescriptions. Prism was updated to Python 3.9 in version Beta 12. This causes that Python Deadline jobs will be submitted as Python 3.9 jobs. Unfortunately Deadline still doesn’t support Python 3.9 jobs and will create errors on these Python jobs. These errors can be found in the log, which can be viewed in the “Job Reports” panel in the Deadline Monitor.
To add support for Python 3.9 to the Python Deadline plugin, this file in the Deadline repository needs to be modified: \plugins\Python\Python.param
This file contains a section for each Python version. In a text editor a section for Python 3.9 can be added to the bottom of the file:
[Python_Executable_3_9] Type=multilinemultifilename Label=Python 3.9 Executable Category=Python Executables CategoryOrder=0 Index=13 Default=C:\Python39\python.exe;/usr/bin/python3;/usr/bin/python Description=The path to the Python executable. Enter alternative paths on separate lines.
A restart of the Deadline Monitor is needed after editing and saving this file. In the “Tools” menu in the main menu bar in the Deadline Monitor the “Super User Mode” needs to be enabled. Then in the same menu the option “Configure Plugins…” will show up. In the new window that opens select the Python plugin and scroll down to the “Python 3.9 Executable”. Here you have to enter the path of a Python 3.9 executable. That can be from a custom Python installation or the path to the Python executable included in Prism.
Confirm the window and now the Python Deadline jobs will be executed without errors.
Configuring Deadline to run jobs with unsupported Houdini versions¶
When submitting jobs from Houdini to Deadline it is important to check if the installed Deadline version supports the used Houdini version. This can be done by consulting the official Deadline changelog here or checking the content of the \plugins\Houdini\Houdini.param file in the Deadline repository.
When submitting jobs from an unsupported Houdini version, the jobs will error and in the “Job Reports” panel you will see the following error message:
In some cases it can help to update Deadline to the latest version. But after a new Houdini version gets released it can take months until Deadline gets updated to officially support that Houdini version. Waiting months for a new Deadline version is usually not an option and luckily there is a simple way to add support for any new Houdini version.
Open this file from the Deadline repository in a text editor: \plugins\Houdini\Houdini.param For example to add support for Houdini 19.5, the following section can be added to the bottom of the file.
[Houdini19_5_Hython_Executable] Label=Houdini 19.5 Hython Executable Category=Render Executables CategoryOrder=0 Type=multilinemultifilename Index=12 Default=C:\Program Files\Side Effects Software\Houdini 19.5.000\bin\Hython.exe;/Applications/Houdini/Houdini19.5.000/Frameworks/Houdini.framework/Versions/19.5.000/Resources/bin/hython;/opt/hfs19.5/bin/hython Description=The path to the hython executable. It can be found in the Houdini bin folder.
A restart of the Deadline Monitor is needed after editing and saving this file. In the “Tools” menu in the main menu bar in the Deadline Monitor the “Super User Mode” needs to be enabled. Then in the same menu the option “Configure Plugins…” will show up. In the new window that opens select the Houdini plugin and scroll down to the “Houdini 19.5 Hython Executable”. Here you have to enter the path of a Hython executable, which is usually in the bin folder of your Houdini installation.
Confirm the window and now the Houdini Deadline jobs will be executed without errors.
While the solution in the previous section is recommended, there is also an alternative solution without modifying a file in the Deadline repository.
The environment variable
PRISM_DEADLINE_HOUDINI_VERSION can be set to a Houdini version like “18.5” or “19.0”. If that environment variable is set at the time of the job submission in Houdini, this version will be set in the job settings and Deadline will try to render that job using this Houdini version. By doing this, Deadline will render the job using a supported Houdini version like 18.5 even though it was submitted from an unsupported version like 19.5. As a last step we need to point the Houdini 18.5 configuration in Deadline to the Houdini 19.5 executable so that Deadline actually uses the executable of our Houdini 19.5 installation.
Assuming Houdini 19.5 is installed and Deadline 10.1, which supports officially Houdini versions up until 19.0.
In the Prism User Settings in the “Environment” tab we can set the variable
PRISM_DEADLINE_HOUDINI_VERSION to “18.5”.
Now we can submit our job from Houdini to Deadline for example using the Prism LOP File Cache HDA.
Deadline will try to render this job using Houdini 18.5 and will error because we only have Houdini 19.5 installed.
In the Deadline Monitor we can enable the “Super User Mode” in the “Tools” menu. Then we can open the “Configure Plugins…” window from the “Tools” menu. When selecting the Houdini plugin we can see the executable configuration for all supported Houdini versions. In the “Houdini 18.5 Hython Executable” field we add the path to the bin/hython.exe in our Houdini 19.5 folder.
Now we can save the configuration and Deadline will render the job successfully.
The environment variable
PRISM_DEADLINE_HOUDINI_VERSION can be set in the Windows system settings of the workstation or in the Prism User or Prism Project Settings.