AHTYA04 - Working With Clones Part 1
Added 2018-06-07 11:06:43 +0000 UTC3D packages other than Houdini often offer a dedicated system to control and animate lots of clones. Be it Mash in Maya, MoGraph in Cinema4D or Animation Nodes in Blender. In Houdini you have to build such a system yourself, if you want to quickly and easily animate clone effects. In todays episode of AHTYA I'll show you how to code a cloning system with falloffs and effectors. We'll dive deeper into VOPs this time and create interfaces for our operators. This video is the foundation for the next video to come in 2 weeks that will explore clone setups in more detail.
Comments
The primitive sphere has 1 point but how can I use the falloff if I have multiple points like a text
Frederike Bruijn
2022-03-23 13:30:17 +0000 UTCKudos for the tuts!
Luis Román
2018-11-14 03:01:53 +0000 UTCHi Juan. None of them is there. Because things in Houdini work a little different than in Xpresso. As you always compute stuff on all elements at once a result node would be of limited use. Instead you just write your values to an attribute and use the geometry spreadsheet to inspect the values. You can do this anywhere in your graph. If you just want to have a look at the values just use an attribute called dbug or something similar. cheers mnu
Entagma
2018-10-01 15:10:35 +0000 UTCIs there a result node equivalent in Houdini to read values or spy type node to inspect ?
Juan Iturbe
2018-10-01 15:05:57 +0000 UTC100 % new here, total noob starting from c4d, amazing content Thank you
Juan Iturbe
2018-10-01 12:16:12 +0000 UTCAnother clear, complete lecture. Thanks!
Maury Rosenfeld
2018-09-11 21:19:56 +0000 UTCHi guys im learning a lot :D. I almost replicated this tutorial in vex hiting f1 all the time xD. If it is usefull for someone, this is the file <a href="https://drive.google.com/open?id=1hlLO-rmU6mOq7gr1mxVLNpy-j_BNHo68" rel="nofollow noopener" target="_blank">https://drive.google.com/open?id=1hlLO-rmU6mOq7gr1mxVLNpy-j_BNHo68</a>
Hugo Mejicanos
2018-06-27 16:43:47 +0000 UTCVOP is more graphical for beginner to understand. both are great.
Yue Wu
2018-06-11 10:51:02 +0000 UTCHaha I agree.
JP Castel
2018-06-10 21:08:32 +0000 UTCthank you. very useful. about vex and vop : I also like to learn vex but I personally prefer he do it it in VOP because he explain everything very well in VOP and make it easier with the help of VEX101 to imagine how it would look like in VEX. also we can always see the code generated by any VOP node right ? I hope he keep using VOP unless it's 2 or 3 lines vex codes it's not a problem. I think you should be carful when you ask entagma to start using VEX. if you don't believe me check their Vimeo vex tutorials. they VEX the hell out of my brain 🧠 . so plz stay with VOP for now :D
Ash
2018-06-09 08:50:40 +0000 UTCPersonally I like both. Sometimes easier to iterate and understand different noise types in VOPS, but sometimes love the straight forwardness and simplicity of VEX. So my vote would be to jump between both as you wish. That's just my opinion because I like learning VEX. Maybe also better idea to keep VEX for VEX101 and use VOPS in AHTYA, considering it's aimed at beginners.
JP Castel
2018-06-08 15:42:07 +0000 UTCPerfect:-) I can do everything in VEX instead of VOPs in the future of you prefer. I always thought People prefer VOPs
Entagma
2018-06-08 15:28:14 +0000 UTCHaha, was thinking exactly the same thing as I was watching this. So I tried myself, and this is what I came up with. vector pnt1 = point(1, "P", 0); vector rad = getbbox_max(1); vector pnt2 = @P; float grad = distance(pnt1, pnt2); float falloff = fit(grad, 0, rad[0], 1, 0); @Cd = set(falloff, 0, 0); float height = chf("Height"); float shape = chramp("Shape", falloff); float displace = height * shape; @P.y += displace;
JP Castel
2018-06-08 15:25:44 +0000 UTCWhat exactly do you have in mind?
Entagma
2018-06-07 17:12:25 +0000 UTCDo you think it might be beneficial as part of the VEX 101 stream to recreate this as a VEX only tutorial?
jimbachalo
2018-06-07 16:48:59 +0000 UTC
