Tyler Britton

Thanks for the fix. I can't really test it out with my exact situation because we are in full production and are hesitant to switch to a non-production build, but I will check it out in the future. Should executeGraph(self, False, True, True) crash or did that require a fix as well?

For testing, the ID is set to an index I know will pickup a work item, but in the overall case it is corresponding to a variation or cluster that the user is caching geometry for. Basically we were using PDG to cache out all of our geometry, so we had a lot of setups that used it. However we now got Houdini on our farm so I wanted a way to run a work item for each variation/cluster, and then launch that on the farm.

Yeah I am still getting crashes after having tried a lot of combinations. I cannot use setSelectedWorkItem after using executeGraph to cook a dynamic PDG node. It does work if I cook the dynamic node using Right Click-Generate node, and then use the setSelectedWorkItem to select the work item.

Nevermind, it looks like executeGraph does not run the whole network, only up until the specified node.

However I am still getting crashes, even when I have already exectuted the graph. I am doing something like this.
“
otlTopPath = ”/obj/Box/topnet1/CacheIt1“
otlTopNode = hou.node(otlTopPath)

otlTopNode.executeGraph(0, 1, 1)
otlTopNode.setSelectedWorkItem(1)
”
I am not getting an error when I manually generate the top node (Right Click - Generate Node). I am only getting the crashes after doing the executeGraph(0, 1, 1).

I found setting executeGraph to executeGraph(0, 1, 0) resulted in no crashes, however that so only if I have Static jobs. When I have Dynamic ones, I get the crashes again.