I am trying to string HDA processors together but after the first bake or so, the HDAs are not finding each predecessor's output geo, so they are all failing. The processors that require input have the “Create File Inputs” property set.
I have attached a simple repro where I cannot even visualize the output geo from a single HDA processor in my PDG. The file node is asking me to “please specify a geometry file.” I have verified that the HDA does cook and the file is created, and if I replace `@pdg_output` in the File node with a path to a specific geo file, it loads fine.
New to PDG, but the feels like a bug potentially as it only happens most of the time…
`@pdg_output` not finding HDA processor output geo
7473 11 1-
- BryanBishop
- Member
- 6 posts
- Joined: June 2018
- Offline
-
- BrookeA
- Staff
- 387 posts
- Joined: Aug. 2017
- Offline
Hi there,
Are you able to upload the HDA file as well?
Note that in order for the File node to resolve the @pdg_output expression, you will have to have one of the HDA Processor work items selected, as this expression is evaluated within the context of an individual work item.
Thank you!
Are you able to upload the HDA file as well?
Note that in order for the File node to resolve the @pdg_output expression, you will have to have one of the HDA Processor work items selected, as this expression is evaluated within the context of an individual work item.
Thank you!
Edited by BrookeA - Nov. 29, 2019 22:39:06
-
- BryanBishop
- Member
- 6 posts
- Joined: June 2018
- Offline
Thank you for the very prompt reply Brandon!
Pro tip on the work item selection. It makes sense, if it were based on the Output flag on the node like I assumed, it would try to throw output geo for each task in the processor? I think I am understanding it all a bit better.
There is still something funky about how that attribute is refreshed perhaps? When I select a new task in the PDG, not always does the File node pick up that update until I unselect it and select another node in the graph? It was throwing me a bit, but we answered a lot of other questions along the way!
Pro tip on the work item selection. It makes sense, if it were based on the Output flag on the node like I assumed, it would try to throw output geo for each task in the processor? I think I am understanding it all a bit better.
There is still something funky about how that attribute is refreshed perhaps? When I select a new task in the PDG, not always does the File node pick up that update until I unselect it and select another node in the graph? It was throwing me a bit, but we answered a lot of other questions along the way!
-
- BrookeA
- Staff
- 387 posts
- Joined: Aug. 2017
- Offline
-
- BryanBishop
- Member
- 6 posts
- Joined: June 2018
- Offline
Perhaps one of the things I am experiencing is just something wrong with how I have my HDA setup? I am trying to pass a range of values from a Wedge node to drive a noise offset in my HDA.
Using the hip and HDA attached, I can see in several work items that the HDA is seeing the Wedge node's values correctly, but the mesh displayed in the Scene View does not change.
Using the hip and HDA attached, I can see in several work items that the HDA is seeing the Wedge node's values correctly, but the mesh displayed in the Scene View does not change.
-
- BrookeA
- Staff
- 387 posts
- Joined: Aug. 2017
- Offline
Hi Bryan,
Everything seems to be working good for me with your setup. I can click through the work items on the HDA Processor and they are updated in the scene view.
The one thing I can think of is that the “Cache Mode” is set to Automatic, which means that if the output file already exists on disk it will cook from cache (the work item cooks instantly and the file on disk is reported as the work item's output). Do you perhaps have some bad results on disk and it's picking up those files? If you manually open the geometry files in gplay do they appear correct? If this is the case, you can avoid this by setting the Cache Mode to “Write Files”.
Everything seems to be working good for me with your setup. I can click through the work items on the HDA Processor and they are updated in the scene view.
The one thing I can think of is that the “Cache Mode” is set to Automatic, which means that if the output file already exists on disk it will cook from cache (the work item cooks instantly and the file on disk is reported as the work item's output). Do you perhaps have some bad results on disk and it's picking up those files? If you manually open the geometry files in gplay do they appear correct? If this is the case, you can avoid this by setting the Cache Mode to “Write Files”.
-
- BryanBishop
- Member
- 6 posts
- Joined: June 2018
- Offline
Brandon thanks for sticking with me! Yeah for some reason the HDA running in the PDG is generating identical .bgeo files, despite their logs saying they were run with different offset values (all attached).
Running the values from the log file through just the HDA (outside the PDG), I do get unique geo.
screenshot of gplay display: https://drive.google.com/open?id=1r1nJ5YzuIAJ4rIhBEFhxrmsC535jC7tz [drive.google.com]
Running the values from the log file through just the HDA (outside the PDG), I do get unique geo.
screenshot of gplay display: https://drive.google.com/open?id=1r1nJ5YzuIAJ4rIhBEFhxrmsC535jC7tz [drive.google.com]
Edited by BryanBishop - Dec. 5, 2019 23:03:46
-
- BrookeA
- Staff
- 387 posts
- Joined: Aug. 2017
- Offline
-
- kfinlayson
- Member
- 9 posts
- Joined: July 2013
- Offline
-
- filipw
- Member
- 138 posts
- Joined: March 2018
- Offline
-
- cuckon
- Member
- 9 posts
- Joined: Feb. 2012
- Offline
-
- cuckon
- Member
- 9 posts
- Joined: Feb. 2012
- Offline
Finally I get rid of this by using a extra attribute_create. For reference: https://www.tokeru.com/cgwiki/index.php?title=HoudiniTops#When_pdg_input_and_pdg_output_are_blank [www.tokeru.com]
-
- Quick Links