02-28-2009, 12:58 AM
So i still use Pflow and i am not sure if this is an issue with TP. Particles in max (maybe again just pflow) have a max number set to 10million. So what i am running into is this. If i use fumebirth it seems to not realize when a particle is infact deleted so it keeps adding it to the over all particle counts.
IE: If i have a 200 frame sequence and am birthing lets say 2000000 (rate) particles it seems to run out of particles due to the fact its creating 200000 x per second. So it hits the cap quickly. Now with a normal setup i have a delete or enable the delete if out of grid so it retains an under 10million particle count. But it seems like Fume + Pflow dont realize that the particle that was deleted is gone so it leaves that number to just keep counting up even though that particle is gone. aka there are 200000 particles ACTUALLY there but the system thinks it 10000000 (but they have been deleted).
Maybe there is a work around but i havent heard or seen anything to that. And i would love to know if this is the same thing in TP as if its not then i will use that from now on for simple fumebirth stuff.
Mark
IE: If i have a 200 frame sequence and am birthing lets say 2000000 (rate) particles it seems to run out of particles due to the fact its creating 200000 x per second. So it hits the cap quickly. Now with a normal setup i have a delete or enable the delete if out of grid so it retains an under 10million particle count. But it seems like Fume + Pflow dont realize that the particle that was deleted is gone so it leaves that number to just keep counting up even though that particle is gone. aka there are 200000 particles ACTUALLY there but the system thinks it 10000000 (but they have been deleted).
Maybe there is a work around but i havent heard or seen anything to that. And i would love to know if this is the same thing in TP as if its not then i will use that from now on for simple fumebirth stuff.
Mark