Sensor Questions

What's the fastest Senor Repeat can work at?

How do I detected Multiple object names I tried || but didn't work

It's nominally 0.05 seconds, but don't expect to get anywhere near that consistently. The actual repeats you'll get are very sensitive to sim load. On the other side of the coin, sensors have a tendency to eat up a lot of a sim's script time, not just because they scan for stuff but also because they inevitably involve fairly expensive list slicing and dicing. The game is to make your sensors repeat as far apart as you can, and use as small a range as you can get away with, and still do the job.

For the name thing, you are out of luck, you would need one sensor per name. It's the same situation as listen filters, we don't have anything fancy like wildcards or regex to use there.

Yes.. Any time you find yourself asking how quickly you can repeat a sensor, it's a good time to take a step back. Not that it's something you should never do - just that it's sortofa red flag.


Does that work? I thought (but have never tried) that sensors were like timers - when you do one, it nukes any other ones you've done..

You'll have to experiment to see how small the rate parameter can be. The faster a sensor has to work, though, the more likely it is to be affected by lag. Worse still, a fast sensor is going to create a whole mess of lag. So... don't do it unless you want to create a lot of problems and lose a few friends.

You can't look for multiple object in a single sensor sweep. If you want to look for several objects, you'll need to do seperate sweeps for them. If you're tempted to do something like this ...

sensor (integer num_detected)
{
     integer i;
     for (i=0;i<=num_detected;++i)
     {
          if (llDetectedName(i) == "Item 1" || llDetectedName(i) == "Item 2" || llDetectedName(0) == "Item 3")
              {
               //Do stuff
               }
     }
}

then you'll really slow things down, so don't do that either.

Yep, they clobber, but only in the same script. You can do more than one sensor script in the same object.

In llSetTimerEvent there is a brief mention of a “Default event delay - Only so many events can be triggered per second” but no details on how many that is. In the LSL Wiki it is suggested that you can't get more than about 25 events per second, so a rate of less than 0.04 has no real effect. However, since many LSL Library calls have a 0.2 second delay built in, I've rarely been able to get more than 5 events per second, so a rate of 0.2 is the smallest I normally use.

To detect multiple object names you have to leave the name field "" which detects all objects. If you have a shorter list than that, you must check for them yourself. For example:

llSensorRepeat( “”, “”, PASSIVE, 50, PI,0.2);
. . .
sensor(integer num)
{
while(--num>=0)
{
if (llDetectedName(num)==”wall”)
llOwnerSay(“found a wall”);
if (llDetectedName(num)==”floor”)
llOwnerSay(“found a floor”);
}
}

There should be a link somewhere in there to http://wiki.secondlife.com/wiki/LSL_Delay .. will have to see where things are linking now! (eta: fixed)

Chances are, the sensor is going to detect a lot of things on every sweep unless it's on a vacant sim. That's going to add up to a lot of script time, probably losing you friends on the sim.

You don't specify a name in the llSensorRepeat function and in the sensor event handler you check the names, say:

llSensorRepeat( "", NULL_KEY, AGENT, a_Range, a_Arc, a_Rate );
sensor( integer n )
{
    integer j;
    for ( j = 0; j < n; j++ ) llOwnerSay( llDetectedName(j)+" is an agent");
}

A kinder way to do the timer thing might be a round robin arrangement, fire off a sensor for the next wanted name in the sensor/no_sensor events.