Ole Bohnacker
olebohnacker
About Me
Environment Generalist at Woodblock Berlin
EXPERTISE
Generalist
INDUSTRY
Film/TV
Connect
LOCATION
Berlin,
Germany
WEBSITE
Houdini Skills
ADVANCED
Procedural Modeling | Environments | Solaris | Lighting
INTERMEDIATE
Digital Assets | Hair & Fur | Cloth | Mantra | Karma | VEX
BEGINNER
Character Rigging | Motion Editing | Animation | Crowds | Muscles | Pyro FX | Fluids | Destruction FX | Realtime FX | PDG | Python
Availability
I am currently employed at Woodblock Berlin
Recent Forum Posts
HUSK Feather Procedural double Transform July 7, 2025, 10:38 a.m.
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.
HUSK Feather Procedural double Transform July 2, 2025, 6:01 a.m.
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
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