Just for a bit more context here, the reason MOPs uses a solver for effects like this is for scalability. CHOPs will really start to feel the pain as you start scaling up to tens or hundreds of thousands of packed primitives. Great use of CHOPs here though! It's a really underrated part of Houdini. I just wish they'd bring it up to speed with TouchDesigner.

@WhatIFound

2 жыл бұрын

Thanks for the response. And thanks for MOPS such a great toolset. I’ve kept playing with my set up have ended up doing the spring CHOP set up on the mops_falloff attribute before applying the MOPs transforms. It’s a lot cleaner and then any transforms applied after inherit the spring effect. Thanks again.

@MM-cn1wk

3 ай бұрын

@@WhatIFound Oow, exactly what I'm trying to do but it's not working for some reason ! Chops kind of confuse me up. I would be super interested for a tutorial with this method. :) Thank you for your video by the way !

Great. Really appreciated for performance boost... Would be great a MOPS series.

super thanks, yes a mops series would be cool to

thanks for the info!

Wonderful !!💯✌👀

u are doing great all hanks

Is there a way to make a decay effector in chops as well? decaying the position transform overtime so that you would get those pieces hover for longer like there is no gravity as the MOPs effector passes through. Maybe you can achieve it with the current setup? not sure. its a bit confusing - spring - delay - decay. This particular effect is more of a spring rather than a delay i think. maybe delay is what i am talking about?

was just playing with mops and wondering what's up with mops_apply_attributes. thx.

@WhatIFound

2 жыл бұрын

Check out the newer video I put out with a revised set up that avoids the apply attribs. Also Henry put out a dev branch release of MOPs that has a rewritten version of apply attribs that is much faster.

@vipergx

2 жыл бұрын

@@WhatIFound Just watched it! Thanks. ;)