Nelson Lim
iamnelsonlim
About Me
Connect
LOCATION
Not Specified
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Overcoming a double transform from dop network within a geometry node. Sept. 12, 2019, 4 p.m.
Thanks Tomas for confirming my suspicion. At the moment, sounds like it is probably still best for setups to have dopnets that are separate objects.
Overcoming a double transform from dop network within a geometry node. Sept. 11, 2019, 7:03 p.m.
Hi guys,
I wanted to pick your brains about overcoming double transforms that happen when you place a dop network within a geometry node.
As a matter of workflow, I have found over the years that trying to contain my setups within a small set of or single geometry node has been beneficial for clarity. That something that Jeff covered also in this webinar. https://vimeo.com/272793390 [vimeo.com]
However, when you do something like that, if you need to place a transform on the geometry node or parent it to a null with a transform, inevitably, it will cause the dop network within to receive a double transform. Once from the geometry node itself and a second time when the data from the geometry node is fed into the dopnetwork via opinputpath().
I've attached a simple smoke scene to illustrate what I mean.
The pyro_doubletransformed node is being translated 8 units to on the x instead of 4 units.
Is there a simple/elegant way to avoid this from happening?
I wanted to pick your brains about overcoming double transforms that happen when you place a dop network within a geometry node.
As a matter of workflow, I have found over the years that trying to contain my setups within a small set of or single geometry node has been beneficial for clarity. That something that Jeff covered also in this webinar. https://vimeo.com/272793390 [vimeo.com]
However, when you do something like that, if you need to place a transform on the geometry node or parent it to a null with a transform, inevitably, it will cause the dop network within to receive a double transform. Once from the geometry node itself and a second time when the data from the geometry node is fed into the dopnetwork via opinputpath().
I've attached a simple smoke scene to illustrate what I mean.
The pyro_doubletransformed node is being translated 8 units to on the x instead of 4 units.
Is there a simple/elegant way to avoid this from happening?
Forced Matte Objects in image planes Oct. 12, 2016, 9:42 p.m.
I was wondering if anyone figured out a good workflow for this issue? It's hard to use the normal/Pz pass if force matte objects are still included in it.