It would be easier to do this with two separate clouds. If you clone the first cloud's points on emission, then the creation order and therefore the point indices will be the same so you can use Switch Context. You can set the cloned particles' size to 0 if you want to hide them and then "trigger" them some time after emission.
1. Store the ID as a custom attribute, say ParentID, before cloning. This will get cloned and establishes a correspondence between parent and child.
3. Use Build Array from Set to put ParentID into an array. Find the parent's ParentID in the array. You should get an array with two indices, the one that isn't the parent is the cloned child (safe to say it will be the second one).
4. . Use Build Array from Set again to put the tangents into an array. Use the child's index to get the tangent you want.
] On Behalf Of Alan Fregtman
Sent: Wednesday, July 17, 2013 9:45 AM
To: XSI Mailing List
Subject: Re: Setting data on a particle based off data from another particle in the same cloud
@ Julian & Leonard,
Thank you guys. I will check your scenes and explanations when I get home later.
It does, but only so for the particles with strands. Particles without strands get filtered out of the logic. So even though I can work out the orientation I need from the location StrandPosition's, when I set self.Orientation, it only sets it for the strandy particles, not the others. That's my main problem. How do I force my set on self.Orientation to be on the original particle IDs?
On Wed, Jul 17, 2013 at 9:28 AM, Ciaran Moloney <moloney...@gmail.com
I guess I don't understand the problem....why not do just ID to Location >> strand positions ? It's quick and gives you the array you need right away.
On Wed, Jul 17, 2013 at 2:07 PM, Christian Keller <chri...@me.com
If you clone the points clone the id into a new attribute, then you know which particle is the parent. And add a attribute that it's a clone. You can use that later to decide not to put orientation values on.
Build a set from you tangent, whatever values and then you can select the corresponding value from that set.
I'm not in front of a computer right now, but I'll have a quick look at it if you don't get it working.
m +49 179 69 36 248<tel:%2B49%20179%2069%2036%20248>
f +49 40 386 835 33
gesendet von meinem iDing
On Wed, Jul 17, 2013 at 2:34 AM, Alan Fregtman <alan.f...@gmail.com
I thought that too, but it's not cutting it. :(
The "do stuff" part doesn't get any StrandPosition data for the points without strands. (Tried both ID to Location & Point Index to Location.)