Difference between revisions of "LlSensor"

From Second Life Wiki
Jump to: navigation, search
m (testing)
Line 1: Line 1:
|inject-2={{LSL_Function/uuid|id|object=*|sim=*}}{{LSL Constants/Sensing|type}}
<!--|inject-2={{LSL_Function/uuid|id|object=*|sim=*}}{{LSL Constants/Sensing|type}}-->

Revision as of 12:25, 15 February 2012


Function: llSensor( string name, key id, integer type, float range, float arc );

Performs a single scan for name and id with type within range meters and arc radians of forward vector

• string name object or avatar name
• key id
• integer type mask (,,,, , and/or )
• float range range [0.0, 96.0m]
• float arc the max angle between the local x-axis of the prim and detectable objects, range 0.0 to

If name or id is empty then that empty constraint is ignored.
If id is an invalid key or NULL_KEY it is treated as empty.


  • Objects do not detect themselves, and attachments cannot detect their wearers (this includes HUD attachments).
  • For an object to be detected, the center of its root prim (the same point it would report with llGetRootPosition) must be within the sensor beam.
  • For an agent to be detected, a point near the pelvis must be inside the sensor beam (the same as llGetRootPosition would report in a script attached to that avatar). This point is indicated by red crosshairs when Advanced>Character>Display Agent Target is turned on.
    • If the agent is sitting on an object, the root prim of the sat upon object becomes a second sensor target for the agent (but not if the avatar is outside the sensor arc, see SVC-5145).
  • Sensors placed in attachments will use the direction the avatar is facing as their forward vector. In mouselook, this means that it will be wherever the avatar is looking, while out of mouselook, this means whichever way the avatar is pointing. This does not include where the avatar's head is pointing, or what animation the avatar is doing, just the direction the avatar would move in if you walked forward. This is the case, regardless of where the object is attached.
  • If type is zero, the sensor will silently fail, neither sensor or no_sensor will be triggered.
  • Only 16 objects will be scanned each time.
All Issues ~ Search JIRA for related Bugs


This sensor scans a 45 degree cone about the x-axis. (PI/2 or PI_BY_TWO scans a hemisphere. PI is a spherical scan.) <lsl>llSensor( "Gigs Taggart", NULL_KEY, AGENT, 96.0, PI/4 );</lsl>

This sensor detects all prims and agents with a given name within 15m of the sensor. (AGENT, PASSIVE and ACTIVE behave inclusively. SCRIPTED is not inclusive and will exclude non-scripted targets (like avatars) from the detected set.)

<lsl>llSensor( "", NULL_KEY, ( AGENT


Loops & Repetition

Using llSensor in a for loop is a beginners mistake, as events will not interrupt each other (the sensor event will not interupt whatever event is currently being executed). To perform repeat sensor sweeps, llSensorRepeat is the better solution. While it is possible to call llSensor from a timer event, it is less efficient to do so; there is a limit to the number of events that can be processed in a second and using the timer just to call llSensor will result in your script getting less timeslice.

See Also


•  sensor Triggered when a sensor detects something
•  no_sensor Triggered when a sensor detects nothing


•  llSensorRepeat Runs a sensor on a timer
•  llSensorRemove Stops the llSensorRepeat timer

Deep Notes

Search JIRA for related Issues


  1. ^ The ranges in this article are written in Interval Notation.


function void llSensor( string name, key id, integer type, float range, float arc );