2000 fps hybrido solve looks great...but no splash particles

Post Reply
ctjanney
Posts: 4
Joined: Fri Apr 29, 2011 3:07 am

2000 fps hybrido solve looks great...but no splash particles

Post by ctjanney » Fri Mar 09, 2012 10:22 pm

I'm matching footage shot on a phatom at 2000fps

RF 2012
preferences:
fps 2000
time step - fixed 10

grid splash particles
speed threshold 0.0
vorticity threshold 0.0

what am I missing?

User avatar
FlorianK
Posts: 238
Joined: Fri Jun 11, 2010 9:56 am
Location: Cologne, Germany

Re: 2000 fps hybrido solve looks great...but no splash parti

Post by FlorianK » Wed Mar 14, 2012 7:52 pm

For standard particles/ SPH, changing FPS also changes the speed of the fluid solver, so it might have a problem at 2000fps. I never tried a fps setting that high.

The Grid solver works differently and is independent from your substeps settings, as those only affect grid/ SPH particles. It could be (I am just guessing) the grid simulation is working fine at 2000fps, but the particle solver (Splash is calculated using standard particles) goes nuts.

What happens if you try the same scene, using the very same splash settings at a more common FPS rate, such as 25 (just for testing/ debugging). Are particles created, then?

ctjanney
Posts: 4
Joined: Fri Apr 29, 2011 3:07 am

Re: 2000 fps hybrido solve looks great...but no splash parti

Post by ctjanney » Thu Mar 15, 2012 3:06 am

FlorianK,

Thanks for reply. Yes, the grid mesh solves pretty well, if not a little 'poppy', but the particles don't solve at all. At 30fps, they solve just fine setting steps to 10/333 min/max.

I'm taking a different approach of solving at 30fps, but adjusting all my deamons + drags here and there to make it slow motion. so far, so good. Now if I could just get the spline emitter to behave and not flip it's direction all the darn time.

User avatar
FlorianK
Posts: 238
Joined: Fri Jun 11, 2010 9:56 am
Location: Cologne, Germany

Re: 2000 fps hybrido solve looks great...but no splash parti

Post by FlorianK » Thu Mar 15, 2012 4:42 pm

Just a hint:

10/333 is probably not an optimal setting, as 333 substeps calculate slowly and you don't need that many substeps very often.

Try 10 -20, 20 -50...or maybe a fixed 10, 15 or 20 will work. If that's not of, 50 -100, fixed 50 etc.

Post Reply