The behavior of the trailPOP when its inputs point number changes seems strange to me. Adding or removing a point in the input screws up the connectivity. Could this be optimized?
Thanks,
Josef
The very first version of the trail POP had a behavior similar to trail SOP, and behaved in a nicer way with changing number of points, that got lost when more features got added, I’ll see if we can bring it back (not totally sure how doable with the new accurate way it relates to elapsed time though), in the mean time, does the match by attribute with an id attribute work for you?
I think there are some examples with changing number of particles in Overview.toe
It’s a little more expensive though since it sorts the input points by the attribute value
Ya the “id” attribute gives you control over the point connectivity.