Hello,

Has anyone achieved success with the new Pixar release for RfH? I have performed these steps but I keep getting errors:

1- create out/ris1 node

2- create shop/risnet1/pxrpathtracer1
getting this error when adding integrators:
Warning: flipbook rendering with no output specified, using ‘ip’.
Could not open file scripts/vop/risnet.py

3- assign pxrpathtracer1 to ris1 integrator

4- create obj/pxrstdarealight

5- create obj/cam1

6- When I click “render” in a render view, it just says “generating image” and nothing happens - it remains black and no errors are shown in the console.

When I click “Render to MPlay” off of the renderman ris1 node, I get:
“Warning: flipbook rendering with no output specified, using ‘ip’.” and nothing happens.

I've added the following to my houdini.env:
RMANTREE=“cProgram Files/Pixar/RenderManProServer-20.1”
PATH=$PATH;$RMANTREE/bin
HOUDINI_DEFAULT_RIB_RENDERER=prman20.1

and the RMANTREE path definitely exists.

Any help would great…

Thanks,
Caesar

Under Preferences/Rendering, did you check the checkbox next to Renderman20?

Yes - it is checked

Ok when I click the little film real in the lower left of the Scene View I get the error in the attached image.

Also, in this setup directions:

http://www.sidefx.com/docs/houdini15.0/render/renderman#setting-up-the-display-driver [sidefx.com]

It says to setup these environment variables:

ensure the RMANTREE is set to the installed version of RenderMan, for example:

export RMANTREE=/opt/pixar/RenderManProServer-20.0
ensure the search path includes the bin subdirectory of RenderMan, for example:

export PATH=$PATH:$RMANTREE/bin
set the HOUDINI_DEFAULT_RIB_RENDERER to the desired version, for example:

export HOUDINI_DEFAULT_RIB_RENDERER=prman20.0



…so is that how it is supposed to look in the houdini.env file like this:??

#
# Houdini Environment Settings
#
# Example:
#
# HOUDINI_NO_SPLASH = 1
export RMANTREE=“cProgram Files/Pixar/RenderManProServer-20.1”
export PATH=$PATH:$RMANTREE/bin
export HOUDINI_DEFAULT_RIB_RENDERER=prman20.1

I looked up the three errors (in the screenshot below) but I don't know how to fix them or what they mean really:

TgPathDLOpen: Bad DSO found: %s (%s)
RenderMan found the specified DSO (dynamic shared object), but it was an invalid file. The file was probably built for the wrong architecture or has undefined symbols in it.

DspyName: couldn't find requested driver: %s (%s)
You have specified a display driver which could not be located.

Can't open display image %s
The requested display image could not be initialized.

Any help would be great! thank you.
Caesar

RenderMan rendering starts, so your environment variables are set up correctly. The issue seems to be the display driver, d_houdini.dll, ie, the plug-in that makes the image appear in Houdini's MPlay window.

From your config, I noticed that you are running PRMan20.1, which did not ship with that plugin yet, but PRMan20.2 did, as mentioned on the help setup page you mentioned in your post.

However, in the error message, rman says “Bad DSO found”, so it looks like rman does find d_houdini.dll nonetheless, probably because of the configuration in $HOME/rendermn.ini. Unfortunately, it looks like that d_houdini.dll is old and was compiled with an incompatible compiler.

The best solution is to upgrade to PRMan20.2 (or even more recent if possible) and to remove the currently used d_houdini.dll from rendermn.ini.

If you must use PRMan20.1, then copy d_houdini.dll from PRMand20.2 and point to it in rendermn.ini.

You can probably also work around it by changing the Display Device parameter on the ROP node from “houdini” to “openexr”.

Thank you rafal.

I have downloaded and installed 20.7 and the error is gone, yet now there is a new license error.

I looked at the license and it looks like it is indeed a non-commercial license.

It looks like somehow a few RenderMan processes (renderers) try to run at the same time. Perhaps Render View tries to restart while one is running.

Try rendering just a single frame from the ROP node and see if it works. Otherwise, maybe you need to re-run RMan's license manager to update the renderman license for the new version?