Jump to content
ParticleSkull

Create multiple FEM over time?

Recommended Posts

Interesting problem. You can use a SOP solver with a multisolver node to process the mesh point attributes, you just don't want to affect the P attribute directly. Attached is a solution to your intersect problem using a VDB in a sop solver to dynamically set the targetP attribute. It changes the look of your sim a little, so it still needs tweaking.

For more info on "solid object" point attributes, see here: http://www.sidefx.com/docs/houdini/nodes/dop/solidconfigureobject

Note that this works well enough that you can almost get by with a single substep. Also it almost completely takes place of the internal collision calculated by the finite element solver, try turning off self collision in the attached example to see what I mean.

flask.v1.Odforce.FF.VDB.hiplc

  • Like 3

Share this post


Link to post
Share on other sites
On 6/9/2017 at 1:54 AM, ParticleSkull said:

Guys, is there a way to get the older spheres out of the simulation, make it rigid?
Let's say, by age. If the sphere is 24 frames old it becames a static/rigid object?

So, whatever happened to this idea? I'm also curious if it would help to stabilize / speed up simulation.

Share this post


Link to post
Share on other sites

this is a cool effect - i was trying to get the copy sop to create random rotation on each spawned object but had no luck.  I was using copy stamp but couldn't suss it out - each spawned character just appears in the same rotation sadly :/

Share this post


Link to post
Share on other sites
27 minutes ago, Farmfield said:

With a copy stamp, random vector per point (per frame) would solve it. :D

all i really know is something like rand($PT)*360 or something noob and incorrect like that - no idea how to set it up for a vector :/

Share this post


Link to post
Share on other sites

I was so close doing a wrangle when I remembered - there's wheels already, no need to reinvent one. :D

Screenshot from 2017-06-27 15-30-54.png

  • Like 1

Share this post


Link to post
Share on other sites

see now my first thought went to attribute randomise but all i ever hear is ppl twiddling wrangles and writing code now so my mindset seemed to gravitate that way and i was trying to do that ffs!  So where would i plug this in on the copy sop?  I'm guessing its before the copy sop on the input template points i reckon..

Share this post


Link to post
Share on other sites

All the attrb that you want the copy to take into account for your points need to put it before the Copy. rand color, size, orient, etc.

  • Like 1

Share this post


Link to post
Share on other sites

@ParticleSkull yep i'll hopefully be having a go at doing something else hehe - got a few fun things lined up!

 

btw i couldn't get the random rotation thing working:
rand($PT)*360 in the copy stamp variable

tried a fit something or other - still nothing

 

in the end this worked:
rand($PT) * 33.3 * $FF

 

now my instanced fem things are rotated on creation.  It works sod it!

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×