Hi,
I want to delete nParticles.
Thats actually no problem.
For the relevant particle, I do:
particle( "-e",
"-or", <physical index of selected nParticle>,
"-at", "lifespanPP",
"-fv", 0.0,
"particleName" );
After that I do a ‘saveInitialState’ on the relevant particleObject.
I have rotationPP values for every particle.
In test scenes, all is fine. The correct particle is killed and the other particles keep their correct rotationPP data, which means the physical indices of both the position data and the rotationPP data ( and all other perParticle attribute data ) remain at identical values in their respective arrays.
( I should mention that, when a particle at physical index, lets say 10, is deleted and we have 20 particles in the particle object, then all particle data of all perParticleAttributes at index 19 jump to index 10, which is of course the right thing to do )
But in my production scene with some thousand particles, when I delete selected particles, the rotationPP data are now at wrong indices, because they simply keep being at their old index instead of jumping to the new like the position data correctly do…
It looks like that does not happen always, but I have a case here where it does.
So, is this a known issue?
Might there something obvious I do wrong?
Thanks for help!