This causes problems with a larger project I have randomly selecting a subset of points to render with a different instance.
A strange behaviour I was noting was that the flickering also was affecting attribute inputs from before the Particles. Its like the memory of the particles is getting overwritten for a partial frame. Reproduction of this behaviour here:
I since bought an update license from the previous post and have been having heaps of fun with POPs. Its very polished and I’ve got faith that these little bugs will get smoothed out Let me know if I can help with the debugging process any more.
It looks like this could be an issue with how the attribute values are displayed in the viewer. This sample shows that the PartId attribute appears to remain constant over the particle’s lifetime. We’ll keep investigating.
I have attached an example of the bug extending beyond just affecting the viewer. When I run this project, the instances glitch when they should be constant over the lifetime of the particle.
I selectively render points based on ‘Type’, which is derived from modulo TypeId.
In your example, in addition to the attribute value matching, you have a pattern set on delete2 and delete3 ([*:4]). Because the particles don’t keep a fixed position in the list and their indices change over time, you can’t rely on the index to select particles consistently. When you remove the pattern, it works as expected.
Let me know if I can help with the debugging process any more.