animatrix_
Yes that should work.
Cheers. Sorry, just edited my earlier message - realised I should just go try it myself, and it does indeed work.
animatrix_
Yes that should work.
animatrix_
You can use:hou.Node.cook(force=True)
https://www.sidefx.com/docs/houdini/hom/hou/Node.html [www.sidefx.com]
hou.node("./node_i_want_to_cook").cook(force=True)
tamteCheers, yeah, this is one route I'm exploring.
if your hesitation about creating an HDA is from the fact that its usually an external file that has to be managed
keep in mind that you can create an Embedded HDA in which case it's definition is always stored internally in the hip file
bringing in all the advantages of an HDA with convenience of a subnet
animatrix_Cheers for the clarification, and the suggestion. Yeah, I've done similar myself, but that still requires separate setting of display flag and template flag to show the "guide" overlaid with the output.
Yes this is an HDA only feature.
But one trick you can use is to show the "guide geometry" as the first output and the actual output as the second output. I have seen some HDAs that do this in production so they have real geometry as the display result of the HDA while the actual result is at the second output.
tamteAh, that was the one I couldn't find in the docs. Thanks!VortexVFXDid you try using $TIMESTEP variable directly?
…
I'm resorting to just piping it in using a parameter, with an HScript expression, but that's a bit hacky considering TimeInc has to be calculated from $FPS in HScript, plus I then need to take substepping into account with the calculation, and have no way of accounting for any variable-timestepping solvers might …
DASDWell, for a-maximum-of-three people, according to the terms :-P
…
Now I can make tools for everyone when the need arises.
…