When you clone, it creates new IDs for the cloned points. I'm guessing
that your caches particles mush have some points that gets deleted over
time? What you can do to get around this issue is save the ID as a
custom attribute (self.originalID) after reading the cache and then that
attribute will be cloned as well and you can then use that custom
attribute instead of the ID to drive your random color.
-Mathieu
Mitchell Lotierzo wrote:
Hi everyone,
I'm trying to clone some points on a point cloud by first reading in a
cache file with a "Cache On File" node and then using the "Clone
Point" node. I'm then trying to randomize their color values (which I
know relies on an ID attribute). All works well for the first three or
four frames or so, but then the color and the particle's ID shifts.
This behavior seems to cycle. I've noticed that after I clone the
points is when this behavior seems to happen. If I just plug in the
"Cache On File" node and visualize my ID attribute it's fine; no
shifting. I should point out that I'm trying to do all of this in the
modeling stack and using 2012.SAP.
Is there something trivial I'm missing here?
Thanks for any insight!
Mitch
