Dependency Rendering and the Render Command

   2189   2   1
User Avatar
Member
4256 posts
Joined: July 2005
Offline
This is just a little heads up for everyone.

I had a sexy little dependency network in ROPs that would get run on our farm, (when JC isn't looking). However every time I ran the job I would get a different behavior from when I just hit the render button in locally in Houdini.

As it turns out when you hit the render button it renders the ROP and its dependencies frame by frame. But when you render a ROP via hscript using the render command it renders the dependency network node by node. To render frame by frame you need to start the render with render -I <rop_name>.

No big deal but it had me going “wtfbbq” for a couple of minutes. :wink:
if(coffees<2,round(float),float)
User Avatar
Member
2199 posts
Joined: July 2005
Online
That's a handy thing to know, cheers Wolfwood
The trick is finding just the right hammer for every screw
User Avatar
Member
4256 posts
Joined: July 2005
Offline
There are tons of ways to control how the dependencies are handled, ie Batch ROP and Frame Dependency ROP. (Very handy btw.)

What tricked me was the standard, “The defaults for the interface aren't the defaults for the commands.”

if(coffees<2,round(float),float)
  • Quick Links