Page tree

Contents

  • RenderMan for Houdini (RfH) 23 currently only provides support for the following production Houdini versions:
    • RenderMan 23.0 and 23.1
      • 17.0.506
      • 17.5.360
      • 18.0.287
    • RenderMan 23.2
      • 17.0.506
      • 17.5.360, 17.5.460
      • 18.0.391
  • Rendering with RenderMan will not operate on Houdini Apprentice editions, see Side FX's website for options that allow Third Party Rendering
  • Houdini Indie is only compatible with version 17.5.210 or higher

The environment variable for RfH must be listed first in the houdini.env file. (Windows requires a semi-colon) For example:

HOUDINI_PATH=$RFHTREE/17.5:&


RenderMan for Houdini 23 with Solaris now requires an additional line in the configuration file:

RMAN_PROCEDURALPATH = $RFHTREE/18.0/openvdb:&


RenderMan for Houdini 23 on Windows now requires an additional line in the configuration file:

PATH=$RMANTREE\bin;&


Additional instructions and details are found below in this document.

RenderMan for Houdini is installed using the RenderMan Installer, which manages the downloading, installation and licensing of RenderMan Pro Server (the actual renderer) along with all bridge products.


After installing the plugin, Houdini requires a modification to the Houdini environment in your home directory to load the RenderMan plugin. Houdini specific environment variables can also be set in the houdini.env, found in the following locations for each operating system:

Windows: %HOME%\Documents\houdiniX.X\houdini.env
Mac: ~/Library/Preferences/houdini/YY.Y/houdini.env
Linux: ~/houdiniYY.Y/houdini.env

NOTE: When you run a new version of Houdini for the first time, you may have to run it twice before the houdini.env files appear in the locations mentioned above, once created you can add the lines mentioned below.


You need to edit the houdini.env file with a text editor and place the following lines below in that file before you start Houdini. This only has to be done once for each new major version of Houdini that is being used.

EXAMPLES

For example on Linux, one would edit this file in: $HOME/houdini18.0/houdini.env:

RMANTREE=/opt/pixar/RenderManProServer-23.0
RFHTREE=/opt/pixar/RenderManForHoudini-23.0
RMAN_PROCEDURALPATH=$RFHTREE/18.0/openvdb:&
HOUDINI_PATH=$RFHTREE/18.0:&

On Windows with 18.0, one would edit the file in: \Users\myself\Documents\houdini18.0\houdini.env:

NOTE: Windows uses a semi-colon instead of a colon to separate the HOUDINI_PATH!

RMANTREE=C:\Program Files\Pixar\RenderManProServer-23.0
RFHTREE=C:\Program Files\Pixar\RenderManForHoudini-23.0
RMAN_PROCEDURALPATH=$RFHTREE\18.0\openvdb;&
HOUDINI_PATH=$RFHTREE\18.0;&
PATH=$RMANTREE\bin;&

Finally an example on OS-X with 18.0, one would edit this in: /Users/myself/Library/Preferences/houdini/18.0/houdini.env:

RMANTREE=/Applications/Pixar/RenderManProServer-23.0
RFHTREE=/Applications/Pixar/RenderManForHoudini-23.0
RMAN_PROCEDURALPATH=$RFHTREE/18.0/openvdb:&
HOUDINI_PATH=$RFHTREE/18.0:&