Right on! I'm glad that this technique can help speed things up for you VFX Skull. I use this on just about every RBD sim now, and it makes a major difference.
Hi - many thx for this, great tip! One question (I know it is not used in the end, but just for better understanding): Why (at about 6:00) is it necessary to create a spare input on the "bound1" to access the detail attribute generated by "attribpromote1"? The "bound1" already is connected to "attribpromote1", so wouldn't the expression simply work as "detail(0, "area", 0)" without the spare input?
The spare input is the best way to work nicely when creating compiled for-loops. So for that reason, it's always my go-to when I know something is going to be looped eventually. Just to add - oftentimes hscript expressions will cause errors when compiling, so that's why it's best to avoid them when looping.
Hey Allie, if you have access to the node bible, then I would suggest taking a look at the measure sop video. There's a lot of ways to use that node, so it would be worth taking a look
Very efficient and inteligent method! Thank you very much. You have really open mind. :)
A really very nice and robust technique for fast sim, Awesome!!!
You have an incredible way of explaining things in an intuitive way. Thanks so much for this!
Thank you Kyle, I'm glad I could help
Another great tip
dude, i always have this issue with chipping! thank you
Right on! I'm glad that this technique can help speed things up for you VFX Skull. I use this on just about every RBD sim now, and it makes a major difference.
@@cgforge VFX SKULL XD:)
nice content
Thank you c0d2x 👍
Cool tip ! Cheers Ty !
Hi - many thx for this, great tip!
One question (I know it is not used in the end, but just for better understanding): Why (at about 6:00) is it necessary to create a spare input on the "bound1" to access the detail attribute generated by "attribpromote1"? The "bound1" already is connected to "attribpromote1", so wouldn't the expression simply work as "detail(0, "area", 0)" without the spare input?
The spare input is the best way to work nicely when creating compiled for-loops. So for that reason, it's always my go-to when I know something is going to be looped eventually. Just to add - oftentimes hscript expressions will cause errors when compiling, so that's why it's best to avoid them when looping.
so not sure what's happening but the measure node is giving me really odd bounds like massive scale and im not sure how :(
Hey Allie, if you have access to the node bible, then I would suggest taking a look at the measure sop video. There's a lot of ways to use that node, so it would be worth taking a look