HUSK Feather Procedural double Transform

   338   2   1
User Avatar
Member
2 posts
Joined: July 2021
Offline
Good morning

We're currently getting our Solaris + Feather pipeline up and running.

Our turntable setup is currently applying a transform to the root primitive of our asset.
Unfortunately, it seems that the transform is being applied twice to our feather procedurals.

Our assumption is that the procedural is evaluated last, and as a result, it generates the feathers based on the already transformed groom primitives, while also inheriting the transform from the root primitive.

As a quick fix, we inverted the transform and applied it to all procedurals (%type(HoudiniProceduralAPI)).
Another Idea

It would be great to know if there's a more elegant solution or some best practices to this.

Cheers,
Ole

Attachments:
after_transform.png (2.6 MB)
before_transform.png (2.6 MB)
asset_composition.png (24.4 KB)
research_featherproc_transforms_v002.hip (1.9 MB)

User Avatar
Member
249 posts
Joined: Jan. 2015
Offline
Procedural can use !resetXformStack! on the xformOpOrder, then it will ignore all parent transforms.

Have been using it on hundreds of shots with the hair procedural.

Attachments:
research_featherproc_transforms_v002_fix.hip (1.9 MB)

User Avatar
Member
2 posts
Joined: July 2021
Offline
Heileif
Procedural can use !resetXformStack! on the xformOpOrder, then it will ignore all parent transforms.

Have been using it on hundreds of shots with the hair procedural.

Works like a charm! Thank you so much.
  • Quick Links