hello, first, is it possible to create inputs for a own digital assets that look like the inputs of the reference lop, one input for a single node and a input for multiple connections?
and what does the "is reference" check box in the type properties page under inputs/outputs mean? I can not tell the difference.
sanostol is it possible to create inputs for a own digital assets that look like the inputs of the reference lop,
I don't think you can, probably just HDK you can do multiinput by specifying lots of inputs, but not sure if you can split off the first one like that in HDA
sanostol and what does the "is reference" check box in the type properties page under inputs/outputs mean? I can not tell the difference
reference inputs show connecting wires as dashed lines to my experience it's purely visual, it doesn't have any functional meaning, many factory nodes however use dashed line to suggest that that geo doesn't get passed to the output but merely used as a reference or helper geo (but again purely for visual purposes completely up to the author which lines they make dashed)
@SWest Mh, can You describe the workflow. The reference LOP is a closed hdk build asset, so You can not dive into into it. And You mentioned "converting" a subnet to a reference LOP, what do You mean by this? Martin
okay, well, there is no option to convert a node in the right click menu, just to change type and well, it changes the type. That's it. the image You showed earlier is show just to reference nodes. one has a additional parameter, that's it. I doubt You get a new hda with Your content and functionality, but the interface of the other one. That's not how hdas work, You define then in the type properties and every functionality that You want to have must be available there.
Have You ever opened the type properties of the reference lop and the rig pose sop? Or even tried to dive into the reference Lop?
There are different ways to create digital assets. You can use the tools sidefx provides with their tools inside houdini or You can create them by hdk. the houdini tools are easy to use and very good, but hdk gives You more control and it is more challenging to create them. You have to write them in c++ and compile them for Your target system.
SWest if you have an example of a HDA with input distribution like Reference LOP I think many people would appreciate that
From your descriptions it sounds like you are just describing creating an HDA in general, but the actual question is about defining inputs to be single input + multiinput, which I've seen only on HDK nodes, not HDAs
tamte SWest if you have an example of a HDA with input distribution like Reference LOP I think many people would appreciate that
From your descriptions it sounds like you are just describing creating an HDA in general, but the actual question is about defining inputs to be single input + multiinput, which I've seen only on HDK nodes, not HDAs
Maybe some testing will be needed to see that everything really works, but here are some rough ideas.
Left: It is possible to dynamically build the UI of a node, so the left approach should work. However, there are no visual connections between nodes.
Right: It should be possible to dynamically check what inputs are used and programmatically reorder things. This is a subnet HDA with 100 inputs. So if you drag your connection to any input on the right side, it should be possible to automatically move it far left. It is somewhat a hack and I'm not sure if it feels good to use. If so, maybe it is possible to fix.
Question is purely about the same visual style Since there are many HDK nodes defined this way not only in LOPs but also DOPs
And it has an advantage over full multiinput, mostly that you can easily see and manage first input connection For now I'll continue assuming it's not possible in HDA
