Paul Golter

The invokegraphprocedural is our general-purpose "wrapper" to allow invokable SOP graphs (https://www.sidefx.com/docs/houdini/nodes/sop/invokegraph.html) to be run, taking USD prims as input

Thanks for the explanation. That sounds like a really powerful feature! Looking forward to it becoming more accessible.


And thanks for letting me know how to bake the procedurals. We tried experimenting with the preview procedurals node and exporting it but we totally missed that option on the USD ROP. Also interesting that husk as that option too.

Oh and I also was wondering if it's possible to 'bake' houdini procedurals?

As an exmaple, lets say we want to cache the hair procedural node in the current usd layer.

Hey,

thanks for the quick reply!

* you may not modify runprocedurals.py
* you may not run a procedural other than invokegraph.py
* you may not modify invokegraph.py
* you may not use a SOP graph that generates anything other than curves and/or points (unless the graph has been shipped and digitally-signed by SideFX - e.g., RBD destruction graph, Ocean graph - both in H20.0)

Thanks for the clarification. That means we should be able to run the houdini hair procedural in basic mode, which does not require a houdini license.

Can you talk a bit more about this invokegraph.py script? Where is it located and has it some sort of special meaning? I noticed it is used in the hair procedural as well.

There shouldn't be any unique license configuration required.

I tried running some jobs again with the --allowed-procedurals=all flag and some worked but some not. Strange...
Is there a command line flag for husk to check if the required license is available and if not abort he render immediatly?

Would that be?

And what is the minimum license required to run husk with procedurals?

You say "the computers can run other houdini jobs fine". What jobs are they running?

I mean for example hython jobs, which should aquire a full houdini license as far as I know.



Thanks for the help!