llVolumeDetect causes lingering phantom-ness

Is this a temporary glitch and has anyone else encountered it?

Using llVolumeDetect for splashing water, the water splashes fine once ... but then it just stays phantom, so the event won't trigger any more. I thought it may because I'm working in a laggy sim, but the water was still phantom after I relogged.

Has the function stopped working? Should I start using collision-start & collision-end events instead?

Your observations will be most welcome

Cherry

Forgive me if I'm misunderstanding, but it doesn't sound like you're using llVolumeDetect correctly. All llVolumeDetect does is give a prim the special characteristics of a) being phantom and b) still being able to detect collisions, something ordinary phantom prims cannot do. You still need event handlers in the form of collision_start or collision_end.

So just plop llVolumeDetect(TRUE) into state_entry or on_rez or somewhere like that, and handle collision events in the usual way with collision_start et al.

llVolumeDetect only detects collisions with physical objects including avatars, not non-physical objects.

I somehow doubt she's editing plywood cubes into her hot tub and hoping the water will splash.

I appreciate your tact, Anti!

I thought llVolumeDetect did the above all by itself .... going by this statement from the Wiki:

So I've just been doing this .... Am I wrong? Have I been getting away with half a script all this time?

default {
    collision_start(integer num_detected) 
    {
        llVolumeDetect(TRUE);
        llPlaySound("splashsound", 1.0);
    }
}

Yikes. Please advise!
... and thank you for taking the trouble

Cherry

You have all the right pieces, just not quite in the right order

default
{
    state_entry()
    {
        llVolumeDetect(TRUE);
    }

    collision_start(integer num_detected)
    {
        llPlaySound("splashsound", 1.0);
    }
}

See, you only need to call llVolumeDetect once in the very beginning, and it imparts the special VolumeDetect magic to the prim for All Time From that point on, avatars and other physical objects intersecting with your water will generate a collision, and then your script can have it play a sound or whatever you want to have happen.

Your script as written does something kind of interesting if you look at it closely; the water starts off normal, then someone collides with it and it becomes VolumeDetect "just in time" for you to fall into it. If you added some code to turn VolumeDetect back off at collision_end, and checked each time to see if the colliding entity was you, you'd have "security water" that stays solid for intruders Seriously though, I believe there are doors made that way.

Hope that helps some, and it was no trouble at all

I am such a dipstick

I must have been looking at that line for so long that I'd stopped seeing it!!
Thanks, Anti - and, hey, what a great idea for a "members-only" pool

Cherry.