Krakatoa PRT Birth Problems

Hi

I’m currently tasked to do a disintegration effect with krakatoa and during my tests almost everything is working fine so far except when I try to save particles after I used pflow with krakatoa prt birth to modify their behavior.
My current workflow is:

  1. Create Picture for the projection
  2. Spawn particles on Object during Frame Zero use camera per pixel map on particles and use krakatoa for partitioning.
  3. Deactivate first Pflow System. Load Partition into Prt Loader to see if the the color etc came over correctly (which it did)
  4. Go back into pflow create a new particle system which looks like:
    Event 1: Krakatoa PRT Birth (use prt loader 1)-> Krakatoa PRT UPDATE(use prt loader 1) (Position/ID/COLOR checked) -> Age test (Age>1) -> NEW EVENT -> Krakatoa PRT UPDATE(use prt loader 1) (ID/COLOR CHECKED) -> Collision Test -> NEW EVENT -> Force ->DELETE (Age 120) (Display operators are there just didn’t want to mention them everytime :stuck_out_tongue:)

Inside the PRT Loader I have a constant particle count of 3.9 mio particles and if I scrub the timeline pflow agrees with that number. The Number is constant.
But as soon as I want to save my modified particles to a new prt sequence Krakatoa PRT Birth is producing another 3.9 million particles every other frame. Only during the saving process.
While saving to a prt sequence Krakatoa PRT Birth produces another set of 3.9 million particles at frame 3 so my total goes up to 7,8 million but if I just go to maybe frame 5 and render my particle count stays at 3.9 million.

I created a new scene redid the whole thing but I get the same result.
I’m using max 2014 and Krakatoa version 2.1.8.50654

Hope somebody could help me.

We discovered this problem a few weeks ago. The ID channel comparison wasn’t doing the right thing and additional particles were being created. This is fixed internally for the upcoming v2.2 update which is currently posted in our Beta forum.

How urgent is this for you? What company do you work for?