Vellum 101 - Voronoi Cloth Bags
Added 2019-05-02 08:01:00 +0000 UTCOne of our very first setups we tried pulling off in Houdini.
In this tutorial we'll go over how to set up a bunch of connected voronoi cell shaped cloth bags that are held in place by a couple of strings.
Comments
Cool stuff! It didn't exist back then, but instead of using a foreach-loop you can now flood-fill outside pieces using the group expand node, then blast. Or identify affected prims with a primitive wrangle: int prims[] = expandprimgroup(0, 'outside'); foreach(int pr; prims){ string name_pr = prim(0, 'name', pr); if(s@name == name_pr){ removeprim(0, i@primnum, 1); break; } }
Konstantin Magnus
2021-03-28 18:54:56 +0000 UTCWell as Vellum currently only is able to approximate rigid bodies via stiff softbodies you'll have to find softbody settings that work for your case: maybe generate more struts per point and increase their directional variance (so they don't always search for point straight across a given point). Or use vellum tetrahedral softbody... I kinda had good success with the first technique though. Cheers, Mo
Entagma
2019-06-24 16:30:36 +0000 UTCReally get a kick out of this one. I’m curious, how would you approach suspending a rigid body instead of the cloth … if I substitute “Vellum Configure Strut Softbody” and crank-up the stiffness I get something close, but the rigid body still deforms a bit.
Timothy M. Shead
2019-06-23 22:02:52 +0000 UTChellraiser squab incoming! :D
jeremy jozwik
2019-06-05 14:40:31 +0000 UTCThanks so much for the info guys!!
Ryan Paterson
2019-05-07 14:05:45 +0000 UTCAlso remember that when going from C4D (or any other 3D program) to Houdini, you can export your entire scene as a single Alembic and then in Houdini, use the"Object Path" and "Object Exclusion" options under the "Selection" tab in the alembic file SOP to filter which objects you read in. You could grab the particles in one SOP and use another with a different Object Path to bring in the floor, etc. Going the other way, use the Alembic ROP as Adam descibed.
Geoffrey Bailey
2019-05-06 17:17:44 +0000 UTCYes, Adam's probably referring to exporting different Houdini streams as individual Alembic caches. You could use the same ROP, by changing the input and output variables, but its usually easier to just use separate ROP nodes for each stream. Regarding scene scale: since Houdini is in Meters, I'm normally having to scale any imported geo from (Maya or C4D) down to 0.01 to deal with the difference in default scene units. In this case, going from centimeters (Maya) to Houdini (meters).
Howitzer99
2019-05-04 05:19:07 +0000 UTCExport from C4D with 0.01 and will be the equivalent of 1 in Houdini. Houdini to C4D, scale it up by 100. Primitive groups in Houdini become polygon selections in C4D. Different geo streams exported out of Houdini with an Alembic ROP become seperate objects in C4D. Some point attributes C4D will read from Houdini, others it wont (or cant..). For particle attributes you use TP groups and a Xpresso tag with P Pass, P Get & P Set to fetch attributes from the imported points and set them to something C4D understands.
Adam Priester
2019-05-03 14:28:01 +0000 UTCThis is completely random but I don't know where else to put it (if there's a DM area in Patreon I haven't found it yet, clearly). I often use a workflow that i feel is becoming quite common in motion graphics- Houdini->Alembic->C4D, and I was wondering if you guys could possibly shed some light on the elephant in the room- SCENE SCALE. I just mess around with the settings in C4D until it looks right but I know there must be a method to this madness. I feel like a good old Entagma deep dive would set me straight once and for all. Some advanced tips on exporting ABC's couldn't hurt either while you're in there... like the different maps and their benefits, getting attributes out, telling C4D how to separate geometry (like particles are one object, a floor is another)...ya that stuff. Hope that makes sense. THANK YOU I LOVE YOU
Ryan Paterson
2019-05-02 08:15:44 +0000 UTC
