Strange Particle Behaviour?

i have 2 different attachments that have particle systems in them. one is activated on touch, and one is a poofer. there's no other functions that would set them off, so i'm wondering what's causing them to activate when i login or teleport to a new sim. anyone ever seen this before?

Take a peek at the changed event stuff i.e. CHANGED_REGION and/or CHANGED_TELEPORT.

regs
/esc

yeah, but i don't have anything like that in my script. one script is simply a touch script, no state entry, on rez, or anything. the other is a poofer that only has the state entry to turn on the listen, and the actual listen event that "poofs" when told to. i have the PSYS_SRC_MAX_AGE set to 3 seconds. i also just encounted another strangeness when i went to edit the touch one, right clicking activated it too???

well i got a work around for the touch one, put the particle system in a link message function in a child prim, and put the touch script in the root to send a link message. not sure what to do about the poofer

heyas;

particle systems, even ones with limited life that should be 'off,' tend to give out one burst whenever you come into visual range of them. whether it is walking up to them, or logging in, or teleporting, or rezzing a new instance, or copying one....


that is, sad to say, normal behavior for them. don't beat yourself up about it.

ok, cool, i thought i was just going nuts. but it still makes me wonder why the touch activated one was getting triggered on right click, while other touch functions don't seem to be

ahh ok - then try this -- put in a *shortish* one-off timer

touch_start(...) {
llParticleSystem(paramlist);
llSetTimerEvent(5.0);
}
timer() {
llSetTimerEvent(0.0);
llParticleSystem([]);
}

Never depend on PSYS_SRC_MAX_AGE to turn off your particles in the long run. Use it only for redundancy with a call to 'llParticleSystem([])' to REALLY turn the particles off, unless you are only going to turn off the particles for a short period and will be making some other call to llParticleSystem() shortly anyway.

The reason is that each client will determine the particles being emitted by a prim when it first renders the prim, and "start" the particles then (the particle source will die after the PSYS_SRC_MAX_AGE duration from that moment). It is a feature, not a bug.

yeah, i got that part, so what i did was used the empty call after a 2 second sleep. but for some reason, it was still triggering when i right clicked.