Dominik Wojtarowicz

Is there a way to limit how many cores the live render rop uses? I have a decent Threadripper 9970X 32-Core machine and when I run the live render lop I can barely rotate my viewport which sort of defeats the purpose of the node for me.

I have a simulated water surface that an animal is splashing in being loaded into lops via the houdini ocean procedural in order to add more ripples to the zones outside the main splash. Currently the mesh is coming in through a sop import inside of the ocean procedural node. When i compute the final render rop, the file grows quite large and creates workflow bottlenecks.

I exported the water surface out of sops as a USD file and I'm trying to reference it inside the ocean procedural in order to avoid it getting copied again during my final render rop export that is sent to husk on our farm. The problem is that the ocean spectrum/ripples don't seem to get applied to the referenced geometry. I'm not sure if this is possible, but if it is, I suspect my sop to usd save is not including the group that the ocean spectrum is supposed to get applied to. Since usd does not support houdini's groups, what would be the proper way to convert them to some primvar that the lop context could access? Ideally a Geom Subset.

If this setup is not possible, then what would be the best approach to reference the finished water/spectrum without it getting copied again to the final rop used for rendering?

I have tried this and it does work with my feather setup, but for some reason the same setup does not work with fur. I'm reading in some hair generate nodes which display and animate fine in the sop context, but when run through the component builder workflow only a few of the fur objects appear while others don't. They all appear in the VK viewer but not in karma CPU or XPU. Doing a sop import on all the fur generate nodes and merging them together, and saving out a usd rop does work and things render fine. Unfortunately this is an ugly setup as it produces automatic file structures based on the last merge object name (the resulting file still works and contains all the fur pieces). I have tried using a layer save path on the sop import nodes that are getting merged but this also produces a single file named after the last merged node.

While all this works as a workaround, I'm worried that it will create problems later so I would rather have a clean setup.

Any ideas?