Second Life Wiki - User contributions [en]

User talk:Alopex Khaos

2015-06-21T18:06:57Z

Alopex Khaos: Creating page. Logging justification of first wiki edits.

[[User:Alopex Khaos|Alopex Khaos]] ([[User talk:Alopex Khaos|talk]]) 11:06, 21 June 2015 (PDT)<br>First wiki I ever edited. Not too familiar with wiki procedures. This looks like the best place for me to log justifications for my edits. Anyone feel free to point me to a better/more official place if there is one. Likewise for formatting standards.

====Justification for edit to caveats of https://wiki.secondlife.com/wiki/LlSensor and https://wiki.secondlife.com/wiki/LlSensorRepeat:====
[[User:Alopex Khaos|Alopex Khaos]] ([[User talk:Alopex Khaos|talk]]) 11:06, 21 June 2015 (PDT)
:Procedure:
:*Created a hemispherical prim, 0.1 meters in diameter, with the curved side oriented to +X.
:*Added a simple script to change the prim's color to red in sensor and green in no_sensor events, triggered by <code>llSensorRepeat("",NULL_KEY,AGENT,3.2,PI_BY_TWO,0.1)</code>.
:*Duplicated the prim, rotated it by 180 degrees about Y axis and placed at the same location, creating a 2 part sphere. Edited the script to change the colors to yellow and blue. Linked the prims with red/green version as root.
:*Walked around the object and observed color changes as expected with the side of the sphere nearest me changing to the sensor event color whenever I came in range.
:*Wore the object as a HUD. Approached another Avatar. Observed the red/green toggle when I came into and left sensor range, so long as I was facing more toward the avatar than away. Observed yellow/blue toggle when I was facing more away than toward.
:*Rotated the HUD 90 degrees about Z axis and repeated above. Observed that the sensor orientations did not change.
:Conclusions:
:*Caveat regarding attachments as originally written is correct only for the root prim of an attachment. Non-root prims in attachments have their sensor direction offset from the avatar's forward direction according to how the prim is oriented relative to the root prim.
:*This should be regarded as a useful feature, not a bug, and documented accordingly.

LlSensorRepeat

2015-06-21T16:39:54Z

Alopex Khaos: Changed the caveat about sensors in attachments to refer to the root prim of the attachment only. Added a caveat after to describe what happens with sensors in non-root prims of attachments.

{{LSL_Function
|inject-2={{LSL_Function/uuid|id|object=*}}{{LSL Constants/Sensing|type}}
|inject-3={{Issues/SVC-2409}}{{Issues/SVC-4301}}{{Issues/SVC-6662}}{{Issues/BUG-2366}}
|func=llSensorRepeat|sort=SensorRepeat
|func_id=29|func_sleep=0.0|func_energy=10.0
|p1_type=string|p1_name=name|p1_hover=Object or avatar name|p1_desc=Object or avatar name[[#NameFormat|<span style="color:red;">!</span>]]
|p2_type=key|p2_name=id
|p3_type=integer|p3_name=type|p3_desc=mask ({{#var:AGENT_BY_LEGACY_NAME}}, {{#var:AGENT_BY_USERNAME}}, {{#var:ACTIVE}}, {{#var:PASSIVE}}, and/or {{#var:SCRIPTED}})|p3_hover=mask (AGENT_BY_LEGACY_NAME, AGENT_BY_USERNAME, ACTIVE, PASSIVE, and/or SCRIPTED)
|p4_type=float|p4_name=range|p4_desc=range in meters, {{Interval|gte=0.0|lte=96.0|center=range}}|p4_hover=range in meters, {{Interval/Hover|gte=0.0|lte=96.0|center=range}}
|p5_type=float|p5_name=arc|p5_desc=the max angle between the local x-axis of the prim and detectable objects, range {{Interval|gte=0.0|lteh=PI|lte={{#var:PI}}|center=arc}}|p5_hover=the max angle between the local x-axis of the prim and detectable objects, range {{Interval/Hover|gte=0.0|lte=PI|center=arc}}
|p6_type=float|p6_name=rate|p6_desc=How often a [[sensor]]/[[no_sensor]] will be queued.
|func_footnote=If {{LSLP|name}}, {{LSLP|id}}, and/or {{LSLP|type}} are empty or 0, they are ignored.<br/>If {{LSLP|id}} is an invalid key or [[NULL_KEY]] it is treated as empty.<br id="NameFormat"/>Depending upon which AGENT* flag is used determines the format requirements for {{LSLP|name}}

See: [http://www.lslwiki.net/lslwiki/wakka.php?wakka=llSensor llSensor] for an excellent explanation of {{LSLP|arc}}.
|func_desc=Performs a single scan for {{LSLP|name}} and {{LSLP|id}} with {{LSLP|type}} within {{LSLP|range}} meters and {{LSLP|arc}} radians of forward vector and repeats every {{LSLP|rate}} seconds. It does not perform the first scan until {{LSLP|rate}} seconds have passed.
|return_text
|spec
|caveats=*The repeat of the sensor event is adversely affected by [[llGetRegionTimeDilation|time dilation]] (lag).
*Sensors placed in the root prim of 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.
*Sensors placed in prims other than the root prim of an attachment will have their forward direction offset relative to the root prim's forward direction, e.g. a sensor in a prim whose +X direction is the reverse of the root +X will look backward.
* Only the most recent [[sensor]] event is queued. Previous sensor events are replaced.
* A repeating sensor does not persist across a state change.
* [[llSensorRepeat]] can occasionally detect outside of it's specified range every few cycles when used near sim borders. [[llSensor]] in a [[timer]] does not.
|examples=
<source lang="lsl2">// Written by Steamy Latte.
// Scans every 30 seconds for visitors within 10 meters.
// Reports new visitors to object owner when she is in range.

string AllAgents;
string OwnerName;

default
{
state_entry()
{
// arc=PI is a sphere, you could look more narrowly in the direction object is facing with PI/2, PI/4 etc.
// don't repeat this too often to avoid lag.
llSensorRepeat("", "", AGENT_BY_LEGACY_NAME, 10.0, PI, 30.0);
}
sensor(integer num_detected)
{
string thisAgent = "";
integer agentNum;
for (agentNum=0; agentNum<num_detected; agentNum++)
{
key thisKey = llDetectedKey(agentNum);
string thisAgent = llDetectedName(agentNum);
if (thisKey == llGetOwner())
{
if (AllAgents != "")
{
llOwnerSay("We've had the following visitors:" + AllAgents);
AllAgents = "";
}
}
else if (llSubStringIndex(AllAgents+"\n", "\n"+thisAgent+"\n") < 0)
{
AllAgents = AllAgents + "\n" + thisAgent;
}
}
}
}</source>

<source lang="lsl2">
// Written by Evans Love.
// (Limited to most recent 200 names by Void Singer to prevent eventual Stack/Heap Collision + clean up)
// Continuously scans for visitors within 10 meters and reports new visitors to object owner.
//-------------------------------------------------------------------------------------

integer RESPONSE_CHANNEL = -100;
float SCAN_RANGE = 10.0;
float SCAN_INTERVAL = 0.1;
list VISITOR_LIST;

default
{
state_entry()
{
llSensorRepeat("", NULL_KEY, AGENT_BY_LEGACY_NAME, SCAN_RANGE, PI, SCAN_INTERVAL);
}

sensor(integer number_detected)
{
integer agent_number;

// iterate through all detected agents
for (; agent_number < number_detected; agent_number++)
{
string this_agent_name = llDetectedName(agent_number);
key this_agent_key = llDetectedKey(agent_number);
integer index = llListFindList(VISITOR_LIST, [this_agent_name]);

// if the agent is not found on the list
if (index == -1)
{
// add her/him and make the list hold the last 200 visitors
VISITOR_LIST = [this_agent_name] + llList2List(VISITOR_LIST, 0, 198);

llDialog(this_agent_key, "Welcome!", ["Ok"], RESPONSE_CHANNEL);

llOwnerSay(this_agent_name);
}
// else agent is already on the list
}

}
}
</source>
|helpers
|also_functions=
{{LSL DefineRow||[[llSensor]]| Runs a sensor once}}
{{LSL DefineRow||[[llSensorRemove]]| Stops the llSensorRepeat timer}}
{{LSL DefineRow||[[llOverMyLand]]| What happens over owners land}}
|also_events=
{{LSL DefineRow||[[sensor]]|Triggered when a sensor detects something}}
{{LSL DefineRow||[[no_sensor]]|Triggered when a sensor detects nothing}}
|also_articles
|notes=
{{LSL Tip|You might want to use [[llGetAgentList]] instead of using sensors to get a list of all avatars within the same parcel or region.}}
|cat1=Sensor
|cat2=Detected
|cat3=Username/As A Parameter
|cat4=Legacy Name/As A Parameter
|haiku={{Haiku|Binoculars raised,|All eyes scan the horizon.|Ever vigilant.}}
}}

User:Alopex Khaos

2015-06-21T16:32:47Z

Alopex Khaos: Created page with "Long time free lance programmer--numerical analysis, custom small systems, custom drivers, etc. etc. Now massively brain injured--beware of teenagers driving meat trucks. Pl..."

Long time free lance programmer--numerical analysis, custom small systems, custom drivers, etc. etc. Now massively brain injured--beware of teenagers driving meat trucks. Pleas be patient, I'm slow, but I usually get there sooner or later. Teaching myself LSL partly as recovery therapy, mostly because it's fun to make toys.

LlSensor

2015-06-21T16:08:45Z

{{LSL_Function
|inject-2={{LSL_Function/uuid|id|object=*|sim=*}}{{LSL Constants/Sensing|type}}
|func_id=28|func_sleep=0.0|func_energy=10.0
|sort=Sensor|func=llSensor
|func_desc=Performs a single scan for {{LSLP|name}} and {{LSLP|id}} with {{LSLP|type}} within {{LSLP|radius}} meters and {{LSLP|arc}} radians of forward vector
|p1_type=string|p1_name=name|p1_hover=object or avatar name|p1_desc=object or avatar name[[#NameFormat|<span style="color:red;">!</span>]]
|p2_type=key|p2_name=id|p2_desc=
|p3_type=integer|p3_name=type|p3_desc=mask ({{#var:AGENT}}, {{#var:AGENT_BY_LEGACY_NAME}}, {{#var:AGENT_BY_USERNAME}}, {{#var:ACTIVE}}, {{#var:PASSIVE}}, and/or {{#var:SCRIPTED}})|p3_hover=mask (AGENT, AGENT_BY_LEGACY_NAME, AGENT_BY_USERNAME, ACTIVE, PASSIVE, and/or SCRIPTED)
|p4_type=float|p4_name=radius|p4_desc=distance from center {{Interval|gte=0.0|center=radius|lte=96.0m}}|p4_hover=radius 0.0 to 96.0m inclusive
|p5_type=float|p5_name=arc|p5_desc=the max angle between the local x-axis of the prim and detectable objects, range 0.0 to {{#var:PI}}|p5_hover=the max angle between the local x-axis of the prim and detectable objects, range 0.0 to PI
|func_footnote=If {{LSLP|name}} and/or {{LSLP|id}} are empty, they are ignored.<br/>If {{LSLP|id}} is an invalid key or [[NULL_KEY]] it is treated as empty.<br id="NameFormat"/>Depending upon which AGENT* flag is used determines the format requirements for {{LSLP|name}}

See: [http://www.lslwiki.net/lslwiki/wakka.php?wakka=llSensor llSensor] for an excellent explanation of {{LSLP|arc}}.
|return_text
|spec
|caveats=
*Objects do not detect themselves, and attachments cannot detect their wearers (this includes HUD attachments).
*Attachments cannot be detected by llSensor.
*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 {{Jira|SVC-5145}}).
*Sensors placed in the root prim of 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.
*Sensors placed in prims other than the root prim of an attachment will have their forward direction offset relative to the root prim's forward direction, e.g. a sensor in a prim whose +X direction is the reverse of the root +X will look backward.
*llSensor does not detect objects or agents across region boundaries
*If {{LSLP|type}} is zero, the sensor will silently fail, neither [[sensor]] or [[no_sensor]] will be triggered.
*Only 16 objects will be scanned each time.
|examples=
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). Also it will only match an agent with the {{LSLGC|Avatar/Name|legacy name}} "Governor Linden".
<source lang="lsl2">llSensor( "Governor Linden", NULL_KEY, AGENT_BY_LEGACY_NAME, 96.0, PI/4 );</source>

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.)
<source lang="lsl2">llSensor( "", NULL_KEY, ( AGENT | PASSIVE | ACTIVE ), 15.0, PI );</source>

Basic example script that when touched executes a sensor scan of agents. When the sensor event is processed it spits out messages to the owner of each detected agents' name.
<source lang="lsl2">
default
{
touch_start(integer total_number)
{
llSensor("", NULL_KEY, AGENT, 30.0, PI);
}

sensor( integer detected )
{
while(detected--)
{
llOwnerSay(llDetectedName(detected));
}
}
}
</source>

|helpers
|also_functions=
{{LSL DefineRow||[[llSensorRepeat]]| Runs a sensor on a timer}}
{{LSL DefineRow||[[llSensorRemove]]| Stops the llSensorRepeat timer}}
|also_events=
{{LSL DefineRow||[[sensor]]|Triggered when a sensor detects something}}
{{LSL DefineRow||[[no_sensor]]|Triggered when a sensor detects nothing}}
|also_articles
|notes=
{{LSL Tip|You might want to use [[llGetAgentList]] instead of using sensors to get a list of all avatars within the same parcel or region.}}
====Loops & Repetition====
Using [[llSensor]] in a [[for]] loop is a beginners mistake, as events will not interrupt each other (the sensor event will not interrupt 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.
|permission
|negative_index
|cat1=Sensor
|cat2=Detected
|cat3=Username/As A Parameter
|cat4=Legacy Name/As A Parameter
|haiku={{Haiku|The hounds are straining.|Elusive quarry sighted.|The game's afoot!}}
}}
<div id="box">
==Gallery==
<gallery>
File:sensor_pi_by_four.png|arc = PI / 4
File:sensor_pi_by_two.png|arc = PI / 2
File:sensor_pi.png|arc = PI
</gallery>
</div>