Recent Forum Posts
Stash in an HDA July 15, 2019, 5:53 p.m.
HybrideRDI have used a very similar setup before and if it works for you I don't want to say it's wrong. I personally try to stay away from editable nodes as I feel I have less control of the setup and are better prepared for debugging but that's more a flavor thing.
I did do my database query in Python, but I then do various modifications in VEX and using other SOP nodes before I want to stash the results… and that's why I want to expose a button to just evaluate the entire tree just when the artist clicks the load button, which in itself invokes the Stash Input.
HybrideRDExactly. So in your setup your button would instead copy the geo from one node and put it in the data attribute on the hda. The stash nodes data would be referencing this.
Now I'm still not sure what your script/set-up is doing. Is it copying the data that comes in to the python node into the floating stash node?
Stash in an HDA July 15, 2019, 5:09 p.m.
yeah, that would break. Multiparm sounds like a good idea. Never combined them with data attributes myself but why not?
Stash in an HDA July 15, 2019, 11:39 a.m.
HybrideRDI took for granted that you did your database query in a python script then you could do something like in the hip.
I'm not sure how you “set this in your python code to a geometry object”? Can you elaborate on that?