Just in case you misunderstand me:
It made a difference when I sent them out into a „delete operator“ event.
I can follow all your explanations, but the delete behaviour would then have to be the same for any other delete operation.
When I changed my flows to send out into delete event - instead of using the integrated „delete“ - it was a different simulation and I did not have the mentioned issue.
(I did not try to reproduce although, because I stopped where I thought it already to be a bug. I never ever even knew that I have to delete actively in the birth flow.
Last year I did a vast destruction setup with multiple caches without any unwanted former deleted particles in the birth flow update…. So something has either changed or it is a difference between delete straight in the surface test snd delete in a separate event. And that‘s the logic I didn‘t get)
Cheers
It made a difference when I sent them out into a „delete operator“ event.
I can follow all your explanations, but the delete behaviour would then have to be the same for any other delete operation.
When I changed my flows to send out into delete event - instead of using the integrated „delete“ - it was a different simulation and I did not have the mentioned issue.
(I did not try to reproduce although, because I stopped where I thought it already to be a bug. I never ever even knew that I have to delete actively in the birth flow.
Last year I did a vast destruction setup with multiple caches without any unwanted former deleted particles in the birth flow update…. So something has either changed or it is a difference between delete straight in the surface test snd delete in a separate event. And that‘s the logic I didn‘t get)
Cheers