Author: admin

Hi everyone, I created some themes for Houdini. Of course, just ping me or put in an issue if you see anything that’s wonky or could get improved. Cheers 🙂 github.com/beatreichenbach/houdini-themes

docs.google.com/document/d/1HBQ6CwiDX0MbK7-nBrLU8hF8H08uPbewZF1z8ybdRw0/edit?tab=t.0

also unrelated but this file is ridiculously fast

Attachments in this post:
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20251409/12/25/image.png

I’m trying to wrap my head around the linear solver node. Since there is very little out there on its functionality I thought I might share this very simple initial setup i cobbled together that just does an “attribute fill”.
it was painful to get this working. wish i had @jake rizzler 😮 brains.

Attachments in this post:
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20253709/12/25/attribute_fill_using_linear_solver.hiplc
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20253709/12/25/image.png

I don’t like how the guide process core and hairgen core are C++

great nodes, but the decision to make them C++ operators locks you out of some of the building blocks

there’s also a nasty bug in a couple of those hardcoded nodes

“`Hello, I have found that using hairgen SOP to generate guides will result in making: skinprimuv 3flt, but is using guidegroom(in for example draw, or plant, or any mode that creates guides) it will make: skinprimuv 2flt16 This comes down to the guidegroomcore and hairgencore spitting out the different bit depth/types. That will cause groomblend to break, as it reports it “cannot find skinprimuv” , the error coming from the guidemaskcore node, another C++ hardcoded base node.“`

love the toolset, but not sure the speed increase reason was good enough to make these into compiled nodes

@astv this you? 1minutevex.com/books/OneMinuteVex.html

lovely stuff