Houdini

Parent Previous Next


Render Licenses


Rendering with Houdini requires a full or an "Engine" license per client.


If you use Mantra, then it require a Mantra render license.


Please enter the number of your Houdini licenses in rrConfig to verify that RR does not start more instances that you have licenses.




Takes


You can use takes in Houdini. 

Do not forget to use $ACTIVETAKE in your file names if you want to use one output node for multiple takes.


Note: If you set your mantra node to a take, then the rrSubmitter will load this mantra node with this take.

If you have not set a specific take (set to "current"), the rrSubmitter creates a job for each take.


Example scene:

www.RoyalRender.de/download/web/houdini_take.zip 






Python Script Execution


The render config file RR\render_apps\_config\3D06__Houdini_Python.cfg executes a python script with Houdini Hython.
It uses the custom job variable "CustomScript" for the name of the script file to execute.



How to submit


Test run:
For a test you can try this:




Production:

We recommend to create a submission .xml file.

Or you can pass all required arguments as commandline flags for the rrSubmitter/rrSubmitterconsole.
In this case you have to start the rrSubmitter or rrSubmitterconsole with the commandline flag -NoAutoSceneRead.

Please see the rrHelp section rrSubmitterconsole for instructions for both submission types.





Pass Arguments to Script


You have 3 options to get arguments into the script:

  1. Some scripts support 3 custom arguments <CustomA>,<CustomB>,<CustomC>.
    See Custom Job Variables 

  2. Set environment variables and read them in your script.
    Please see rrHelp section Customization/Render Environment

  3. Use the rrJob setting AdditionalCommandlineParam.
    In this case use the Submitter option "AdditionalCommandlineParam=0~0~Myflag1 Moreflags EvenMoreFlags".
    or set it via the submitter or rrControl UI (you might need to press the Show All button).
    Note: This option is limited to 250 characters, NON-unicode.



Custom Icon

If you use some scripts very often, we recommend to override the default icon as well.

The icon has to be a png, 14 pixel high and 14-28 pixel wide, located in RR\render_apps\_config\

XML submission: <OverrideIcon> NoPathFileName.png </OverrideIcon>

Commandline:    -OverrideIcon  NoPathFileName.png



Arnold (HtoA)



Redshift




Exporting .rs files without a GPU:

It is possible to export .rs files on a machine that does not have any GPU installed.

Redshift does not need a GPU for writing .rs files, but the Redshift plugin requires the NVidia libraries for its startup.

You have to copy the NVidia libs from a machine with a GPU into the Redshift/bin folder.

On Windows, the libs are located here:  C:\Windows\System32\nv*.dll 


Note: If you use the same Redshift folder for rendering, then you should ensure that all GPU machines use the same NVidia driver version as the one you copied to /bin.



Pixars Renderman


* Renderman ProServer source path is set to ....\render_apps\renderer_exe\houdini\win_x64\RendermanProServer-.....
* Renderman Houdini source path is set to ....\render_apps\renderer_exe\houdini\win_x64\RendermanForHoudini-.....


Example:



ROP setup/artist notes:


No output via RR?
We have seen that Renderman 23.4 does not print any error message in batch render.  Example: "Camera does not exist".

But you can change your ROP to "Render current frame" and try render inside the Houdini UI.

In this case the node displays a small error icon. Just hover over the ROP with your mouse and click on the error icon that appears on the left side of the node to see the error message



Renderman not loaded?
There have been cases in which Pixars Renderman was installed on the artists workstation, but the artist was using the Renderman ROP version that was shipped with Houdini.
This is an example with Houdini 18 and Renderman v23. As long as Houdini does not update the included Renderman version, you can see the difference in the logo of the ROP: