Jon Parker

That did it! Thanks for the tip. Very cool to see this works!

EDIT: BTW, I did it manually instead of using loputils to keep the core code free of Houdini dependencies.

Hello,

I'm not sure where to find this info: is it possible, using only Python, to build a stage similar to the way stages are defined in a LOP network, where one can build and layer anonymous layers and then save them all to separate explicit paths using the USD ROP?

Here is what I would like to do:
- take the Solaris stage as an argument to a script in a Python LOP
- on this stage object, import various files, and create a USD layer for each. Add an explicit save path to each (but don't save yet!).
- build a hierarchy of layers using these imported files
- take the resulting stage output of the Python LOP, then save everything with a USD ROP

What I have tried to do so far in Python for each created layer is:
- create an anonymous layer and add prims
- create a "HoudiniLayerInfo" prim in the anonymous layer
- set the attribute "HoudiniSaveControl" to "explicit"
- set the "HoudiniSavePath" to my desired path

I hoped this parlor trick would convince Solaris to save my custom layers, but it did not seem to do so. The USD ROP just saved my root layer and ignored the anonymous ones, even though they had the save info prim embedded.

Is there a better way to do this? I'm aware I can just save the layers as I create them, but wanted to utilize the LOP output processors.

What's the recommended way to modify the PATH environment variable to pass on to work items? In the farm schedulers, PATH gets ignored because it contains paths in $HFS . I'd like to just be able to prepend or append extra paths to the running work item's environment without clobbering any existing path items on it.

I guess a Python pre-render script is the best approach?