Tomas Slancik

Gaalvk
I’m not sure what the purpose of adjacency is then, since we get the same result by simply copying points based on the UV layout. To be honest, the correct way to utilize adjacency still eludes me.

from my understanding adjacency doesn't create seamless representation of 3D space in 2D, if that was easy, then uv's would not have seams to begin with
what adjacency does is it creates information around seams that can sample/transform boundary data across, like a portal, so that the data moving out of a UV island can be transformed to corresponding location on neighboring island, so it's most useful for simulations where things flow through boundaries or for setups where the inside of an island can be extrapolated from information at the boundary

houdiniLearner02
For cloth/hair simulation is not normal to unlock the solver and modify/add nodes inside it?

ideally, you wouldn't need to do that, since that makes it difficult in the future to know what exactly it was unlocked for, it bloats up the file and also makes it more difficult to update the node version in the future, and dive targets stop working when HDA is unlocked, so it makes it pretty annoying to tweak the microsolvers in the actual internal dive target

the only time I unlock the Vellum Solver is when I need to do SDF colliders, which is mostly when dealing with changing topology colliders

but for selective collisions among individual pieces I'd personally do collision groups and keep things locked and just use the provided dive target for further customization

olivierth
...My goal is to connect multiple assets (packed primitives with names) to my HDA and to have the list automatically fill up like in my image. What would be the best way to do so?

in that case definitely don't make it based on geo unless maybe if you have fixed set of assets that never changes and you just want to control the visibility

if the amount/names of named prims in the expected geo is variable, I'd do a UI with default probability slider which will be a fallback value for any named prim
and then a multiparm, where you can add specific named instances, dropdown one of the names from the current geo's unique name values (or specify a name pattern) and set it's probability, which will internally use it for named prims matching that pattern instead of the default value

you can have a button that will fill the multiparm for you based on one time cook, or just add missing, maybe have enable toggle on each so you(or the button) can just disable ones that are no longer present without losing the value

but definitely keep it decoupled from the geo, since there is nothing worse than UI trying to be too smart and update when the geo is in errored state or empty and wiping out all your values, etc