Altering Particle/point Attributes

[B.Walters]

Is there a way to modify a particle/points attribute(s) (while this point is NOT being accessed in say an attribute create SOP / POP? You know, something very similar to the point() or poppoint() expression but a "set_point()" expression.

e.g.:

{

for (float i = 0; i < $NPT; i++)

{

set_point(i, "myAttribute", 0, i);

}

}

Given this is a trivial example and there's a better way to do this, but the question remains.

Thanks in advance.

[MADjestic]

Is there a way to modify a particle/points attribute(s) (while this point is NOT being accessed in say an attribute create SOP / POP? You know, something very similar to the point() or poppoint() expression but a "set_point()" expression.

e.g.:

{

for (float i = 0; i < $NPT; i++)

{

set_point(i, "myAttribute", 0, i);

}

}

Given this is a trivial example and there's a better way to do this, but the question remains.

Thanks in advance.

I am not sure if that's what you need, but I would suggest grouping your particles in 2 groups: "Accessed particles" and "Non-accessed particles" and change the attrubutes, based on particles grouping.

-oink-oink

[B.Walters]

I am not sure if that's what you need, but I would suggest grouping your particles in 2 groups: "Accessed particles" and "Non-accessed particles" and change the attrubutes, based on particles grouping.

-oink-oink

No, I don't think that's going to be what I need/mean. There's actually no current project I'm working on that I need this for, but I have found in past projects I've frequently wanted this feature.

For example, in my last project, "tiny" (if you're not familiar with "tiny" you can check it out in the WIP forum). But in there I had spaceships that flew around and blew the crap out of each other. To determine if a laser had hit a ship or not, there was a for loop that looped through all of the ships, and checked if there was a laser beam that was within a certain distance from the ship to the laser. If that threshold was met, the ship's particle would be killed. Simple enough. But let's say, I wanted to kill the laser particle as well - do I have to do another for loop that iterates through every laser to see if it's within the distance of a ship? Doesn't that seem repetitive (and slow)?

[SpencerL]

No, I don't think that's going to be what I need/mean. There's actually no current project I'm working on that I need this for, but I have found in past projects I've frequently wanted this feature.

For example, in my last project, "tiny" (if you're not familiar with "tiny" you can check it out in the WIP forum). But in there I had spaceships that flew around and blew the crap out of each other. To determine if a laser had hit a ship or not, there was a for loop that looped through all of the ships, and checked if there was a laser beam that was within a certain distance from the ship to the laser. If that threshold was met, the ship's particle would be killed. Simple enough. But let's say, I wanted to kill the laser particle as well - do I have to do another for loop that iterates through every laser to see if it's within the distance of a ship? Doesn't that seem repetitive (and slow)?

Hey,

Not sure if this helps for your "tiny" example, but couldnt you just use an attribute transfer from the ships particle to the laser particle to get a distance threshold or use a proximity pop and "add nearest distance" attribute to get your distance threshold?