You are by far one of the best Houdini teachers on TH-cam. Everything is thoroughly and calmly (not frantically like with most spazzy Houdini artists) explained and easy to follow along with.
Ik this video is two years old but thank you so much for doing this. My current 3D prof is boring as sin and is explaining all of this in a very confusing way. You keep things simple and you enlarged the node window so I can actually see what's going on. Great Job!
Thanks! Yeah I made the node window larger on purpose, you are the first to notice that! I figured people would want to see the nodes more than the 3D viewport, because it's a tutorial and everyone watching probably wants to recreate the nodes. Thanks for the awesome comment!
Thanks! I've been planning to create a new video on more details on the feedback foreach loop and how to use it for procedural modeling. Hopefully that'll be released soon!
@@bubblepins, for sure even if I work for the game industry, it's always interesting to learn something. About game, if you have some times to make a deeper video on creating hda, thanks in advance ^^
7:00 - Every time you do this merge with Fetch Feedback you're duplicating the input. So it goes exponential which is why Houdini runs out of memory. Each iteration: 2 boxes, 4 boxes, 8 , 16, 32, 64, etc.
This is a pretty good tutorial. I came to learn and I did. However, I recommend you write down/organize your thoughts and/or re-record certain sections if you need to. The part where you were explaining the merge each iteration vs feedback each iteration, it was completely jumbled and you ended up having to re-explain things because of unexpected results, like when the first cube was NOT copied because your merge was taking the iteration before the translation.. Everything made sense, but it was quite messy. BUT.. I thank you. I did learn more about for-each stuff.
@@alexanderkingkwame241 I don't think I got your message. And I didn't know IG has a message box! Double check if you have the right alias, there's another bubblepins on IG. My IG is: instagram.com/bubble_pins/ with an underscore.
@@bubblepins Your way to explain is great =), it's really entertaining. I'm learning VEX at the moment and it would be so good to get some kind of tutorial like that about "pcopen", "pcfind", get an attribute from another point etc... of course it's just an idea ^^. Thank you
@@kourage94 Yeah definitely I want to dive into VEX and hopefully soon get into CVEX for Houdini. Just building it all up. Right now I'm finishing up one last video on RBD Tools Guided Sim then pyro, then I am going to fulfil one of the requests that I got about explaining a chipping cube animation I did before and there's a camera tracking. And then I think I got most of the basics of Houdini covered to prep me for VEX. Long list ... But will get there soon. Stay tuned!
Thanks for watching! The output null nodes are just for organization, because as the projects get bigger, its good practice to put null nodes to indicate what the networks. The name "OUT_" helps find the output nodes later when you need to link the networks and makes it easier to find it in a list because the nodes are usually listed alphabetically.
thanks great video perfect explanation, i have some object in houdini and for each of this object i want to store the size of object in array but without lack i do merge each iteration but i am getting just first iteration of the size multiple times can you help?
I believe you want a feedback foreach loop. To my understanding you want to feed in the same object into the foreach loop multiple times applying the block stuff again and again in an array of some sort? A feedback foreach loop will take the result of 1 iteration and feed it into the next iteration until the foreach loop is done. I did a mini-series on feedback foreach loops: th-cam.com/play/PLqovuMX-teVNe0lstXx1XEYuoS3FnR3Gh.html Hope this helps!
Hello again! Has ever happened to you that when doing this "for each loop" with booleans substracting spheres from other objects, with over 1000 instances in 6 or 7 meshes, somehow those meshes start appearing hollow? Like if there was so much to calculate that it empties some meshes by mistake or smth. Do you know if there is a solution?
I don't recall hollowing spheres happening to me, but I remember that Houdini crashed on me several times when I ran the scene too long for more instances and more meshes, due to the growing polygon count as it cooks forward. In my case where HOudini kept crashing, I believe it was because I ran out of memory and couldn't handle the large polygon count. You can try converting the polygon to a vdb and replace the boolean with a vdbcombine and do a vdb union or vdb subtract. See if that will help? This helped me because vdb's are more memory efficient, but I don't know if it'll help with your hollowing spheres. Let me know how it turns out!
7:00 - Because every time you do this merge with Fetch Feedback you're duplicating the input. So it goes exponential which is why Houdini runs out of memory. Each iteration: 2 boxes, 4 boxes, 8 , 16, 32, 64, etc.
It should be dropped down automatically when you choose for each number, but you can also manually drop down a "block begin" node from the Tab menu and then hook up the newly "block begin" node with the foreach group by selecting the foreach group just like how its shown at 23:47 in the video.
Thanks alot. Whatever they are paying you it's not enough.
4 ปีที่แล้ว +1
OOHHAAAAA how many tutorial Videos I had seen in my life like Pluralsight Gnomon and others but.. believe me I just opened my mouth while I am watching this tutorial it is so amazing explaining like illusion thank you so so so much int thanks; for(int i=0; i
The meta data node is for the attributes in the details that the foreach loop creates. It has values for the iteration number available if you need to use that within the foreach block. Hope that helps.
I think adding a merge node with feedback each iteration will NOT do the same as changing the for-each to merge each iteration. You will have more than one cube in the same position, the way you showed when four cubes looked like three. Taking out the merge node and changing the for-each to merge each iteration does not give overlapping cubes.
7:55 - Sorry, but this is not correct. You can compare the difference between having a merge in your For-Loop and the isolated result of Merge Iteration if you pack your geo before the loop. The number of Prims in the geo spreadsheet is drastically different. Merge each iteration will create 4 prims for 4 iterations, meaning each iteration result is isolated and merged. Feedback Each Iteration with a Merge in it the way you have it will create 16. prims and it will go exponential. If you want to keep the first object, then you should merge in the initial geo after/outside the for loop.
You are by far one of the best Houdini teachers on TH-cam. Everything is thoroughly and calmly (not frantically like with most spazzy Houdini artists) explained and easy to follow along with.
Thanks for the awesome comment!
Whoa~ by far the most easy to understand Houdini tutorial ever!
This is the best way to teach a beginner, while watching I had confusions and she explained it in very next seconds.
Loved it.
Thanks! You'll love the for loops in Houdini, it comes in handy for procedural modeling so much!
Thank you very much! This is the most comprehensive tutorial on "for each loop" I've ever found.
Thanks for watching! I'm going to make another "feedback foreach loop" coming soon! Stay tuned!
This is so well thought out and well talked through, best Houdini tutorial I’ve seen yet.
Thanks so much!
Im crying watching this at night, tricky thing but you make it easier to understand, thanks
Thanks for watching!
Ik this video is two years old but thank you so much for doing this. My current 3D prof is boring as sin and is explaining all of this in a very confusing way. You keep things simple and you enlarged the node window so I can actually see what's going on. Great Job!
Thanks! Yeah I made the node window larger on purpose, you are the first to notice that! I figured people would want to see the nodes more than the 3D viewport, because it's a tutorial and everyone watching probably wants to recreate the nodes. Thanks for the awesome comment!
The way you going over it makes this really easy :) Thank you
Thanks for watching!
Wow! A lot of people need this: Houdini concepts made simple. Like you did. Thanks and Congrats!
Thanks so much for the awesome comment!
I really appreciate your detailed explanations. Thank you.
Thanks for all the awesome comments! I'm really glad you're enjoying all the videos!
Very helpful, thanks. Waiting for more videos...
This is the most clear tutorial for foreach loop! Thanks so much!
Thanks for watching!
This is very helpful in demystifying the settings of "feedback" vs "merge". Thanks!
Thanks! I've been planning to create a new video on more details on the feedback foreach loop and how to use it for procedural modeling. Hopefully that'll be released soon!
Really great and Polished Tutorial Bubble Pins. Thanks
THanks!
Very detailed!!! Cool!!!! I need more!!! :)
Thanks!
Love your videos!!!
Yep these for loops are tricky little monkeys to grasp at first. This has really helped me. thank you.
Thanks for watching!
Great Tut !!! Thanks a lot !!!
Thanks for watching!
Great tutorial! thanks for sharing
Thanks for watching!
A really big thanks, after few days, to cry with thoses loops, Victory!
Awesome!
@@bubblepins, everything is clearly explained, I hope that will the same for your other videos ^^ have a nice week end
@@OnkAnCa64 Thanks! Stay tuned for a Mantra tutorial Part 1 video that should be released tonight... I just have a couple of last things to edit
@@bubblepins, for sure even if I work for the game industry, it's always interesting to learn something. About game, if you have some times to make a deeper video on creating hda, thanks in advance ^^
whahh i finally understand this node
thanks a lots
Thanks for watching!
Thank you for spoon feeding me this for loop, really takes a bit of time to sink in, when you are used to coding! 😅 👍
I agree! In coding it seems like it's so different, but once you get over that hoop, you'll realize it's the same but with visual nodes.
Best Explain ever. Thank you.
Thanks for the comment!!
Thanks for the video.
Thank you for your video! Now I understand something
Thanks for watching! I'm working on another tutorial about Feedback Foreach Loops, hopefully I can get that out soon.
7:00 - Every time you do this merge with Fetch Feedback you're duplicating the input. So it goes exponential which is why Houdini runs out of memory. Each iteration: 2 boxes, 4 boxes, 8 , 16, 32, 64, etc.
wow you are so good at this
Thanks!
This is a pretty good tutorial. I came to learn and I did. However, I recommend you write down/organize your thoughts and/or re-record certain sections if you need to. The part where you were explaining the merge each iteration vs feedback each iteration, it was completely jumbled and you ended up having to re-explain things because of unexpected results, like when the first cube was NOT copied because your merge was taking the iteration before the translation.. Everything made sense, but it was quite messy.
BUT.. I thank you. I did learn more about for-each stuff.
This was really helpful, God bless ya, love ya
Thanks!
@@bubblepins n also try n check ur inbox @instagram, I sent a message
@@alexanderkingkwame241 I don't think I got your message. And I didn't know IG has a message box! Double check if you have the right alias, there's another bubblepins on IG. My IG is: instagram.com/bubble_pins/ with an underscore.
thanks!
super explanation
I was using this foreach loops correctly already, but I have the feeling I will use it even more correctly now lol
It's all good as long as it works!
@@bubblepins Your way to explain is great =), it's really entertaining. I'm learning VEX at the moment and it would be so good to get some kind of tutorial like that about "pcopen", "pcfind", get an attribute from another point etc... of course it's just an idea ^^.
Thank you
@@kourage94 Yeah definitely I want to dive into VEX and hopefully soon get into CVEX for Houdini. Just building it all up. Right now I'm finishing up one last video on RBD Tools Guided Sim then pyro, then I am going to fulfil one of the requests that I got about explaining a chipping cube animation I did before and there's a camera tracking. And then I think I got most of the basics of Houdini covered to prep me for VEX. Long list ... But will get there soon. Stay tuned!
you saved my life
thanks you
thank youuuuuuuu :D
:)
Best 👌
Thanks!
Thank you
Thanks for watching!
Really enjoy your tutorials. Thank you. I hope you make more. I have a question... What's the point of the output null node in this project?
Thanks for watching! The output null nodes are just for organization, because as the projects get bigger, its good practice to put null nodes to indicate what the networks. The name "OUT_" helps find the output nodes later when you need to link the networks and makes it easier to find it in a list because the nodes are usually listed alphabetically.
@@bubblepins another possible use of nulls is to have them act as the "OFF" node with the Switch SOP :)
@@psychedlicavfx6646 Yeah good point! When you got like a dozen of things to toggle on and off, it comes in super handy!
I came as soon as the alarm went off :)
Thank you! Best fan ever!
thank you
Thanks for watching!
thanks great video perfect explanation, i have some object in houdini and for each of this object i want to store the size of object in array but without lack i do merge each iteration but i am getting just first iteration of the size multiple times can you help?
I believe you want a feedback foreach loop. To my understanding you want to feed in the same object into the foreach loop multiple times applying the block stuff again and again in an array of some sort? A feedback foreach loop will take the result of 1 iteration and feed it into the next iteration until the foreach loop is done. I did a mini-series on feedback foreach loops:
th-cam.com/play/PLqovuMX-teVNe0lstXx1XEYuoS3FnR3Gh.html
Hope this helps!
Hello again! Has ever happened to you that when doing this "for each loop" with booleans substracting spheres from other objects, with over 1000 instances in 6 or 7 meshes, somehow those meshes start appearing hollow? Like if there was so much to calculate that it empties some meshes by mistake or smth. Do you know if there is a solution?
I don't recall hollowing spheres happening to me, but I remember that Houdini crashed on me several times when I ran the scene too long for more instances and more meshes, due to the growing polygon count as it cooks forward. In my case where HOudini kept crashing, I believe it was because I ran out of memory and couldn't handle the large polygon count. You can try converting the polygon to a vdb and replace the boolean with a vdbcombine and do a vdb union or vdb subtract. See if that will help? This helped me because vdb's are more memory efficient, but I don't know if it'll help with your hollowing spheres. Let me know how it turns out!
7:00 - Because every time you do this merge with Fetch Feedback you're duplicating the input. So it goes exponential which is why Houdini runs out of memory. Each iteration: 2 boxes, 4 boxes, 8 , 16, 32, 64, etc.
How did you add the block begin node into the for each connected piece. I'm struggling to get that
It should be dropped down automatically when you choose for each number, but you can also manually drop down a "block begin" node from the Tab menu and then hook up the newly "block begin" node with the foreach group by selecting the foreach group just like how its shown at 23:47 in the video.
Thanks alot. Whatever they are paying you it's not enough.
OOHHAAAAA how many tutorial Videos I had seen in my life like Pluralsight Gnomon and others but.. believe me I just opened my mouth while I am watching this tutorial it is so amazing explaining like illusion
thank you so so so much
int thanks;
for(int i=0; i
Thank you for the gracious comment!
int urWelcome = 0;
for( int j=0; j
It has been a year since this tutorial was released but i still cant find thoes 2 upcoming videos( 26:24)
It's right here:
th-cam.com/video/rGNtGkuZdsA/w-d-xo.html
It's titled, "SOP Solver for Beginners in Houdini"
Hope that helps!
Can you make grains tutorial?
I'll add it to the list, but it's a very long list... May take awhile before I get on it.
what is meta data node for??
The meta data node is for the attributes in the details that the foreach loop creates. It has values for the iteration number available if you need to use that within the foreach block.
Hope that helps.
I think adding a merge node with feedback each iteration will NOT do the same as changing the for-each to merge each iteration. You will have more than one cube in the same position, the way you showed when four cubes looked like three. Taking out the merge node and changing the for-each to merge each iteration does not give overlapping cubes.
This voice is too good for such boring things.
You're too kind!
finally you havent 10 spheres 10 times on each cube. Check it. You have 10 iterations on all your cubes
7:55 - Sorry, but this is not correct. You can compare the difference between having a merge in your For-Loop and the isolated result of Merge Iteration if you pack your geo before the loop. The number of Prims in the geo spreadsheet is drastically different. Merge each iteration will create 4 prims for 4 iterations, meaning each iteration result is isolated and merged. Feedback Each Iteration with a Merge in it the way you have it will create 16. prims and it will go exponential.
If you want to keep the first object, then you should merge in the initial geo after/outside the for loop.