Help with llSensor

I'm having problems combining the "Object Type Constants" in llSensor. If I use them individually they seem to work, but any combination of different "Types" doesn't work. The script compiles and saves just fine but doesn't work as expected. Is this a bug, OR more likely me doing something wrong? Please help me, THANKS in advance.

Here is my simple llSensor script.

default
{
state_entry()
{
}

touch_start(integer total_number)
{
llSensor("", NULL_KEY, AGENT|ACTIVE|PASSIVE|SCRIPTED, 5.0, 2 * PI);
}
sensor (integer numberDetected)
{
integer i;
for (i = 0; i < numberDetected; i++)
{
llOwnerSay( "Detected " + llDetectedName(i));
}
}

no_sensor()
{
llOwnerSay("Nothing is near me at present.";
}

}

I tried the script and it seemed to work for me. It detected an object 5 meters from the cube. What behavior did you expect?

[edit... spoke too soon]

Ok.. I see what you're seeing now... No agents being detected when all flags are present.

If I remove the "SCRIPTED" flag, I think I get the behavior you desire.

BTW, the arc should be PI not 2*PI for a full sphere.

nothing wrong with the code that I see, but you should note sensors won't detect themselves or anything they are a part of (for instance YOU if they are attached, exception, if they are in a child prim).

also the scripted flag tends to act strangely combined with other flags.... in your usage, it probably won't detect av's or non-sripted objects, see this link for details

a few small notes though... you only need to specify PI for the arc, since the arc is measured as a cone of center (+X axis) to side.... meaning that it effectively doubles (compared to an arc from cone side to cone side).... also you can replace NULL_KEY with "" for the same effect and use less memory and code.... also specifying 16 instead of AGENT|ACTIVE|PASSIVE|SCRIPTED will have the same effect, less memory, less code, but also less readable

Removing "SCRIPTED" makes it work as I expected. After reading the info in the link you provided, the statement "Combining the SCRIPTED flag with others can lead to somewhat unintuitive results:" describes in a nutshell the results I was seeing. It seems like a glitch/bug to me, but removing "SCRIPTED" is a GREAT workaround for my purposes.

THANK YOU for your very timely and professional help. It would have taken weeks waiting for a "Support Ticket".