...

RenderMan can find your custom nodes easily but Houdini will need to generate the Interface for your nodes. The basic idea is to use RenderMan environment variables to point to the plugins and then run a script provided to generate the Houdini Digital Assets (HDA) that supply the interface. This script can run each time you start Houdini or you can generate the files once and then disable the script to reload these each time you start Houdini to save time. Note that changes to these nodes will require that you re-run the script to update the interface.

Environment

...

Variables

The following RenderMan Environment Variables can be used (either/or) to point to your installation location for your custom nodes, this can be a network location or separated list of multiple locations.

...

You can find more options for manual operation or possible debugging below, however, the above usage should be enough to accomplish installation of your custom nodes.

Namespace

-s pxr

Version

-V 2.0

Verbose

-v

'''Usage: args2hda.py [options] argsfile1 [argsfile2...]This program parses an args file from Pixar's RenderMan and creates hda files
which allow the shader to be accessed easily in Houdini.Options:
    -v          Verbose
    -o          Dump associated obj files
    -l hdafile  Create a Houdini Digital Asset (HDA) for a single
                shader.
    -d dsfile   Create a ds (dialog script) for a single shader.
    -L hdafile  Add shaders to a library of digital assets (one hda for all shaders)
    -N label    For a single .args file, specify the label in the menu
    -C icon     For a single .args file, specify the name of the icon
    -c iconfile For a single .args file, specify icon file path that will be embedded in hda
    -p path     Path to find the shader when rendering. This path becomes
                the Shader Name property of the hda.
    -m menu     TAB submenu path
    -O          Keep original names instead of casting to lower case.
    -s namespace
    -V version  hda version
'''

...