HDA Processor will generate 1 work item per upstream work item. If you want to provide multiple file inputs from different upstream nodes to HDA Processor, you will first need to partition those work items together before the HDA Processor node. I've attached a .hip file that demonstrates this. From the Tasks menu select “Generate Static Work Items” to see how it works (cooking it won't work as I haven't hooked up an HDA to the HDA Processor – this is just for demonstration).
If you attach your .hip file I can also take a look at it for you.
Found 208 posts.
Search results Show results as topic list.
PDG/TOPs » HDA Processor multiple inputs
- BrookeA
- 387 posts
- Offline
PDG/TOPs » HDA Processor multiple inputs
- BrookeA
- 387 posts
- Offline
With “Upstream Output Files”: the inputs are wired according to the ordering of the outputs in the upstream node. So the first output will become the first input to the HDA, the second output will be wired as the HDA's second input, etc. If you have inputs that you want to provide to the HDA Processor that are produced by multiple nodes, you will need to partition together those work items first before feeding it to the HDA Processor (and ensure that ‘Merge Input Attributes’ is enabled on the partitioner).
With the “Custom File Paths” option: the inputs are wired according to their numbering (Input File 1 -> 1st input pin of the HDA, Input File 2 -> 2nd input pin of the HDA, etc).
With the “Custom File Paths” option: the inputs are wired according to their numbering (Input File 1 -> 1st input pin of the HDA, Input File 2 -> 2nd input pin of the HDA, etc).
Edited by BrookeA - Feb. 10, 2020 14:44:52
PDG/TOPs » HDA Processor multiple inputs
- BrookeA
- 387 posts
- Offline
Hi there,
There is a section in the parameters for specifying the inputs to the HDA. When the input source is “Upstream Output Files”, all the input files with the specified tag will be used as inputs to the HDA. If you select “Custom File Paths”, you can manually specify the inputs to the HDA.
There is a section in the parameters for specifying the inputs to the HDA. When the input source is “Upstream Output Files”, all the input files with the specified tag will be used as inputs to the HDA. If you select “Custom File Paths”, you can manually specify the inputs to the HDA.
PDG/TOPs » PDG and Wrap3 command line utility
- BrookeA
- 387 posts
- Offline
Hi there,
In this instance you do not need the attribute create node. You can simply use the generic generator node and change “@counter” to “@pdg_index”. The 100 work items generated by the Generic Generator node will be indexed from 0…99 so in this use case you can directly use the @pdg_index attribute in your command string.
Here is some more information about using attributes: https://www.sidefx.com/docs/houdini/tops/attributes.html [www.sidefx.com]
In this instance you do not need the attribute create node. You can simply use the generic generator node and change “@counter” to “@pdg_index”. The 100 work items generated by the Generic Generator node will be indexed from 0…99 so in this use case you can directly use the @pdg_index attribute in your command string.
Here is some more information about using attributes: https://www.sidefx.com/docs/houdini/tops/attributes.html [www.sidefx.com]
Edited by BrookeA - Jan. 31, 2020 13:51:17
PDG/TOPs » Iterations option gone from HDA Processor node in Houdini 18
- BrookeA
- 387 posts
- Offline
The same functionality is offered by the Generic Generator node. You will want to put a Generic Generator node before the HDA Processor node with the item count set to what your iterations count would have been. For an example of this, check out roadbuilder_tile.hip in $HFS/houdini/pdg/examples/top_roadbuilder.
Houdini Indie and Apprentice » JSON data and Google Earth Studio
- BrookeA
- 387 posts
- Offline
One way could be the JSON Input TOP (https://www.sidefx.com/docs/houdini/nodes/top/jsoninput.html).
There's an example in $HFS/houdini/pdg/examples/top_jsonpipeline.
There's an example in $HFS/houdini/pdg/examples/top_jsonpipeline.
Edited by BrookeA - Jan. 9, 2020 17:46:09
Houdini Engine for 3ds Max » Loading asset in max , don't do anything ?
- BrookeA
- 387 posts
- Offline
There is documentation about sessions at: https://www.sidefx.com/docs/3dsmax/_session.html [www.sidefx.com]
But I will add this to the “Getting Started” page (https://www.sidefx.com/docs/3dsmax/_getting_started.html) and also make it more clear in the plugin's user interface when there is not an active session.
But I will add this to the “Getting Started” page (https://www.sidefx.com/docs/3dsmax/_getting_started.html) and also make it more clear in the plugin's user interface when there is not an active session.
Houdini Engine for 3ds Max » Loading asset in max , don't do anything ?
- BrookeA
- 387 posts
- Offline
PDG/TOPs » Is there a way to fill an option input to the HDAProcessor?
- BrookeA
- 387 posts
- Offline
PDG/TOPs » Trouble getting started with ffmpeg (OSX)
- BrookeA
- 387 posts
- Offline
PDG/TOPs » `@pdg_output` not finding HDA processor output geo
- BrookeA
- 387 posts
- Offline
Can you try turning on the “Save Debug .hip File” parameter? This will save out a .hip file for each work item in your PDG Temp directory with the state of the HDA. This should provide more information about what is happening.
PDG/TOPs » `@pdg_output` not finding HDA processor output geo
- BrookeA
- 387 posts
- 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”.
PDG/TOPs » HDA Processor- How to use hdasopname for object hda [h18]
- BrookeA
- 387 posts
- Offline
Hi there,
Sorry about this – I will file a documentation bug to make this more clear.
This parameter just takes the name of the node, so I believe you will want to set it to “lookat_geom”.
I will also file an RFE to update this parameter so that it can also take an absolute path.
Sorry about this – I will file a documentation bug to make this more clear.
This parameter just takes the name of the node, so I believe you will want to set it to “lookat_geom”.
I will also file an RFE to update this parameter so that it can also take an absolute path.
PDG/TOPs » `@pdg_output` not finding HDA processor output geo
- BrookeA
- 387 posts
- Offline
It should be updated every time that you select a new work item. Potential reasons for it not showing could be that the work item is missing that attribute or the file is missing on disk.
If you send me a .hip file with any required HDAs, I can take a look at the behaviour.
If you send me a .hip file with any required HDAs, I can take a look at the behaviour.
PDG/TOPs » `@pdg_output` not finding HDA processor output geo
- BrookeA
- 387 posts
- 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
PDG/TOPs » HDA Processor - Ctrl parms from attributes [SOLVED]
- BrookeA
- 387 posts
- Offline
Yes, this is possible. You can use an attribute to drive the HDA Path, and then create attributes that match the parameters on the HDA, and they will be automatically applied to the corresponding HDA parameter when the work item cooks.
PDG/TOPs » access PDG_DIR in PythonScript Top when Evaluate In Process
- BrookeA
- 387 posts
- Offline
__PDG_DIR__ is the TOP network's working directory, as specified on the scheduler for that node. Therefore, to resolve it you will need to call:
self.scheduler.localizePath('__PDG_DIR__')
PDG/TOPs » Python Script set filetag
- BrookeA
- 387 posts
- Offline
Hi there,
The pdgcmd module is for out-of-process jobs. Since you are running the Python script in-process, you can use this Python PDG API method:
Here is the docs page with more information: https://www.sidefx.com/docs/houdini/tops/pdg/WorkItem.html [www.sidefx.com]
The pdgcmd module is for out-of-process jobs. Since you are running the Python script in-process, you can use this Python PDG API method:
work_item.addResultData("/home/images/test.jpg", "file/image", 0)
Here is the docs page with more information: https://www.sidefx.com/docs/houdini/tops/pdg/WorkItem.html [www.sidefx.com]
Houdini Engine for 3ds Max » Bake with animation?
- BrookeA
- 387 posts
- Offline
There's currently no way to bake out animated data via the plugin. I will add an RFE for this.
PDG/TOPs » How to customize Top node's UI when save as Python Script?
- BrookeA
- 387 posts
- Offline
Hi,
I'm not sure exactly what is happening with the asset in your screenshot without being able to see the Python script for the node. What happens generally, though, is that PDG will construct a basic Houdini parameter interface for the node based on the template defined in the node's Python script. This has to happen because the PDG node is distinct from the TOPs node.
I made an exact copy of the Generic Generator Python script, and I've attached an image of what the auto-created TOPs UI looks like. What we always do at this stage is right click the node -> Create Digital Asset and create an HDA for the node so that we can manually create the user interface (for usability, etc).
I hope this helps – please let me know if you have any more questions.
I'm not sure exactly what is happening with the asset in your screenshot without being able to see the Python script for the node. What happens generally, though, is that PDG will construct a basic Houdini parameter interface for the node based on the template defined in the node's Python script. This has to happen because the PDG node is distinct from the TOPs node.
I made an exact copy of the Generic Generator Python script, and I've attached an image of what the auto-created TOPs UI looks like. What we always do at this stage is right click the node -> Create Digital Asset and create an HDA for the node so that we can manually create the user interface (for usability, etc).
I hope this helps – please let me know if you have any more questions.
-
- Quick Links