Robin ISOLA

Having the exact same issue here, adding a rest and skin attribute lookup before hairgen doesn't solve the issue on my
end.

Hey, this is even older, but I'm facing the exact same issue as op, but I do have a static version of my geometry where I generated the guides, the deform nodes is fed the guides in his Groom data input, and the animated geo in the Animated skin input but the problem very much occurs with either Cut or Adjust length nodes within the hairgen.

I've simplified my network so you can see the basics of the setup ;



Geo's are hidden (WIP, can't show/share it as of now) but you can see the guides, deform and hairgen.

I've been looking around for a solution but no luck so far.

Hello,

Let's say your pipeline consists of an alembic animated mesh and a static one to grow your guides onto, the deform links with the animated one and the hairgen follows that, correct ? Well it seems pretty straightforward until I used "guidegroom" type nodes within the hairgen (like cut or adjust length), and all of a sudden my groom doesn't follow the deform anymore and just stays put.

Scratching my head as to why, and while doing so I've been told I should export my groom (I assume the hairgen primitives/curves/please refer to the correct houdini name for them Idk) as alembic or .bgeo and deform/sim with those ?

So, my questions are : - Why are "guidegroom" types nodes breaking the deform/sim ?
- Could you explain/point me to some ressource the details of the workflow to export/import groom as
curves/alembic/.bgeo and use them for simulation ? (with an animated mesh to stick to)

I'm completely out of clue on how to fix this at this stage, ressources dealing with simulation purposes are pretty rare to non-existent online so any advice would be greatly appreciated, thanks !