llSensor doesn't see me

I created an object with a script, and on entry to a state it calls

llSensorRepeat("", NULL_KEY, -1, 10.0, TWO_PI, 2.0)

Well, I'm standing right there and I don't get any sensor events.
I do get no_sensor events (one every two seconds).
I've tried all the constants for the object type and gave up and passed -1 as a hail mary. In reality it'll only be looking for a certain av, but since I can't detect myself, I'm using NULL_KEY.

Why doesn't it sense me? If I create a box, it sees that. Can't this be used to sense avatars?

Thanks,
Jeff

I would say to look at the sensor event. What are the parameters in it? In other words is it set to only look for objects and not AGENTS?

(the llSensor(string name, key id, integer type, float range, float arc) part).

Use AGENT for the third field, instead of -1.

I pasted it in with that, worked for me.

default
{
    state_entry()
    {
        llSensorRepeat("", NULL_KEY, AGENT, 10.0, TWO_PI, 2.0);
    }

    sensor(integer number)
    {
        llOwnerSay(llDetectedName(0));
    }
    
    no_sensor()
    {
        llOwnerSay("None.");
    }
}

Just a note, if you're WEARING the sensor, it doesn't pick you up.

Truth.

OK -- that's the first one I tried, but I'll try it again. There are various bugs at the moment, maybe it's a bad time to learn!

Any case, glad to hear that it SHOULD pick up people.

Thanks
Jeff

Yup, it's working now!

Dunno if this would PREVENT it from sensing, but you should be using PI rather than TWO_PI. If you read the wiki, the sensor angle parameter specifies HALF the angle of the cone.

TWO_PI is correct.
TWO_PI = 360 degrees
PI = 180 degrees
PI_BY_TWO = 90 degrees

I just use PI.

"If you read the wiki, the sensor angle parameter specifies HALF the angle of the cone." ^^

so specifying PI as half of the cone, you get the other half in matching PI size, for 2 * PI total...

eeeeep!!!! Yep I stand corrected and actually my sensors use PI. Brain Fart

Thanks for the tip!