|
Lish Lach
Registered User
Join date: 5 Aug 2006
Posts: 33
|
12-27-2007 13:19
Perhaps this is a well-known effect, but it took me by surprise.
I used llLoopSound on a sound stored in a prim, then decided against it. I deleted both the script and the sound from the prim's contents.
But the sound looped on, every time I rezzed the prim, even after relogging!
Of course, llStopSound terminated the phantom sound, once and for all.
Does this mean that each prim has a persistent looped sound property set by llLoopSound, similar to the persistent sit target set by llSitTarget?
|
|
Talarus Luan
Ancient Archaean Dragon
Join date: 18 Mar 2006
Posts: 4,831
|
12-27-2007 14:11
Yep, I believe a Looped sound is a prim property. It has to be, because once the statement is executed, it is supposed to be persistent.
|
|
Anti Antonelli
Deranged Toymaker
Join date: 25 Apr 2006
Posts: 1,091
|
12-27-2007 16:07
Not sure if it's a bug or a feature, but that's been my experience too.
Be advised that like a few other persistent properties of this type, shift-dragging a copy kills it too.
|
|
Talarus Luan
Ancient Archaean Dragon
Join date: 18 Mar 2006
Posts: 4,831
|
12-27-2007 16:19
Yep. That's because the prims in the copy so made are brand-spanking new. Sadly, no "hidden" prim properties are copied in shift-drag.
|