Sensors for avatar leaving area

Okay so sensor by default fires when someone enters its range but it does not fire when it exits. I am trying to make a system to keep track of people when they enter, then again when they exit. The enter part is no problem but i have to say the exit part has me a bit cornfused. If there is an obvious answer and i've just missed it, sorry. Otherwise any help would be awesome.

I have a system that does this. Use your sensor, keep a list, on the next sweep see if anybody is missing from that list.

Oh, and keep you sweep time fairly high - like 10 seconds. Or you will cause yourself some tangible lag.

also you'll want to make sure to include a no_sensor event so that you pick up when the last person leaves.

Thanks that should work out for me.

This is where I get a bit confused.

I thought the max number of avies you could pick up on a single sensor event was 16...I guessed (or had read) that visitor counters and such worked on "undocumented" features of LSL, since you could never be officially sure that you were going to see more than, worst case, the same 16 avies in a 30-avie crowd.

Is there a more definitive explanation of how it all works?

== danny d.

I wounder what happens if you try to request 20

You can't request a number. But if more than 16 matching objects are present, it only returns 16.

Yeah I just realized this when testing my object. What is the most common way to get around this? Lets say something like a raffle ball, when the person touches it they get entered. When it comes time to payout does the ball check distance from ball to person and award that way?

two answers for two seperate things:

1. when they touch the ball you have their key, that's all you need for llGiveMoney.

2. sensor sweeps using Arc values less than PI to break the sensors range into 1/4 or 1/2 area sweeps and either rotating it or having more than one prim with a sensor in it.

L8r,
UU

So basically code the radar sweeping sensor. Indeed, thanks.

"Okay so sensor by default fires when someone enters its range but it does not fire when it exits."

Isnt there a misunderstanding here? Sensor doesnt fire when something happens. It looks when you tell it to, and tells you whats there. Surely ?

Well, a sensor "goes off" when the script tells it to, via calls to llSensor or llSensorRepeat. If this sensor "ping" detects something that matches its filters, it triggers the sensor event. If it doesn't detect anything that matches its filters, it triggers the no_sensor event.

Make sense?

Mmmm... Sean Connery. "One ping only!" Yum.

you know, I have this strange tingly feeling that sensors can actually sense things much farther away than the 96 meters. Something about the code limiting itself so things dont get out of hand or somesuch I suppose. I've been fiddling with it and can actually get sensors to reach much farther by tricking them I dont know what this has to do with this thread besides sensor information, but hey

it's quite random but yeah I've had a AV sensor pick up people 499m away a few times. I'm sure the limitation is merely so the asset server doesn't have a heart attack.

UU