Second Life Wiki - User contributions [en]

Attachment

2018-10-05T08:38:36Z

Stickman Ingmann: a word

{{Help |Glossary=*}}
{{Otheruses4‎|attachments|[[LSL]] related information about attachments|:Category:LSL Attachment|opensource specs|Attachment (OS)}}

An attachment is an object (clothing, weapons, jewelry, shoes, etc) that can be attached to an [[avatar]] at a specific location. Usually location is set by the creator of the object. The default location otherwise is the [[ATTACH_RHAND|right hand]].

Attachments are linked to bones. When a bone is animated, all attachment locations linked to that bone will move identically to the bone they are linked to.

The following is a list of attachments and the bones they are attached to.
<div style="{{#vardefineecho:style|display:inline-block; vertical-align:top; border-top: 1px dotted #AAA; margin-right: 1em;}}">
* '''Bone: Head'''
** Skull
** Nose
** Left Ear
** Right Ear
** Mouth
** Chin
* '''Bone: EyeLeft'''
** Left Eyeball
* '''Bone: EyeRight'''
** Right Eyeball
* '''Bone: FaceJaw'''
** Jaw<ref name="bento"/>
* '''Bone: FaceEarLeft'''
** Alt Left Ear<ref name="bento"/>
* '''Bone: FaceEarRight'''
** Alt Right Ear<ref name="bento"/>
* '''Bone: FaceEyeAltLeft'''
** Alt Left Eye<ref name="bento"/><ref name="alteye">The alternative eye bones do not have saccades like the default eyes. They remain still unless animated.</ref>
* '''Bone: FaceEyeAltRight'''
** Alt Right Eye<ref name="bento"/><ref name="alteye"/>
* '''Bone: FaceTongueTip'''
** Tongue<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: Neck'''
** Neck
* '''Bone: Chest'''
** Spine
** Chest
* '''Bone: Torso'''
** Left Pec<ref name="pec">The "pec" attachment slots are unfortunately named, as they attach to the central bone of the avatar's torso, and the pectoral muscles are associated with the upper or chest bone.</ref >
** Right Pec<ref name="pec"/>
* '''Bone: Pelvis'''
** Pelvis
** Stomach
* '''Bone: Groin'''
** Groin<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: CollarLeft'''
** Left Shoulder
* '''Bone: ShoulderLeft'''
** L Upper Arm
* '''Bone: ElbowLeft'''
** L Forearm
* '''Bone: WristLeft'''
** Left Hand
* '''Bone: HandRing1Left'''
** Left Ring Finger<ref name="bento">Added with the Bento Skeleton, December 2015</ref>
</div>
<div style="{{#var:style}}">
* '''Bone: CollarRight'''
** Right Shoulder
* '''Bone: ShoulderRight'''
** R Upper Arm
* '''Bone: ElbowRight'''
** R Forearm
* '''Bone: WristRight'''
** Right Hand
* '''Bone: HandRing1Right'''
** Right Ring Finger<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: HipLeft'''
** Left Hip
** L Upper Leg
* '''Bone: KneeLeft'''
** L Lower Leg
* '''Bone: AnkleLeft'''
** Left Foot<ref name="foot">Note: The leg bone hierarchy is Hip -> Knee -> Ankle -> Foot -> Toe. Foot and toe are not rigged in the default avatar, as the mesh foot is rigged to the ankle bone. Custom rigged mesh that use the foot bone may cause unexpected issues with unrigged attachments.</ref>
</div>
<div style="{{#var:style}}">
* '''Bone: HipRight'''
** Right Hip
** R Upper Leg
* '''Bone: KneeRight'''
** R Lower Leg
* '''Bone: AnkleRight'''
** Right Foot<ref name="foot"/>
</div>
<div style="{{#var:style}}">
* '''Bone: Tail1'''
** Tail Base<ref name="bento"/>
* '''Bone: Tail6'''
** Tail Tip<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: Wing4Left'''
** Left Wing<ref name="bento"/>
* '''Bone: Wing4Right'''
** Right Wing<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: HindLimb4Left'''
** Left Hind Foot<ref name="bento"/>
* '''Bone: HindLimb4Right'''
** Right Hind Foot<ref name="bento"/>
</div>

== Footnotes ==
<references/>

== See also ==
* [[Video Tutorial/Wearing attachments]]
* [[Video Tutorial/Editing attachments]]
* [[Video Tutorial/Retrieving lost attachments]]
* [[What are HUD attachments]]
* [[Video Tutorial/Advanced attachment adjustment]]

Attachment

2018-10-05T08:37:14Z

Stickman Ingmann: Documented the missing "ankle" attachment slot.

{{Help |Glossary=*}}
{{Otheruses4‎|attachments|[[LSL]] related information about attachments|:Category:LSL Attachment|opensource specs|Attachment (OS)}}

An attachment is an object (clothing, weapons, jewelry, shoes, etc) that can be attached to an [[avatar]] at a specific location. Usually location is set by the creator of the object. The default location otherwise is the [[ATTACH_RHAND|right hand]].

Attachments are linked to bones. When a bone is animated, all attachment locations linked to that bone will move identically to the bone they are linked to.

The following is a list of attachments and the bones they are attached to.
<div style="{{#vardefineecho:style|display:inline-block; vertical-align:top; border-top: 1px dotted #AAA; margin-right: 1em;}}">
* '''Bone: Head'''
** Skull
** Nose
** Left Ear
** Right Ear
** Mouth
** Chin
* '''Bone: EyeLeft'''
** Left Eyeball
* '''Bone: EyeRight'''
** Right Eyeball
* '''Bone: FaceJaw'''
** Jaw<ref name="bento"/>
* '''Bone: FaceEarLeft'''
** Alt Left Ear<ref name="bento"/>
* '''Bone: FaceEarRight'''
** Alt Right Ear<ref name="bento"/>
* '''Bone: FaceEyeAltLeft'''
** Alt Left Eye<ref name="bento"/><ref name="alteye">The alternative eye bones do not have saccades like the default eyes. They remain still unless animated.</ref>
* '''Bone: FaceEyeAltRight'''
** Alt Right Eye<ref name="bento"/><ref name="alteye"/>
* '''Bone: FaceTongueTip'''
** Tongue<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: Neck'''
** Neck
* '''Bone: Chest'''
** Spine
** Chest
* '''Bone: Torso'''
** Left Pec<ref name="pec">The "pec" attachment slots are unfortunately named, as they attach to the central bone of the avatar's torso, and the pectoral muscles are associated with the upper or chest bone.</ref >
** Right Pec<ref name="pec"/>
* '''Bone: Pelvis'''
** Pelvis
** Stomach
* '''Bone: Groin'''
** Groin<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: CollarLeft'''
** Left Shoulder
* '''Bone: ShoulderLeft'''
** L Upper Arm
* '''Bone: ElbowLeft'''
** L Forearm
* '''Bone: WristLeft'''
** Left Hand
* '''Bone: HandRing1Left'''
** Left Ring Finger<ref name="bento">Added with the Bento Skeleton, December 2015</ref>
</div>
<div style="{{#var:style}}">
* '''Bone: CollarRight'''
** Right Shoulder
* '''Bone: ShoulderRight'''
** R Upper Arm
* '''Bone: ElbowRight'''
** R Forearm
* '''Bone: WristRight'''
** Right Hand
* '''Bone: HandRing1Right'''
** Right Ring Finger<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: HipLeft'''
** Left Hip
** L Upper Leg
* '''Bone: KneeLeft'''
** L Lower Leg
* '''Bone: AnkleLeft'''
** Left Foot<ref name="foot">Note: The leg bone hierarchy is Hip -> Knee -> Ankle -> Foot -> Toe. Foot and toe are not rigged in the default skeleton, as the mesh foot is rigged to the ankle bone. Custom rigged mesh that use the foot bone may cause unexpected issues with unrigged attachments.</ref>
</div>
<div style="{{#var:style}}">
* '''Bone: HipRight'''
** Right Hip
** R Upper Leg
* '''Bone: KneeRight'''
** R Lower Leg
* '''Bone: AnkleRight'''
** Right Foot<ref name="foot"/>
</div>
<div style="{{#var:style}}">
* '''Bone: Tail1'''
** Tail Base<ref name="bento"/>
* '''Bone: Tail6'''
** Tail Tip<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: Wing4Left'''
** Left Wing<ref name="bento"/>
* '''Bone: Wing4Right'''
** Right Wing<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: HindLimb4Left'''
** Left Hind Foot<ref name="bento"/>
* '''Bone: HindLimb4Right'''
** Right Hind Foot<ref name="bento"/>
</div>

== Footnotes ==
<references/>

== See also ==
* [[Video Tutorial/Wearing attachments]]
* [[Video Tutorial/Editing attachments]]
* [[Video Tutorial/Retrieving lost attachments]]
* [[What are HUD attachments]]
* [[Video Tutorial/Advanced attachment adjustment]]

Attachment

2018-10-05T08:14:43Z

Stickman Ingmann: Removed personal frustration from pectoral footnote.

{{Help |Glossary=*}}
{{Otheruses4‎|attachments|[[LSL]] related information about attachments|:Category:LSL Attachment|opensource specs|Attachment (OS)}}

An attachment is an object (clothing, weapons, jewelry, shoes, etc) that can be attached to an [[avatar]] at a specific location. Usually location is set by the creator of the object. The default location otherwise is the [[ATTACH_RHAND|right hand]].

Attachments are linked to bones. When a bone is animated, all attachment locations linked to that bone will move identically to the bone they are linked to.

The following is a list of attachments and the bones they are attached to.
<div style="{{#vardefineecho:style|display:inline-block; vertical-align:top; border-top: 1px dotted #AAA; margin-right: 1em;}}">
* '''Bone: Head'''
** Skull
** Nose
** Left Ear
** Right Ear
** Mouth
** Chin
* '''Bone: EyeLeft'''
** Left Eyeball
* '''Bone: EyeRight'''
** Right Eyeball
* '''Bone: FaceJaw'''
** Jaw<ref name="bento"/>
* '''Bone: FaceEarLeft'''
** Alt Left Ear<ref name="bento"/>
* '''Bone: FaceEarRight'''
** Alt Right Ear<ref name="bento"/>
* '''Bone: FaceEyeAltLeft'''
** Alt Left Eye<ref name="bento"/><ref name="alteye">The alternative eye bones do not have saccades like the default eyes. They remain still unless animated.</ref>
* '''Bone: FaceEyeAltRight'''
** Alt Right Eye<ref name="bento"/><ref name="alteye"/>
* '''Bone: FaceTongueTip'''
** Tongue<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: Neck'''
** Neck
* '''Bone: Chest'''
** Spine
** Chest
* '''Bone: Torso'''
** Left Pec<ref name="pec">The "pec" attachment slots are unfortunately named, as they attach to the central bone of the avatar's torso, and the pectoral muscles are associated with the upper or chest bone.</ref >
** Right Pec<ref name="pec"/>
* '''Bone: Pelvis'''
** Pelvis
** Stomach
* '''Bone: Groin'''
** Groin<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: CollarLeft'''
** Left Shoulder
* '''Bone: ShoulderLeft'''
** L Upper Arm
* '''Bone: ElbowLeft'''
** L Forearm
* '''Bone: WristLeft'''
** Left Hand
* '''Bone: HandRing1Left'''
** Left Ring Finger<ref name="bento">Added with the Bento Skeleton, December 2015</ref>
</div>
<div style="{{#var:style}}">
* '''Bone: CollarRight'''
** Right Shoulder
* '''Bone: ShoulderRight'''
** R Upper Arm
* '''Bone: ElbowRight'''
** R Forearm
* '''Bone: WristRight'''
** Right Hand
* '''Bone: HandRing1Right'''
** Right Ring Finger<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: HipLeft'''
** Left Hip
** L Upper Leg
* '''Bone: KneeLeft'''
** L Lower Leg
* '''Bone: AnkleLeft'''
** Left Foot
</div>
<div style="{{#var:style}}">
* '''Bone: HipRight'''
** Right Hip
** R Upper Leg
* '''Bone: KneeRight'''
** R Lower Leg
* '''Bone: AnkleRight'''
** Right Foot
</div>
<div style="{{#var:style}}">
* '''Bone: Tail1'''
** Tail Base<ref name="bento"/>
* '''Bone: Tail6'''
** Tail Tip<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: Wing4Left'''
** Left Wing<ref name="bento"/>
* '''Bone: Wing4Right'''
** Right Wing<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: HindLimb4Left'''
** Left Hind Foot<ref name="bento"/>
* '''Bone: HindLimb4Right'''
** Right Hind Foot<ref name="bento"/>
</div>

== Footnotes ==
<references/>

== See also ==
* [[Video Tutorial/Wearing attachments]]
* [[Video Tutorial/Editing attachments]]
* [[Video Tutorial/Retrieving lost attachments]]
* [[What are HUD attachments]]
* [[Video Tutorial/Advanced attachment adjustment]]

Attachment

2018-10-05T08:10:55Z

Stickman Ingmann: Added attachment points from Bento

{{Help |Glossary=*}}
{{Otheruses4‎|attachments|[[LSL]] related information about attachments|:Category:LSL Attachment|opensource specs|Attachment (OS)}}

An attachment is an object (clothing, weapons, jewelry, shoes, etc) that can be attached to an [[avatar]] at a specific location. Usually location is set by the creator of the object. The default location otherwise is the [[ATTACH_RHAND|right hand]].

Attachments are linked to bones. When a bone is animated, all attachment locations linked to that bone will move identically to the bone they are linked to.

The following is a list of attachments and the bones they are attached to.
<div style="{{#vardefineecho:style|display:inline-block; vertical-align:top; border-top: 1px dotted #AAA; margin-right: 1em;}}">
* '''Bone: Head'''
** Skull
** Nose
** Left Ear
** Right Ear
** Mouth
** Chin
* '''Bone: EyeLeft'''
** Left Eyeball
* '''Bone: EyeRight'''
** Right Eyeball
* '''Bone: FaceJaw'''
** Jaw<ref name="bento"/>
* '''Bone: FaceEarLeft'''
** Alt Left Ear<ref name="bento"/>
* '''Bone: FaceEarRight'''
** Alt Right Ear<ref name="bento"/>
* '''Bone: FaceEyeAltLeft'''
** Alt Left Eye<ref name="bento"/><ref name="alteye">The alternative eye bones do not have saccades like the default eyes. They remain still unless animated.</ref>
* '''Bone: FaceEyeAltRight'''
** Alt Right Eye<ref name="bento"/><ref name="alteye"/>
* '''Bone: FaceTongueTip'''
** Tongue<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: Neck'''
** Neck
* '''Bone: Chest'''
** Spine
** Chest
* '''Bone: Torso'''
** Left Pec<ref name="pec">The "pec" attachment slots are unfortunately named, as they attach to the central bone of the avatar's torso, and the pectoral muscles are associated with the upper or chest bone. Worse still, in LSL the misnamed the original constants (which was later fixed by adding new constants).</ref >
** Right Pec<ref name="pec"/>
* '''Bone: Pelvis'''
** Pelvis
** Stomach
* '''Bone: Groin'''
** Groin<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: CollarLeft'''
** Left Shoulder
* '''Bone: ShoulderLeft'''
** L Upper Arm
* '''Bone: ElbowLeft'''
** L Forearm
* '''Bone: WristLeft'''
** Left Hand
* '''Bone: HandRing1Left'''
** Left Ring Finger<ref name="bento">Added with the Bento Skeleton, December 2015</ref>
</div>
<div style="{{#var:style}}">
* '''Bone: CollarRight'''
** Right Shoulder
* '''Bone: ShoulderRight'''
** R Upper Arm
* '''Bone: ElbowRight'''
** R Forearm
* '''Bone: WristRight'''
** Right Hand
* '''Bone: HandRing1Right'''
** Right Ring Finger<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: HipLeft'''
** Left Hip
** L Upper Leg
* '''Bone: KneeLeft'''
** L Lower Leg
* '''Bone: AnkleLeft'''
** Left Foot
</div>
<div style="{{#var:style}}">
* '''Bone: HipRight'''
** Right Hip
** R Upper Leg
* '''Bone: KneeRight'''
** R Lower Leg
* '''Bone: AnkleRight'''
** Right Foot
</div>
<div style="{{#var:style}}">
* '''Bone: Tail1'''
** Tail Base<ref name="bento"/>
* '''Bone: Tail6'''
** Tail Tip<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: Wing4Left'''
** Left Wing<ref name="bento"/>
* '''Bone: Wing4Right'''
** Right Wing<ref name="bento"/>
</div>
<div style="{{#var:style}}">
* '''Bone: HindLimb4Left'''
** Left Hind Foot<ref name="bento"/>
* '''Bone: HindLimb4Right'''
** Right Hind Foot<ref name="bento"/>
</div>

== Footnotes ==
<references/>

== See also ==
* [[Video Tutorial/Wearing attachments]]
* [[Video Tutorial/Editing attachments]]
* [[Video Tutorial/Retrieving lost attachments]]
* [[What are HUD attachments]]
* [[Video Tutorial/Advanced attachment adjustment]]

LlSetTimerEvent

2013-09-27T22:51:29Z

Stickman Ingmann: Made the just-added example not stretch beyond the right edge of the screen.

{{LSL_Function
|func_id=107|func_sleep=0.0|func_energy=10.0
|func=llSetTimerEvent|p1_type=float|p1_name=sec|p1_desc=Any positive non-zero value to enable, zero (0.0) to disable.
|func_desc=Cause the [[timer]] event to be triggered a maximum of once every '''sec''' seconds. Passing in 0.0 stops further timer events.
|func_footnote
|return_text
|spec
|caveats=
*The time between timer events can be longer, this is caused by:
** '''Time dilation''' - See [[llGetRegionTimeDilation]] for more information.
** '''[[LSL Delay#Events|Default event delay]]''' - Only so many events can be triggered per second.
** '''Event Execution''' - If the execution of an event takes too long.
*The timer persists across state changes, but gets removed when the script is reset. So if you change to a state that has a timer() event, with the timer still running, it will fire in the new state.
*Setting a new timer replaces the old timer, and if called faster than the timer can ever trigger will result in no timer event ever firing.
|constants
|examples=

<lsl>
// default of counter is 0 upon script load
integer counter;
float gap = 2.0;

default
{
state_entry()
{
llSetTimerEvent(gap);
}

touch_start(integer total_number)
{
llSay(0, "The timer stops.");
llSetTimerEvent(0.0);
counter = 0;
}

timer()
{
++counter;
llSay(0,
(string)counter+" ticks have passed in " + (string)llGetTime()
+ " script seconds.\nEstimated elapsed time: " + (string)(counter * gap));
}
}
</lsl>
<lsl>
// random period in between (+15.0, +30.0]
// which means the resulting float could be 30.0 but not 15.0

llSetTimerEvent( 30.0 - llFrand(15.0) );

// same results for:
// llSetTimerEvent( 30.0 + llFrand(-15.0) );
</lsl>
<lsl>
// The timer event will never fire.
default
{
state_entry()
{
llSetTimerEvent(5.0);
// Sensor every 2.5 seconds
llSensorRepeat("", NULL_KEY, FALSE, 0.0, 0.0, 2.5);
}

no_sensor()
{
llSetTimerEvent(5.0);
}

timer()
{
llSay(0, "I will never happen.");
llSay(0, "Well, unless llSensorRepeat() magically finds something,"+
"or maybe there's 2.5+ seconds of lag and the timer()"+
"event queues.");
}
}
</lsl>
|helpers
|also_functions=
{{LSL DefineRow||[[llSensorRepeat]]|}}
{{LSL DefineRow||[[llGetRegionTimeDilation]]|}}
{{LSL DefineRow||[[llGetTime]]|}}
|also_events={{LSL DefineRow||[[timer]]|}}
|also_tests
|also_articles
|notes=*[http://community.secondlife.com/t5/LSL-Scripting/quot-on-mouselook-quot/m-p/768291#M545 Notes on minimum practical llSetTimerEvent values], Second Life forum, 2011-03-21
|permission
|negative_index
|sort=SetTimerEvent
|cat1=Script
|cat2=Time
|cat3
|cat4
}}

LlSetTimerEvent

2013-09-27T22:49:58Z

Stickman Ingmann: Additional llSetTimerEvent() calls reset current timer, added example.

{{LSL_Function
|func_id=107|func_sleep=0.0|func_energy=10.0
|func=llSetTimerEvent|p1_type=float|p1_name=sec|p1_desc=Any positive non-zero value to enable, zero (0.0) to disable.
|func_desc=Cause the [[timer]] event to be triggered a maximum of once every '''sec''' seconds. Passing in 0.0 stops further timer events.
|func_footnote
|return_text
|spec
|caveats=
*The time between timer events can be longer, this is caused by:
** '''Time dilation''' - See [[llGetRegionTimeDilation]] for more information.
** '''[[LSL Delay#Events|Default event delay]]''' - Only so many events can be triggered per second.
** '''Event Execution''' - If the execution of an event takes too long.
*The timer persists across state changes, but gets removed when the script is reset. So if you change to a state that has a timer() event, with the timer still running, it will fire in the new state.
*Setting a new timer replaces the old timer, and if called faster than the timer can ever trigger will result in no timer event ever firing.
|constants
|examples=

<lsl>
// default of counter is 0 upon script load
integer counter;
float gap = 2.0;

default
{
state_entry()
{
llSetTimerEvent(gap);
}

touch_start(integer total_number)
{
llSay(0, "The timer stops.");
llSetTimerEvent(0.0);
counter = 0;
}

timer()
{
++counter;
llSay(0,
(string)counter+" ticks have passed in " + (string)llGetTime()
+ " script seconds.\nEstimated elapsed time: " + (string)(counter * gap));
}
}
</lsl>
<lsl>
// random period in between (+15.0, +30.0]
// which means the resulting float could be 30.0 but not 15.0

llSetTimerEvent( 30.0 - llFrand(15.0) );

// same results for:
// llSetTimerEvent( 30.0 + llFrand(-15.0) );
</lsl>
<lsl>
// The timer event will never fire.
default
{
state_entry()
{
llSetTimerEvent(5.0);
llSensorRepeat("", NULL_KEY, FALSE, 0.0, 0.0, 2.5); // Sensor every 2.5 seconds
}

no_sensor()
{
llSetTimerEvent(5.0);
}

timer()
{
llSay(0, "I will never happen.");
llSay(0, "Well, unless llSensorRepeat() magically finds something, or maybe there's 2.5+ seconds of lag and the timer() event queues.");
}
}
</lsl>
|helpers
|also_functions=
{{LSL DefineRow||[[llSensorRepeat]]|}}
{{LSL DefineRow||[[llGetRegionTimeDilation]]|}}
{{LSL DefineRow||[[llGetTime]]|}}
|also_events={{LSL DefineRow||[[timer]]|}}
|also_tests
|also_articles
|notes=*[http://community.secondlife.com/t5/LSL-Scripting/quot-on-mouselook-quot/m-p/768291#M545 Notes on minimum practical llSetTimerEvent values], Second Life forum, 2011-03-21
|permission
|negative_index
|sort=SetTimerEvent
|cat1=Script
|cat2=Time
|cat3
|cat4
}}

Attachment

2013-09-24T16:25:52Z

Stickman Ingmann: Added attachment point list, and their associated bones.

Talk:LlGiveInventoryList

2013-09-13T05:44:08Z

Stickman Ingmann: Silent limit of 512 items maybe?

== Editing ==
>> # If inventory cannot be copied then an error is shouted on DEBUG_CHANNEL.

This sucks the big one compared to the elegant, clear, precise English that was in LSL wiki:

llGiveInventoryList can only give items which the object owner has copy permission on.

But one, of course, doesn't dare change it lest Madame sweep in her broom to set it back to the more obscure and exclusive. [[User:Chaz Longstaff|Chaz Longstaff]] 01:38, 20 October 2010 (UTC)

: I can see you are upset and I would like to rectify the situation. Is this grudge specific to an edit you made to an LSL Portal article that was reversed? It's been more than a year since you've edited an LSL article. I've looked over the last few edits you made to LSL Portal articles and I'm just not finding examples of this. If you could point out more instances of obscure text I will try to expand them into something less obscure. I hope {{User|Cerise Sorbet}}'s edit made this instance more clear. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 15:48, 20 October 2010 (UTC)

== Sample ==

Considering there were several edits of the sample script, what should the sample script be? Should we have multiple? The current script gives away it's contents. It used to say it was an unpacker in it's description, but I corrected that. If we want an unpacker, then the sample should be different (and check to make sure the toucher is the owner). If we want a script that checks the flags to ensure they are the correct permission, that seems like a good sample for [[llGetInventoryPermMask]]. [[User:Kunnis Basiat|Kunnis Basiat]] 15:43, 24 December 2008 (UTC)

== Issues ==
Issue Link At Bottom Leads To

llGetInventoryKey returns NULL_KEY when referencing a notecard that's empty

[[User:Adicted Waco|Adi]] 16:59, 20 April 2009 (UTC) Forgot To Sign

Template Was Wrong, 868 Template Lead To 4050
And Yay I Learned About Templates Today
[[User:Adicted Waco|Adi]] 17:12, 20 April 2009 (UTC)

:Sorry about that, when creating those I just copy and paste from one of the others... and I guess I forget. I've been meaning to make it auto-detect the issue handle so it doesn't have to be inserted (also thinking about doing this with the LSL Constants template, where I sometimes make the same mistake). -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 13:31, 21 April 2009 (UTC)

"Group deeded objects cannot use this function, the error "Group owned objects cannot give inventory." is shouted on DEBUG_CHANNEL" This does not seem to be correct. Testing, a deeded object happily hands out inventory lists to avatars (whether they are in the group or not). [[User:Tali Rosca|Tali Rosca]] 20:36, 5 August 2009 (UTC)

There seems to be a limit to items that can be given. I'm going to guess it's 512 items. Try to llGiveInventoryList greater than this limit of several hundred items and it results in silent failure. If someone wants to find the exact count that would be useful to add to the documentation. [[User:Stickman Ingmann|Stickman]] 22:44, 12 September 2013 (PDT)

Talk:LlSetKeyframedMotion

2013-06-18T17:44:47Z

Stickman Ingmann: Explanation of how to "animate" a keyframed object.

== Animation Types ==
Instead of setting integer Loop, let's reuse animation flags that was built for llSetTextureAnim function as list to combine flags usage.<br>
[[LOOP]] [[REVERSE]] [[PING_PONG]] [[SMOOTH]] [[ROTATE]] [[SCALE]] and maybe add another flag <u>POSITION</u>(0x80)?
----
;[[LOOP]]
: Starts from the beginning to the end and returns back to the beginning to start again.

;[[REVERSE]]
: Played backward in following order of the list.

;[[PING_PONG]]
: Starts from the beginning to the end and play backward back to the beginning to start again.

;[[SMOOTH]]
: Could be used as another suggestion between sliding to the next target instead of "llSetPos"-like frames.

;[[ROTATE]], [[SCALE]], and <u>POSITION</u>
: Allow user to trim list down a bit without the needs to add all three at the same time. (Might be a wishful thinking though.)
----
Generally allow users to develop system that could have more than one LlSetKeyframedAnimation function call, long as it's not using same axis/scale/position again, which overrides the first of that same flag. One function call use position and second function call use rotation and scale for a type of event call.

I must point out a discussion about stopping, how do to about it. At the moment, suggesting use <u>STOP</u>(0x00) with combination of any flag from above? --[[Image:Nacon-tag.jpg]] '''[[User:Vincent_Nacon|₪]]''' 03:07, 31 August 2011 (PDT)

:These are great suggestions. I'd make a few tweaks, though:
:*Only [[LOOP]], [[PING_PONG]], and maybe [[REVERSE]] make sense here ([[SMOOTH]] is implicit in the way keyframing works--it is always a smooth interpolation)
:*[[ROTATE]] and <u>TRANSLATE</u> make sense and are a good way to reduce the size of the lists required. However, it would not be feasible to support multiple merging the keyframe sets from different calls (e.g., one call with [[ROTATE]] and one with <u>TRANSLATE</u>)
:*[[SCALE]] is not possibly to implement for physical objects in a way that ensures satisfactory performance. Modifying the scale of a physics shape requires (in simplified terms): (1) rebuilding the shape from scratch, (2) removing the object from the world, (3) applying the new shape to the object, and (4) adding the object back into the world. #1, 2, and 4 are all expensive operations.
:To stop the animation, you could simply pass in an empty list of keyframes.
:[[User:Falcon Linden|Falcon Linden]] 19:11, 6 September 2011 (PDT)

::As to how to supply these to the function, how about <code>[..., ANIM_FLAGS, integer flags, ...]</code>. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 11:01, 8 September 2011 (PDT)

:::About SMOOTH, I simply meant when it's not flagged to have SMOOTH, it would just skip straight to the next frame, no animating between the two frames.

:::As for ROTATE and POSITION(TRANSLATE), treat them separately instead of merging them as one. Which also would cut down the list further when you don't have to have a data at fixed "frame" from where they should perform.

:::I knew SCALE was a wishful thinking... Maybe only applied to phantom/attachment/hud prims, where physic doesn't apply? People are gonna want something like this for visual display. --[[Image:Nacon-tag.jpg]] '''[[User:Vincent_Nacon|₪]]''' 09:35, 26 September 2011 (PDT)

== Interpolation ==

I've got a couple ideas for interpolation:
# Separate flags for configuring interpolation mode for position and orientation parameters. Defaults being LERP and SLERP respectively. Also some flags that provide smoother acceleration.
# Allow the user to instead of supplying a vector or a rotation parameter in the list to supply a float, which should be in the range [0, 1] indicating a proportional interpolated position/orientation between previous and future frames. aka B-Frames
#* So [<0,0,0>, <0,0,0,1>, 0.0, 0.25, 0.0, 0.5, <4,0,0>, <0,0,0,1>, 1.0]
#** So by 0.5 seconds, the position is only <1,0,0> not, <2,0,0> and by 0.75 seconds it would be at <3,0,0>.
#* There is no real reason to restrict the user to the [0, 1] range, and the user may want to overshoot the end so they can mimic oscillating about the end point before reaching it (and having to calculate out the frames).
-- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 11:01, 8 September 2011 (PDT)
:Hey Strife,
:Your suggestion has some merit, but also comes with a few major drawbacks:
:#It makes the list more confusing to understand (and more error-prone to process)
:#It significantly complicates interpretation and processing of the keyframes (which, right can, can be almost directly passed to Havok for application to the physics body)
:#It's just plain harder to implement. This is important because, most likely, if this method comes to fruition, it will be implemented exclusively by yours truly and exclusively in my free time (aka when I'm not working on something else at LL and/or on weekends/evenings.) Since I'm only willing to give up so much of my free time to developing these features, we need to keep them as simple as possible. :)
:Also, it's worth pointing out that accelerations will always be infinite or zero. That is, the object will always have constant linear and angular velocity and it will switch to new linear/angular velocities in a single simulation frame (aka infinite acceleration). Doing it any other way would remove all benefit from using Havok's keyframing system and would be equivalent to implementing a full-blown object animation system (which is not currently feasible). Surprisingly, I discovered that for reasonable velocities, these limitations don't have any noticeable visual artifacts.
:All that said, it is possible that such a feature could be added in the future given the flexibility of the options list parameter.
:[[User:Falcon Linden|Falcon Linden]] 18:51, 8 September 2011 (PDT)

::No sweat really, it can be done by preprocessing the list in user code. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 19:19, 8 September 2011 (PDT)

:::You may want to take a look at {{JiraIssue|SCR-373}}; bezier curves are by far my favourite method for creating custom smoothed motion between two keyframes, and could significantly reduce the number of keyframes required by more complex animations. I've been using them for some time now in CSS3 and it's just so much easier to manage, and actually really easy to implement. <br/>-- '''[[User:Haravikk_Mistral|Haravikk]]''' <sup><small>([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]])</small></sup> 04:56, 22 July 2012 (PDT)

== KFA_DATA ==

I'm thinking that if KFA_DATA is required, than it shouldn't be part of the options but a function parameter. Does it need to be explicit? It could be inferred from the types in the list but that limits future syntax changes. On the flip side having it in the options simplifies serialization as you can then store them in the same list as opposed to a separate variable that must be (de)serialized along with the lists.

-- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 11:14, 16 September 2011 (PDT)

== some thoughts ==

just heard about this, sounds really nice, a few thoughts came up when it got mention on the forums...

"Animation" seems kinda misleading to what it does as when on think 3d they tend to think of animation more like changing the relation of multiple parts, I suggested "Motion", Kaluura suggested "Target". mostly minor either way as long as it does what's expected of it.

Kalurra mentioned a callback, although I suppose the "Target" functions could work for that, they are all global, which both limits the use of the function and forces extra calculations to get the global frame.

and finally a minor tweak, allowing blank list items to be cast as the appropriate "zero", so that the list is more collapsible for items that don't change during a frame... that would allow the structure to be retained, but be less overhead for the script (I think).<br/>-- '''[[User:Void_Singer|Void]]''' <sup><small>([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]])</small></sup> 23:30, 17 September 2011 (PDT)

== llSetPrimitiveAnimation() ==

Just heard about this via {{jira|SCR-203}}, and wanted to point to an older issue of mine in the form of {{jira|SVC-347}}, in case it has anything that needs considering, though this function proposal seems like it may be a better format overall.

I wanted to add that with regards to the timing restriction (no translations faster than 0.1 seconds), surely this restriction could be relaxed if the effect were somehow designated as client-side only, since client-side animation is the more desirable case for a lot of applications that would otherwise be very wasteful if done on the simulator-side. In particular, a lot of current animating objects such as prim NPC's could be replaced with a suitable prim-animation feature, however there wouldn't be much point if the simulator-side is still a bottleneck for lag, as even without the script-delay issue any network lag could still mess up effects. Related to this is the consideration of synchronising time features, both for simulator-side and client-side effects, as per {{Jira|SCR-13}} and {{Jira|SVC-4897}}, as this could give us a better idea of what state the animation will be in at a particular moment.

Lastly, one other useful addition may be a PAUSE command that can set the object to a specific keyframe, or a LOOP_UNTIL or some such command; since a script cannot guarantee the state of the animation since 5 seconds of animation and 5 seconds of script wait or timer-delay may not always coincide as closely as expected.<br/>-- '''[[User:Haravikk_Mistral|Haravikk]]''' <sup><small>([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]])</small></sup> 12:06, 20 September 2011 (PDT)

:In particular, what I'd like to see is the use of LOOP, PING_PONG etc. within the key-frames list. As these are integer constants it should be perfectly safe to do as the keyframes themselves are vectors and/or rotations and floats. In this way, if an integer is encountered, then it will simply set a new state for the rest of the animation. This could potentially be done using a bit-filed like so:
<lsl>llSetKeyframedAnimation(
[
COMMAND, PLAY, // Start the animation
FLAGS, SMOOTH | EASE_IN, // Set flags for all following key-frames to use smooth interpolation, and "ease-in" (decelerating movement)
LOOP, 3, // All following key-frames will loop a total of 3 times
<0, 0, 10>, ZERO_ROTATION, 5.0, // Move up 10m in 5 seconds
<0, 0, -10>, ZERO_ROTATION, 5.0, // Move down 10m in 5 seconds
PING_PONG, 2, // End of previous loop, all following key-frames will ping-pong a total of 2 times (frames will play forward, then play back, then stop)
<5, 0, 0>, ZERO_ROTATION, 1.0, // Move right 5m in 1 second
<-5, 0, 0> ZERO_ROTATION, 1.0, // Move left 5m in 1 second
],
TRUE // Animation is performed client-side only
);
llSleep(60.0);
llSetKeyframedAnimation([COMMAND, PLAY], TRUE); // Play the animation again client-side</lsl>
:Either that, or a key-frame constant can be used, with two choices, so that one constant may be used to specify a short-hand keyframe (vector only or rotation only) or a full keyframe.<br/>-- '''[[User:Haravikk_Mistral|Haravikk]]''' <sup><small>([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]])</small></sup> 12:20, 20 September 2011 (PDT)

== TRANSLATE: Regions or Local? ==
Starting to realize that we also might need an integer to set this Local or not. Any thoughts? --[[Image:Nacon-tag.jpg]] '''[[User:Vincent_Nacon|₪]]''' 13:18, 4 November 2011 (PDT)

:The problem is what happens when you add in KFM_ROTATION? Unless you have sat down and solved the equations for the movement, you won't know where your prim will end up. What you really want is the movement to be local to some starting rotation, not a continuously changing rotation. For the sake of everyones sanity (especially the implementors) there should be a <code>[KFM_SHIFT_ROT, rotation rot]</code> and <code>[KFM_SHIFT_POS, vector pos]</code> flags to allow the user to shift the entire animation, otherwise you have to translate ever single frame in the list if you want to tweak it... not fun. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 16:58, 5 November 2011 (PDT)
:: <span style="text-decoration:line-through;"> Yes, it's not easy but I would personally would want that option. KFM_SHIFT_POS and KFM_SHIFT_ROT sounds like a great idea than adding a integer. </span> --[[Image:Nacon-tag.jpg]] '''[[User:Vincent_Nacon|₪]]''' 12:47, 8 November 2011 (PST)
:::I like this idea. Please file a jira feature request and mention this post so it can be assigned to me. I will try to implement it when I have time, but no promises on when that might be. I wonder, though: perhaps a more general method <code>list llTransformList(list pointsAndRotations, vector translation, rotation rot)</code> would be more widely useful at the cost of some script memory?[[User:Falcon Linden|Falcon Linden]] 12:01, 22 November 2011 (PST)
Ok, I was slightly misunderstanding the Shift suggestion and came to realize that it isn't going to solve most problems for those who wanted absolute coordinates. I honestly wouldn't want shifting the set around by local coordinates, could make LSL writing more complex as it is when making correction due to prim drifting in 45 FPS over time. --[[Image:Nacon-tag.jpg]] '''[[User:Vincent_Nacon|₪]]''' 13:27, 22 November 2011 (PST)

:I must apologize, I have been unable to get in-world to do my own testing. So my knowledge is derived from the documentation and stale first hand experience from over several years of SL experience. After watching [http://www.youtube.com/watch?v=tkD_kf-qouw Moving Platforms, Carousels (llSetKeyframedMotion)] I now have a better understanding of how the function is implemented. I realize now my previous suggestion was not well informed.

:I wonder why I didn't see this earlier, by describing the frames as changes in position/rotation over time, drift is inevitable. The problem is that the vectors & rotations are made of floats, the components of positions look like floats but they lack the precision (even if they didn't there are rounding issues with float math). So the translation from change in position to global position results in the rounding to a valid position. Since everything is local to the previous frame, it compounds.

:There are three ways to implement this:
:# Simulator global coordinators
:#* Drift is limited to rounding the positions to valid positions, a frame may drift but it won't compound
:#* Requires the script to recalibrate the animation when the object is rezzed or risk flying off very quickly.
:#* llTransformMotionList gets used during every call.
:# Describe frames as changes from the previous frame.
:#* Drift compounds.
:# Coordinates local to starting position. (as changes from the starting position)
:#* Drift is limited to rounding the positions to valid positions, a frame may drift but it won't compound
:#* No recalibration needed when rezzing
:#* llTransformMotionList is really only needed to full on edit the animation, not during regular use.

: Implementation 3 gives an added bonus: If you decided to write an editor/script that translates Implementation 2 animations into Implementation 3 animations, you can see the drift and correct it.

: I hate to say this but rotation drift is going to be a bigger issue than position drift. Quaternion multiplication is not pretty. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 22:43, 26 November 2011 (PST)

== Playback speed ==

<code>[KFM_SPEED, float speed]</code> default value for ''speed'' is 1.0, this way you can slow down or speed up the animation. Not sure if this should instead or as well be a feature of llTransformMotionList. Easy to implement, just multiply speed by frame duration. Pretty sure negative speed should not be allowed. Negative speed either means reversing the change in position vectors or playing the animation in reverse, and I don't know which. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 22:43, 26 November 2011 (PST)

s are described by values that are in a set.

== Queuing frames on the fly ==

Lets say you were using this for a train, and you want to be able to flip switches to change which track the train goes down. When you flip the switch you need to update the keyframed motion without stopping the train. What you really want to do is dynamically add frames onto the end of the animation so that when you get close to a switch ([[llTarget]]?) you read the switch and add on the extra frames. This usage could be added with a new flag KFM_CMD_QUEUE. Queuing would imply that old frames that have been processed would be discarded at some point, it would be a memory leak otherwise. With queuing you can really only do KFM_FORWARD or KFM_REVERSE, it's too complicated to do either kind of looping. For queuing you really need [[LSL Constants/ReturnStatus|success value]] to be returned by the function. Maybe it should be a separate function: <code>integer llQueueKeyframedMotion(...)</code>. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 22:43, 26 November 2011 (PST)

== external linking? ==

seems like a bad idea to link to forums threads which are historically unstable in their address... shouldn't we just quote the source and leave it at that?<br/>-- '''[[User:Void_Singer|Void]]''' <sup><small>([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]])</small></sup> 20:20, 18 November 2011 (PST)

:Is the new forum that hard to link into? -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 20:52, 19 November 2011 (PST)

not hard per say, but not exactly stable either. Previous links to the official forums have been broken (as well as much of their script related content), and even in the current software, pathing of links is tied to forum and section names (which have changed majorly at least twice in this software) rather than post ID. my concern is that the information it's supposed to point to will get lost along the way, and in this case, is already duplicated (except for the source, Falcon), which seems to be the point of the link<br/>-- '''[[User:Void_Singer|Void]]''' <sup><small>([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]])</small></sup> 21:53, 22 November 2011 (PST)

== Normalized rotation ==

I just noticed the optimization and helpful comment that Strife added to my note regarding normalized rotations on the Rotation page elsewhere in the wiki. This is one of the cases that I had in mind as I wrote that little section. In trying to resolve a question about KFM in the LSL Forum, I discovered that '''''llSetKeyframedMotion''''' sometimes spits out an inscrutable run-time error message unless you feed it normalized rotations. The example here is one such case. Thanks to Strife. I replaced my original user-defined function with the more compact version that he substituted on the Rotations page. [[User:Rolig Loon|Rolig Loon]] 13:34, 12 February 2012 (PST)

:You're welcome :) I've been watching this unfold, sounds annoying. Please keep us up to date on changes to this. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 21:45, 12 February 2012 (PST)

:P.S. Once upon a time I put in a feature request for Quaternion-Float multiplication & division operators but it got shelved because it might break existing code (and before that I requested more functions for working with quaternions but that request may be lost to the sands of time... or in the script forum archive, not sure which).

Is this quaternion normalizing related to the Key Framed Motion only or what? I never, NEVER had a runtime error with a quaternion not being normalized with the Key Framed Motion or any other LSL function. [[User:Dora Gustafson|Dora Gustafson]] 10:45, 23 February 2012 (PST)

The example that includes quaternion normalizing will discourage any newcomer and many other good people including myself, because it takes focus away from the subject of the article. If included it should be said under caveats or bugs in my opinion. [[User:Dora Gustafson|Dora Gustafson]] 10:45, 23 February 2012 (PST)

:Normalization should only be necessary for math or functions that might return non-normalized ones. so far as I can see, that's direct manipulation of elements, or the functions llAxis2Rot and llRotBetween. all other LSL functions will always return normalized rotations, and math (* or /) on normalized rotations results in normalized rotations. The caveat here should probably only state that it needs normalized rotations, and there should be a caveat on each of the functions or operations that might not return them. The first example shouldn't need normalization since both sources are already normalized.<br/>-- '''[[User:Void_Singer|Void]]''' <sup><small>([[User_talk:Void_Singer|talk]]|[[Special:Contributions/Void_Singer|contribs]])</small></sup> 14:33, 26 February 2012 (PST)

:I, too, am not fond of the way it's sort of alluded that LSL may randomly and uncontrollably wreck rotations, and that everybody should just start using the "magical normalization function" on all rotations. The "some circumstances" should be spelled out clearly. There is the llAxes2Rot on non-orthogonal vectors or the llRotBetween between different magnitudes, but I suspect the primary reason people report seeing it comparatively often is because they read the quaternions from a text representation (such as a notecard), where the components can be rounded off.<br/>[[User:Tali Rosca|Tali Rosca]] 19:12, 9 May 2012 (PDT)

::That is likely the case and they haven't used my [[Float2Hex#Helper_Functions|Rot2Hex]] function to perfectly serialize the rotation! Sorry for the shameless plug but serialization is important. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 22:43, 9 May 2012 (PDT)

the function provides a list of displacements in region coordinates rather than positions [[User:Sigma Avro|Sigma Avro]] 13:39, 5 April 2012 (PDT)

== Client-Side Motion? ==

I think that this function would be particularly useful if it could be used to define client-side motion, as many animations won't necessarily require the object to actually move. This could easily be achieved with a suitable option to make the effect client-side as opposed to server-side only, in which case the object wouldn't physically move, only visually. If it is done, then I'd like to pitch {{jira|SVC-4897}} since it would allow the animation (and potentially loads of other effects) to work better on the viewer side; eliminating the need for messy scripted synchronisation, and avoiding lag-related issues.<br/>-- '''[[User:Haravikk_Mistral|Haravikk]]''' <sup><small>([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]])</small></sup> 09:18, 11 May 2012 (PDT)

:I just wanted to add as well that client-side motion is also particularly important as it would allow the function to be applied to objects that do no use prim-equivalency; since the effect would be client-side only it would not be as demanding, and the viewer can easily reduce the detail of the animation if necessary. I just wanted to ask as well what exactly the state of this is; the function is not recognised by the viewer's LSL editor, though it does compile, at least in LeTigre regions (which my home region belongs to) so I'm curious if it's live yet? If it is a live change then I'll have to look at filing a JIRA issue for client-side integration. <br/>-- '''[[User:Haravikk_Mistral|Haravikk]]''' <sup><small>([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]])</small></sup> 03:43, 12 May 2012 (PDT)

::I wanted to note that I added a proposal under {{JiraIssue|SCR-346}} to retroactively add this ability; animation is fine, but the fact is that nearly all things I'd like to use it for could be handled a lot more efficiently within the viewer as I don't really have any need for the objects to physically go anywhere. As noted in the proposal the advantage of the client-side option is that it eliminates all work from the simulator, leaving each viewer to decide how frequently to update the animation. It would also allow animation of non equivalency prims, and child-prims. In the proposal for child-prims I noted that these would occur locally; i.e - everything is relative to the root. This would allow simple environmental animation without generating huge load; things such as moving pistons, and such. <br/>-- '''[[User:Haravikk_Mistral|Haravikk]]''' <sup><small>([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]])</small></sup> 05:04, 22 July 2012 (PDT)

== MINIMAL TIME ==

Script warming errors indicate that minimal value for time is to be > 0.1 seconds.
Not clear what >0.1s means exactly since according to test the minimal value is 0.112 in an empty sim with zero lag.[[User:Sigma Avro|Sigma Avro]] 12:50, 12 August 2012 (PDT)

Not sure where it becomes 5/45 in the programming, but it was likely originally written as 0.1 and becomes 5/45 due to per-frame rounding. Either that or it was written and always had been 5 frames, and someone thought it was simpler to make the error say '0.1'. [[User:Acheron Gloom|Acheron Gloom]] 14:11, 12 August 2012 (PDT)

== Moving linkset while animating ==
Attempting to modify the any prims of a linkset while it's playing a keyframed motion will result in the following error:

'''Cannot use a script to move a linkset while it is playing an animation.'''

I was surprised had not only not been documented, but had no workaround mentioned. In my examination, this function can potentially be used as a sort of "pathfinding lite," or a replacement when dynamic pathfinding is unavailable. As such, it would inevitably used for some critter that needs to play some sort of prim-based animation while sliding along. I've updated the main page with my findings and solutions, but I wanted to mention them in more detail here.

First, the keyframed motion can be paused by calling:
<lsl>llSetKeyframedMotion([],[KFM_COMMAND,KFM_CMD_PAUSE])</lsl>
Easy peasy. This also works in a second script, if for some reason you can't call it from the original script. Keyframed motion is like particles and hovertext in that it's a prim property, and any script can modify the prim properties without knowing what other scripts are up to. The empty keyframes list doesn't actually clear the keyframes stored.

Restarting the keyframed motion is done with this command:
<lsl>llSetKeyframedMotion([],[KFM_COMMAND,KFM_CMD_PLAY])</lsl>
But be careful! If you've previous called the function with two blank lists to "stop" the motion entirely, this will restart it. It looks like two blank lists is merely a shortcut to pausing, not a termination and clearing of the keyframe list.

Second, for the actual "animating" of your critter. You'll want to use [[llSetLinkPrimitiveParamsFast]]. Since your goal should be not to interrupt the smooth movement (unless it's not your goal) you should lump all of your prim shifting into one call using [[PRIM_LINK_TARGET]], making one list with all your property changes for all prims. Once the list is compiled, pause the motion, call the llSLPPF function, and restart the motion. In my testing, if this all manages to happen in one frame, the motion will not even be interrupted and remain smooth.

Hopefully this helps someone else who was in a similar spot as me, and found themselves encountering an unexpected error. --[[User:Stickman Ingmann|Stickman]] 10:44, 18 June 2013 (PDT)

LlSetKeyframedMotion

2013-06-18T17:26:21Z

Stickman Ingmann: improved formatting of previous edit

{{LSL_Function
|inject-2={{Issues/SCR-345}}{{Issues/SCR-346}}{{Issues/SVC-7796}}{{Issues/SCR-373}}
|func=llSetKeyframedMotion
|func_id=?
|func_desc=Specify a list of times, positions, and orientations to be followed by an object. The object will be smoothly moved between keyframes by the simulator. Collisions with other nonphysical or keyframed objects will be ignored (no script events will fire and collision processing will not occur). Collisions with physical objects will be computed and reported, but the keyframed object will be unaffected by those collisions. (The physical object will be affected, however.)
|func_sleep
|func_energy
|func_footnote
|p1_type=list|p1_name=keyframes|p1_hover=Strided keyframe list of the form: [vector position, rotation orientation, float time]
|p1_desc=Strided keyframe list of the form:
* ''vector'' position (optional via [[KFM_TRANSLATION]] and [[KFM_DATA]])
* ''rotation'' orientation (optional via [[KFM_ROTATION]] and [[KFM_DATA]])
* ''float'' time

Each keyframe is interpreted relative to the previous transform of the object. For example, consider the following list of keyframes: [<0, 0, 10>, [[ZERO_ROTATION]], 5, <0, 0, 0>, [[ZERO_ROTATION]], 5, <0, 0, -10>, [[ZERO_ROTATION]], 5]. This would cause the object to move up 10m over the course of 5s. It would then remain at the location for 5s before moving down 10m over the course of another 5s.
Time values must be 1/9s. or greater.
Linear and angular velocities will be clamped to limits set by the simulator (values TBD).
An empty list will terminate any keyframed animation currently playing.
|p2_type=list|p2_name=options|p2_desc=modifiers and future options
|spec=
The following flags will be supported within the ''options'' list:
*[[KFM_MODE]] followed by one of: [[KFM_LOOP]], [[KFM_REVERSE]], [[KFM_FORWARD]], or [[KFM_PING_PONG]] will specify the playback mode. Defaults to [[KFM_FORWARD]]. Must be specified when the keyframe list is provided.
*[[KFM_DATA]] followed by a bitwise combination of: [[KFM_TRANSLATION]] and [[KFM_ROTATION]]. By default both rotations and translations must be provided. If you specify one or the other, you should only include translations or rotations in your keyframe list. Must be specified at the time the keyframe list is provided.
*[[KFM_COMMAND]] followed by one of: [[KFM_CMD_STOP]], [[KFM_CMD_PLAY]], [[KFM_CMD_PAUSE]]. STOP will pause the animation AND reset it to the beginning. PAUSE will pause the animation without resetting. PLAY will resume a paused or stopped animation.
Note that if [[KFM_COMMAND]] is provided in the options list, it must be the only option in the list, and cannot be specified in the same function call that sets the keyframes list.

Inter-region movement is supported; simply specify a target keyframe that would place the object outside the sim boundaries and it will cross over. This seems to provide the same effect as pausing the animation when it is in limbo between the two regions, but the viewer continues to interpolate its movement. It will jump back to the sim border and continue on the same speed, although the time between waypoints will be increased due to the sim crossing. Make sure you factor this into your system.

Since keyframed motion is a prim property rather than restricted to the script that called it, you can use multiple scripts to control, pause, or restart the same keyframed motion without passing the original keyframe list provided. Just pass an empty list for keyframes list, and the [[KFM_COMMAND]] followed by the command in the options list.
|constants={{LSL Constants/KeyframedMotion|set|table=*}}
|caveats=
*This function does not work in attachments.
*This function can only be called on NON-physical objects. In the future it could be extended to support physical objects, but this is more complicated as collisions could prevent the object from reaching its goal positions on time.
*You cannot use scripts to move any prim in the linkset while the keyframed motion is active. If you must, first pause it with <lsl>llSetKeyframedMotion([],[KFM_COMMAND],[KFM_CMD_PAUSE])</lsl> and restart it with [[KFM_CMD_PLAY]] when done.
*Collisions with avatars affect the angular movement of the object and it may not reach the final rotation.
*This function can only be called on the root prim of a linkset.
*This function requires the linkset to use the Prim Equivalency system. However, it keyframed objects will not receive the dynamics penalty and can have a physics weight of up to 64.
*llSetKeyframedMotion is implemented in terms of frames and not real time. To avoid a drift from the expected positions and rotations, use times which are integer multiples of 1/45, e.g. 20.0/45.0, 40.0/45.0, 90.0/45.0, etc. [http://community.secondlife.com/t5/LSL-Scripting/llSetKeyframedMotion-turning-a-corner/td-p/1225219 Forum Thread]
**Natural drift can still occur; for best results use [[moving_end]] to determine when the animation has ended and confirm the target position with [[llSetPos]].
*There are a few bugs in the avatar animation system that may cause strange looking animations to play when standing on a moving platform (e.g., walking in place, feet-at-pelvis). We hope to fix these in the future, but doing so is out of scope for this feature.
*As with dynamic objects, objects moving using this function are paused when they are selected by an avatar with adequate permissions (object owner, passenger, etc). When such an avatar deselects the object, motion resumes, even if the object had been paused using [[KFM_CMD_PAUSE]].
*A Key Framed Motion is a '''prim property''' in some respect. When a KFM_LOOP or [[KFM_PING_PONG]] is initiated not only '''the motion''' but also the '''prim position''' is '''preserved after the script is removed'''. I.E. The prim will continue what motion it had and it will snap back when moving is attempted. It will not survive take and copy. It will survive server restart.
*Inter region movement is far from perfect. Crossing from sim 1 to sim 2 using a Key Frame list with numerous frames on a curved path will pick up conspicuous errors on the crossing and when reversed by [ [[KFM_MODE]], [[KFM_REVERSE]] ] the object will stay in sim 2 and never return to sim 1
|examples=
<lsl>
// If your client is not mesh-aware use the following line:

llSetLinkPrimitiveParamsFast(LINK_THIS,
[PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_CONVEX]);
</lsl>
<lsl>
llSetKeyframedMotion(
[<0.0, 0.0, 10.0>, 5,
<0.0, 0.0, -10.0>, 5],
[KFM_DATA, KFM_TRANSLATION, KFM_MODE, KFM_PING_PONG]);
</lsl>
<lsl>
llSetKeyframedMotion(
[<0.0, 0.0, 10.0>, llEuler2Rot(<90, 45, 180> * DEG_TO_RAD), 5,
<0.0, 0.0, -10.0>, llEuler2Rot(<270, 225, 360> * DEG_TO_RAD), 5],
[KFM_MODE, KFM_REVERSE]);
</lsl>
==Sample Script - Key Framed Follower==
Under some circumstances, rotations will generate a run-time error unless they are normalized. This script illustrates a way to use llKeyframedMotion to create a follower -- think, for example, of a cart behind a vehicle -- using normalized target rotation.
<lsl>
integer isSensorRepeatOn;

rotation NormRot(rotation Q)
{
float MagQ = llSqrt(Q.x*Q.x + Q.y*Q.y +Q.z*Q.z + Q.s*Q.s);

return
<Q.x/MagQ, Q.y/MagQ, Q.z/MagQ, Q.s/MagQ>;
}

default
{
state_entry()
{
llSetLinkPrimitiveParamsFast(LINK_ROOT,
[PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_CONVEX,
PRIM_LINK_TARGET, LINK_ALL_CHILDREN,
PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_NONE]);
}

touch_start(integer total_number)
{
isSensorRepeatOn = !isSensorRepeatOn;

if (isSensorRepeatOn)
{
// PUBLIC_CHANNEL has the integer value 0
llSay(PUBLIC_CHANNEL, "Sensor repeat switched on!");

llSensorRepeat("", "91b39b5b-13b1-2517-273a-67360b842c02", SCRIPTED, 10.0, PI, 0.1);
}
else
// {
llSensorRemove();
// }
}

sensor(integer num_detected)
{
vector ownPosition = llGetPos();
rotation ownRotation = llGetRot();
vector detectedPosition = llDetectedPos(0);
rotation detectedRotation = llDetectedRot(0);

llSetKeyframedMotion(
[(detectedPosition - ownPosition) + <-1.0, 0.0, 0.2>*detectedRotation,
NormRot(detectedRotation/ownRotation), 0.12],
[]);
}
}
</lsl>
==Universal Hinged Motion in 8 Key Frames==
The script will turn a box prim around one edge parallel to the prim's Y-axis<br>
The script will work for any prim orientation<br>
Note that the smallest accepted time per frame is 1/9S=0.11111111S and NOT 0.1S<br>
<lsl>
float angleEnd = PI_BY_TWO;

float speedInMetersPerSecond = 0.2;

float numberOfKeyframes = 8.0;
float step = 0.0;

list listOfKeyframes;

vector V;
integer open = TRUE;

vector startPosition;
rotation startRotation;

float motion_time(float mt)
{
mt = llRound(45.0*mt)/45.0;

if (0.11111111 < mt)
return mt;

// else
return 0.11111111;
}

default
{
on_rez(integer start_param)
{
llResetScript();
}

state_entry()
{
llSetMemoryLimit(0x2000);

llSetLinkPrimitiveParamsFast(LINK_THIS,
[PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_CONVEX]);

vector scale = llGetScale();
startPosition = llGetPos();
startRotation = llGetRot();

vector v1 = 0.5*scale*startRotation;

rotation deltaRot = llEuler2Rot(< 0.0, angleEnd/numberOfKeyframes, 0.0>);

while (step < numberOfKeyframes)
{
vector ownRot2Left = llRot2Left(llGetRot());

V = v1*llAxisAngle2Rot(ownRot2Left, angleEnd*step/numberOfKeyframes);
V = v1*llAxisAngle2Rot(ownRot2Left, angleEnd*(step + 1.0)/numberOfKeyframes) - V;

listOfKeyframes += [V, deltaRot, motion_time(llVecMag(V)/speedInMetersPerSecond)];

step += 1.0;
}
}

touch_start(integer num_detected)
{
llSetKeyframedMotion([], []);

if (open)
{
llSetLinkPrimitiveParamsFast(LINK_THIS,
[PRIM_POSITION, startPosition,
PRIM_ROTATION, startRotation]);

llSetKeyframedMotion(listOfKeyframes, []);
}
else
// {
llSetKeyframedMotion(listOfKeyframes, [KFM_MODE, KFM_REVERSE]);
// }

open = !open;
}
}
</lsl>
After editing prim position, rotation and/or size the script should be reset in order to update the motion
==More Examples==
# [https://wiki.secondlife.com/wiki/User:Dora_Gustafson/Pendulum_motion Pendulum motion] Simple Pendulum Motion in 24 Key Frames, a good motion for a swing
# [https://wiki.secondlife.com/wiki/User:Dora_Gustafson/Harmonic_Oscillator_motion Oscillator motion] Motion in 12 Key Frames
|notes=
Potential Use Cases:
* Elevators
* Moving platforms
* Trains/Fixed-Track Vehicles
* Moving doors/walls/gates
* Windmills and other machines
Targeted coordinate systems: The Translation is in Global coordinates, the Rotation in Local coordinates
* Say: a move on the X-axis will move the object along the global, region X-axis no matter how the object is rotated
* Say: a rotate around the X-axis will rotate the object around it's local, prim X-axis no matter the object's rotation
* When the object is not rotated in the global system you won't notice the difference
|cat1=Physics
|cat2=Movement
|cat3
|cat4
}}

LlSetKeyframedMotion

2013-06-18T17:23:59Z

Stickman Ingmann: Added limitations and abilities that were not documented

{{LSL_Function
|inject-2={{Issues/SCR-345}}{{Issues/SCR-346}}{{Issues/SVC-7796}}{{Issues/SCR-373}}
|func=llSetKeyframedMotion
|func_id=?
|func_desc=Specify a list of times, positions, and orientations to be followed by an object. The object will be smoothly moved between keyframes by the simulator. Collisions with other nonphysical or keyframed objects will be ignored (no script events will fire and collision processing will not occur). Collisions with physical objects will be computed and reported, but the keyframed object will be unaffected by those collisions. (The physical object will be affected, however.)
|func_sleep
|func_energy
|func_footnote
|p1_type=list|p1_name=keyframes|p1_hover=Strided keyframe list of the form: [vector position, rotation orientation, float time]
|p1_desc=Strided keyframe list of the form:
* ''vector'' position (optional via [[KFM_TRANSLATION]] and [[KFM_DATA]])
* ''rotation'' orientation (optional via [[KFM_ROTATION]] and [[KFM_DATA]])
* ''float'' time

Each keyframe is interpreted relative to the previous transform of the object. For example, consider the following list of keyframes: [<0, 0, 10>, [[ZERO_ROTATION]], 5, <0, 0, 0>, [[ZERO_ROTATION]], 5, <0, 0, -10>, [[ZERO_ROTATION]], 5]. This would cause the object to move up 10m over the course of 5s. It would then remain at the location for 5s before moving down 10m over the course of another 5s.
Time values must be 1/9s. or greater.
Linear and angular velocities will be clamped to limits set by the simulator (values TBD).
An empty list will terminate any keyframed animation currently playing.
|p2_type=list|p2_name=options|p2_desc=modifiers and future options
|spec=
The following flags will be supported within the ''options'' list:
*[[KFM_MODE]] followed by one of: [[KFM_LOOP]], [[KFM_REVERSE]], [[KFM_FORWARD]], or [[KFM_PING_PONG]] will specify the playback mode. Defaults to [[KFM_FORWARD]]. Must be specified when the keyframe list is provided.
*[[KFM_DATA]] followed by a bitwise combination of: [[KFM_TRANSLATION]] and [[KFM_ROTATION]]. By default both rotations and translations must be provided. If you specify one or the other, you should only include translations or rotations in your keyframe list. Must be specified at the time the keyframe list is provided.
*[[KFM_COMMAND]] followed by one of: [[KFM_CMD_STOP]], [[KFM_CMD_PLAY]], [[KFM_CMD_PAUSE]]. STOP will pause the animation AND reset it to the beginning. PAUSE will pause the animation without resetting. PLAY will resume a paused or stopped animation.
Note that if [[KFM_COMMAND]] is provided in the options list, it must be the only option in the list, and cannot be specified in the same function call that sets the keyframes list.

Inter-region movement is supported; simply specify a target keyframe that would place the object outside the sim boundaries and it will cross over. This seems to provide the same effect as pausing the animation when it is in limbo between the two regions, but the viewer continues to interpolate its movement. It will jump back to the sim border and continue on the same speed, although the time between waypoints will be increased due to the sim crossing. Make sure you factor this into your system.

Since keyframed motion is a prim property rather than restricted to the script that called it, you can use multiple scripts to control, pause, or restart the same keyframed motion without passing the original keyframe list provided. Just pass an empty list for keyframes list, and the '''KFM_COMMAND''' followed by the command in the options list.
|constants={{LSL Constants/KeyframedMotion|set|table=*}}
|caveats=
*This function does not work in attachments.
*This function can only be called on NON-physical objects. In the future it could be extended to support physical objects, but this is more complicated as collisions could prevent the object from reaching its goal positions on time.
*You cannot use scripts to move any prim in the linkset while the keyframed motion is active. If you must, first pause it with ''llSetKeyframedMotion([],[KFM_COMMAND,KFM_CMD_PAUSE])'' and restart it with ''KFM_CMD_PLAY'' when done.
*Collisions with avatars affect the angular movement of the object and it may not reach the final rotation.
*This function can only be called on the root prim of a linkset.
*This function requires the linkset to use the Prim Equivalency system. However, it keyframed objects will not receive the dynamics penalty and can have a physics weight of up to 64.
*llSetKeyframedMotion is implemented in terms of frames and not real time. To avoid a drift from the expected positions and rotations, use times which are integer multiples of 1/45, e.g. 20.0/45.0, 40.0/45.0, 90.0/45.0, etc. [http://community.secondlife.com/t5/LSL-Scripting/llSetKeyframedMotion-turning-a-corner/td-p/1225219 Forum Thread]
**Natural drift can still occur; for best results use [[moving_end]] to determine when the animation has ended and confirm the target position with [[llSetPos]].
*There are a few bugs in the avatar animation system that may cause strange looking animations to play when standing on a moving platform (e.g., walking in place, feet-at-pelvis). We hope to fix these in the future, but doing so is out of scope for this feature.
*As with dynamic objects, objects moving using this function are paused when they are selected by an avatar with adequate permissions (object owner, passenger, etc). When such an avatar deselects the object, motion resumes, even if the object had been paused using [[KFM_CMD_PAUSE]].
*A Key Framed Motion is a '''prim property''' in some respect. When a KFM_LOOP or [[KFM_PING_PONG]] is initiated not only '''the motion''' but also the '''prim position''' is '''preserved after the script is removed'''. I.E. The prim will continue what motion it had and it will snap back when moving is attempted. It will not survive take and copy. It will survive server restart.
*Inter region movement is far from perfect. Crossing from sim 1 to sim 2 using a Key Frame list with numerous frames on a curved path will pick up conspicuous errors on the crossing and when reversed by [ [[KFM_MODE]], [[KFM_REVERSE]] ] the object will stay in sim 2 and never return to sim 1
|examples=
<lsl>
// If your client is not mesh-aware use the following line:

llSetLinkPrimitiveParamsFast(LINK_THIS,
[PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_CONVEX]);
</lsl>
<lsl>
llSetKeyframedMotion(
[<0.0, 0.0, 10.0>, 5,
<0.0, 0.0, -10.0>, 5],
[KFM_DATA, KFM_TRANSLATION, KFM_MODE, KFM_PING_PONG]);
</lsl>
<lsl>
llSetKeyframedMotion(
[<0.0, 0.0, 10.0>, llEuler2Rot(<90, 45, 180> * DEG_TO_RAD), 5,
<0.0, 0.0, -10.0>, llEuler2Rot(<270, 225, 360> * DEG_TO_RAD), 5],
[KFM_MODE, KFM_REVERSE]);
</lsl>
==Sample Script - Key Framed Follower==
Under some circumstances, rotations will generate a run-time error unless they are normalized. This script illustrates a way to use llKeyframedMotion to create a follower -- think, for example, of a cart behind a vehicle -- using normalized target rotation.
<lsl>
integer isSensorRepeatOn;

rotation NormRot(rotation Q)
{
float MagQ = llSqrt(Q.x*Q.x + Q.y*Q.y +Q.z*Q.z + Q.s*Q.s);

return
<Q.x/MagQ, Q.y/MagQ, Q.z/MagQ, Q.s/MagQ>;
}

default
{
state_entry()
{
llSetLinkPrimitiveParamsFast(LINK_ROOT,
[PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_CONVEX,
PRIM_LINK_TARGET, LINK_ALL_CHILDREN,
PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_NONE]);
}

touch_start(integer total_number)
{
isSensorRepeatOn = !isSensorRepeatOn;

if (isSensorRepeatOn)
{
// PUBLIC_CHANNEL has the integer value 0
llSay(PUBLIC_CHANNEL, "Sensor repeat switched on!");

llSensorRepeat("", "91b39b5b-13b1-2517-273a-67360b842c02", SCRIPTED, 10.0, PI, 0.1);
}
else
// {
llSensorRemove();
// }
}

sensor(integer num_detected)
{
vector ownPosition = llGetPos();
rotation ownRotation = llGetRot();
vector detectedPosition = llDetectedPos(0);
rotation detectedRotation = llDetectedRot(0);

llSetKeyframedMotion(
[(detectedPosition - ownPosition) + <-1.0, 0.0, 0.2>*detectedRotation,
NormRot(detectedRotation/ownRotation), 0.12],
[]);
}
}
</lsl>
==Universal Hinged Motion in 8 Key Frames==
The script will turn a box prim around one edge parallel to the prim's Y-axis<br>
The script will work for any prim orientation<br>
Note that the smallest accepted time per frame is 1/9S=0.11111111S and NOT 0.1S<br>
<lsl>
float angleEnd = PI_BY_TWO;

float speedInMetersPerSecond = 0.2;

float numberOfKeyframes = 8.0;
float step = 0.0;

list listOfKeyframes;

vector V;
integer open = TRUE;

vector startPosition;
rotation startRotation;

float motion_time(float mt)
{
mt = llRound(45.0*mt)/45.0;

if (0.11111111 < mt)
return mt;

// else
return 0.11111111;
}

default
{
on_rez(integer start_param)
{
llResetScript();
}

state_entry()
{
llSetMemoryLimit(0x2000);

llSetLinkPrimitiveParamsFast(LINK_THIS,
[PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_CONVEX]);

vector scale = llGetScale();
startPosition = llGetPos();
startRotation = llGetRot();

vector v1 = 0.5*scale*startRotation;

rotation deltaRot = llEuler2Rot(< 0.0, angleEnd/numberOfKeyframes, 0.0>);

while (step < numberOfKeyframes)
{
vector ownRot2Left = llRot2Left(llGetRot());

V = v1*llAxisAngle2Rot(ownRot2Left, angleEnd*step/numberOfKeyframes);
V = v1*llAxisAngle2Rot(ownRot2Left, angleEnd*(step + 1.0)/numberOfKeyframes) - V;

listOfKeyframes += [V, deltaRot, motion_time(llVecMag(V)/speedInMetersPerSecond)];

step += 1.0;
}
}

touch_start(integer num_detected)
{
llSetKeyframedMotion([], []);

if (open)
{
llSetLinkPrimitiveParamsFast(LINK_THIS,
[PRIM_POSITION, startPosition,
PRIM_ROTATION, startRotation]);

llSetKeyframedMotion(listOfKeyframes, []);
}
else
// {
llSetKeyframedMotion(listOfKeyframes, [KFM_MODE, KFM_REVERSE]);
// }

open = !open;
}
}
</lsl>
After editing prim position, rotation and/or size the script should be reset in order to update the motion
==More Examples==
# [https://wiki.secondlife.com/wiki/User:Dora_Gustafson/Pendulum_motion Pendulum motion] Simple Pendulum Motion in 24 Key Frames, a good motion for a swing
# [https://wiki.secondlife.com/wiki/User:Dora_Gustafson/Harmonic_Oscillator_motion Oscillator motion] Motion in 12 Key Frames
|notes=
Potential Use Cases:
* Elevators
* Moving platforms
* Trains/Fixed-Track Vehicles
* Moving doors/walls/gates
* Windmills and other machines
Targeted coordinate systems: The Translation is in Global coordinates, the Rotation in Local coordinates
* Say: a move on the X-axis will move the object along the global, region X-axis no matter how the object is rotated
* Say: a rotate around the X-axis will rotate the object around it's local, prim X-axis no matter the object's rotation
* When the object is not rotated in the global system you won't notice the difference
|cat1=Physics
|cat2=Movement
|cat3
|cat4
}}

Limits

2012-11-01T13:28:14Z

Stickman Ingmann: Undo revision 1174070 (zero index, test was flawed) by Stickman Ingmann (Talk)

<noinclude>{{KBmaster}}</noinclude>
== Summary ==
{{RightToc}}
The Second Life Viewer and simulators have a division of labor, keeping track of the data that makes Second Life run. The Viewer's job is to:

* Handle locations of objects.
* Get velocities and other physics information, and does simple physics to keep track of what is moving where.

The simulator's job is to:

* Run the physics engine.
* Detect collisions.
* Keep track of where everything is
* Send locations of content to the Viewer along with updates when certain changes occur.

Limits are necessary for all of these components to work together. The list below outlines many of the '''Second Life numerical limits that affect your inworld experience'''. Some of these will likely change over time, so if you spot something incorrect/outdated, please take a moment to update it.

{{KBcaution|1=The scope of this page is focused on Linden Lab's official Viewers, keeping in mind [[Third_Party_Viewer_Directory|3rd-party viewers may differ]]. Cite sources and provide substantiation for limits that aren't provided by Linden Lab. Also, unconfirmed speculation [[Talk:Limits|goes on this discussion page]]. Don't add data without a hard limit, and don't add obscure trivia that doesn't practically affect the general inworld experience.|width=80%}}

== [[Avatar]] ==

* '''Max. # of attachments''' - 38 combined [[HUD]] or body attachments.
** They can be viewed by right-clicking your avatar and choosing '''Take Off''' > '''HUD''' or '''Detach'''.
** With the formal introduction of [[multiple attachments|multiple attachments to a single point]] in Viewer 2.4, you can attach up to 38 total objects, and they can all be attached to a single point.
* '''Max. # of clothing layers per slot''' - 5 (this includes alpha and Tattoo Layers)
* '''Max. unassisted fly height''' - Stable hover at 4096m.
** You can easily acquire a flight attachment to fly high. Also see [[flight limit]] and [[Limits#Navigation|the Navigation section]] below.
* '''Common shoe sizes''' - Most women's shoes are designed for a size 0 (zero) foot. Men's generally scale up to 14.
** You can check this by going to Edit menu > Appearance and clicking on the Shape > Legs tab.

* '''Max. length of avatar name''' - 31 for first name, 31 for last name, 63 in total (including the space).

* '''Max. length of {{LSLGC|Username}}''' - All lower case and a maximum of 63 including the '.'(eg; firstname.lastname)
**Older account user names are a combination of the First and last name in lower case separated by a period(.)(eg; lilmix.pixelmaid)
**Modern user names are a single name(no period)(eg; john1234) - '''Max.''' length is 31 characters
**The {{LSLGC|Legacy Name}}s for modern user names always shows Resident as the last name. So the Max is 40 characters in total for a new avatar's legacy name(including the space and last name 'Resident')
*'''Min. length of [[Display_Names]]''' - At least one script character
*'''Max. length of Display Names''' - 31 characters
**Display Names can include most Unicode script characters, spaces, and some punctuation.

* '''Max. avatar speed''' - 250m/s (with only attachments to assist)
* '''Max. teleport speed'''
** '''Server 1.27.1''' - 10 teleports per 15 seconds
** '''Server 1.27.0''' - 3 teleports per 15 seconds

== [[Animation]] ==

* '''Max. length of animation:''' 30.0 seconds
* '''Min. animation priority:''' 0
* '''Max. animation priority:''' 4 (5 with custom tools)
* '''Max. unique joints per animation:''' 32

== Building ==

* '''Max. [[prim]] dimensions (non-[[megaprim]])''' - 64×64×64m
** it was 10×10×10m before Second Life Server 11.08.17.238770
* '''Min. prim dimensions''' - 0.01×0.01×0.01m
* '''Max. # of prims in a linkset''' - 256
** It was 255 before SL Server 1.26.
** with the addition of Mesh, LI is not a factor, So a max of 256 0.5 LI objects can be linked for a max LI of 128 in that case.
* '''Max. link distance''' - See [[Linkability Rules]].
* '''Max. physics weight for an object to be set physical''' - 32.0
** If you try to link more, it'll either say "Can't enable physics for objects with more than 32 primitives" or "Object has too many primitives -- its dynamics have been disabled.".
** On server versions 1.38 and below, each sitting avatar counted as 1 prim. From 1.40.2 the limit is only on actual prims.
* '''Max. build or rez height''' - 4,096m
** This is 768m for Viewers prior to SL 1.20
* '''Max. prim name length''' - 63 bytes UTF-8 [[string]]
** Note: This is the same total character limit as avatar names.
* '''Max. prim description length''' - 127 bytes UTF-8 [[string]]
** Note:
* '''Temporary prim lifetime''' - around 60 seconds
* '''Max. number of temporary prims''' - regular_prim_limit - current_regular_prims + minimum(0.5 * regular_prim_limit + 400, 1000)
** From [http://forums-archive.secondlife.com/8/cd/305651/1.html Andrew Linden's February 2009 discussion])
* '''Max. length of hovertext (via [[llSetText]] or [[PRIM_TEXT]])''' - 254 bytes UTF-8 [[string]]

== Chat (text) ==

* '''Whisper distance''' - 10 m
* '''Chat distance''' - 20 m
* '''Shout distance''' - 100 m
** ''Rule of thumb:'' when you're at default zoom ('''View''' > '''Reset View'''), if you can see another person's nametag, they can see your chat. If they're far enough away that you don't see a nametag, they won't "hear" you unless you shout.
** Text spoken as a "Chat" step in a gesture cannot be shouted or whispered
** Text spoken as "Replace with" text in a gesture can be whispered or shouted in Viewer 2 either by putting <code>/whisper</code> or <code>/shout</code> at the start of the "Replace with" text or by typing <code>/whisper</code> or <code>/shout</code> at the beginning of the nearby chat input bar, followed by the gesture's trigger text. (Though, if you do both, or if a gesture with built-in <code>/whisper</code> or <code>/shout</code> is used mid-sentence, the "/whisper" or "/shout" will appear literally.) Viewer 1 does not honor <code>/whisper</code> or <code>/shout</code> and will always send them literally.
* '''Max. length of a chat message''' - 1024 bytes/single-byte characters
* As of 8/13/2012 Instant Messages sent via llInstantMessage() can send a maximum of 1180 single byte characters.
** The same holds true for an IM <-> email replies.
*** When the receiver is offline, if they set an IM to Email feature ('''Edit''' > '''Preferences''' (or press {{K|Ctrl|P}}), go to the '''Communication''' tab and check the '''Send IM to Email''' checkbox), it will send offline messages directly to the mailbox connected to your account. When an offline message is received via Email, this message can also be answered via Email again. The length of properly delivered Email replies is limited to 1023 bytes/single-byte characters.
* '''Capped''' - Maximum number of offline messages (involving [[IM]]s, inventory offers, group notices and group invitations) received before messages get capped is 25.
** Senders can't know whether their messages were capped or not.
* '''Email -> IM''' replies can be sent up to 5 days after receiving the offline IM the email is meant to answer.<sup>[<span class="plainlinks">[https://blogs.secondlife.com/community/features/blog/2007/02/06/im-to-e-mail-return-addresses-changing blog]</span>]</sup>
* '''IMs''' are retained on Linden Lab's servers for up to 31 days before being discarded. For example, if someone sends you an Instant Message and the next time you login is 33 days later, you won't get it.
** Torley confirmed this with Kelly Linden.
* The number of '''IMs''' an object can send in one hour is 5000.

== [[Gesture]]s ==

* '''Shortcut key mapping:''' 33 unique combinations, since {{K|F2}}–{{K|F12}} can be used with the {{K|Ctrl}} or {{K|Shift}} modifiers.
* '''Maximum Chat step length:''' 127 single-byte characters.
* '''Maximum Wait time:''' 3600 seconds (one hour).

== [[Group]]s ==

* '''Maximum number of groups you can belong to:''' 42
** Roles within groups are sort of like sub-groups. In many cases, you can use them instead of creating new groups.
* '''Minimum number of members in a group:''' 2
** A group with only 1 person for 48 hours will be disbanded (cancelled). Unless the group owns land.
* '''Maximum number of roles allowed in a group:''' 10 (including "Owners" and "Everyone", which cannot be deleted)
* '''Maximum Group Name:''' 35 single-byte characters.
* '''Maximum Group Title:''' 20 single-byte characters.
* '''Maximum Length of a Group Notice:''' 512 single-byte characters.

== [[Inventory]] ==

* '''Maximum number of inventory items that can be sent in a folder:''' 42
** Folders count as items too. This has more to do with packet size limits than cheeky Douglas Adams references.
* '''Maximum notecard line:''' None, but scripts can only read the first 255 bytes.
* '''Maximum notecard size:''' 65,536 bytes
* '''Number of items in the Library:''' 1,248 as of 2010-06-17
** Verified by [[How_does_the_Library_work|hiding the Library]] and counting the difference.

== [[Land]] ==

* '''Maximum [[Land#Parcel|parcel]] size:''' 65,536 meters²
** Covering a whole region, or square on the World Map.
* '''Minimum parcel size:''' 16 meters²
* '''Maximum parcel name length:''' 63 single-byte characters
* '''Maximum parcel description length:''' 255 characters
* '''Region name length:''' Under Linden Concierge policy, minimum of 3 characters, and a maximum of 25 characters (including spaces). See [[Linden Lab Official:Guidelines for Private Region Naming|Guidelines for Private Region Naming]].
** Rare exceptions exist, like [http://slurl.com/secondlife/Q/128/128/24 Q].
* '''Maximum "NO ENTRY" ban line height:''' is for all options 80 meter. Only the option 'Banned Residents' (named) has a 5020 meter ban line high, which is visible up to a high of 800 meter above the terrain mesh.
* '''Maximum prims in a [[Land#Region|region]]:'''
** Full region: 15,000
** [[Land#Homestead|Homestead]]: 3,750
** [[Land#Openspace|Openspace]]: 750
* '''Maximum auto return value''': Besides "0" (which means ''never''), {{HoverText|999,999|Almost 23 months}} minutes is the highest auto return value.
* '''Terraforming limits:'''
** Most mainland can be raised/lowered by 4 meters (+/-).
** Some mainland cannot be terraformed, including: Bay City Regions, Blumfield, Boardman, Brown, De Haro, Nautilus City Regions, Nova Albion Regions, Shermerville Regions, and West Haven.
** A few, very old mainland Regions like Da Boom have a terraform range of 40 meters (+/-).
** Estate (private island) terraformability is settable to a maximum of 100 meters (+/-) by the estate owner or managers.
* '''Maximum water height:''' 100 meters using inworld controls (mainland limit), 255 meters by using a *.raw file upload.
** Region water height is usually 20 meters, and adjacent regions should have the same water height, or else they will look discontinuous.
* '''Maximum terrain height:''' 255 meters using inworld controls (mainland limit), 510 meters by using a *.raw file upload.
* '''Miscellaneous estate limits:''' You can have a maximum of 10 estate managers, 500 allowed Residents, 63 allowed groups, and 500 banned Residents.
** See World menu > Region/Estate > Estate tab.
* '''Mainland maximum number of agents'''
** Full region: 100 (Historically set to 40 by LL but this does vary. Some meeting areas have this set to 60 and higher.)
*** Recent server performance improvements make regions with 60 agents in them perform quite well excepting the issue described in {{JIRA|SVC-3895}}.
** [[Land#Homestead|Homestead]]: 20
** [[Land#Openspace|Openspace]]: 10
* '''Island maximum number of agents:'''
** Full region: 100
** [[Land#Homestead|Homestead]]: 20
** [[Land#Openspace|Openspace]]: 10
* '''Freeze Time:''' Land owners can [[freeze]] other Residents for up to 30 seconds. Members of land owning groups can also be granted this ability.
* '''Minimum parcel that can be listed in Places or All search:''' 144 meters² 
* '''Minimum parcel that can be listed in Events:''' 512 meters²
* '''Maximum altitude for event listings:''' 768 meters ({{JIRA|WEB-814}})
* '''Maximum heights that objects can be seen on the [[World Map]]:''' 400.005m
* '''[[Classic clouds]] layer:''' Approximately 150-225 meters, although the edges of particles can appear to exceed that.

== [[Mesh]] ==

* '''Maximum Vertices:''' 65536 vertices per LOD for each Mesh.
* '''Maximum COLLADA File Size:''' The maximum mesh asset size after compression is 8MB, roughly equivalent to a 256MB raw COLLADA file.
* '''Maximum Bone Influence Weights Per Vertex:''' 4
* '''Maximum Materials per Mesh:''' 8
* '''Maximum Materials per Face:''' 1

== Misc. ==

*'''[https://secondlife.com/currency/describe-limits.php Billing and Trading Limits]''' - Includes [https://secondlife.com/whatis/economy-market.php LindeX] currency exchange limits.
*'''Contacts in Communication > Friends tab ''' - A maximum of 20 simultaneous contacts can be selected to change permissions, remove, or invite for a conference chat.

== Navigation ==

[[File:Max Alt.jpg|thumb|right|435px|'''Height counter error above 2147483647 meters''']]
* '''Absolute height limit:''' [http://en.wikipedia.org/wiki/2147483647#2147483647_in_computing 2147483647] = 2<sup>31</sup> − 1 meters, which causes the altitude counter to roll over. Altitudes well below this cause graphics errors probably due to limited floating point number precision.
* '''Highest z-value of an [[SLurl]], that will still teleport you to a positive altitude:''' 2147483583
** This is lower than the ''Absolute height limit'' above probably because of precision issues. Any value higher than 2147483583 would be rounded up to something beyond 2147483647 and thus cause an [http://en.wikipedia.org/wiki/Arithmetic_overflow overflow], while 2147483583 will still be rounded down to 2147483520 (see below).
* '''Highest altitude you can teleport to with an SLurl:''' 2147483520 meters

== [[Profile]] ==

Each 7-bit ASCII character is encoded in one byte. International characters might need more bytes. When pasting text instead of typing, you can get in one byte more into each of the below.

* '''2nd Life tab's About field''' - 510 bytes
* '''Picks tab''' - 10 picks with 1022 bytes each
* '''1st Life tab's Info field''' - 253 bytes
* '''Classified tab''' - 100 listings with x bytes each
* '''My Notes''' - 1022 bytes

== Performance ==

* '''Healthy Viewer FPS''' - Generally, FPS above 15 is good. The higher it gets, the smoother. You can check via Help menu > Lag Meter, or for more advanced usage, see View menu > Statistics Bar.
* '''Avatar Rendering Cost scores''' - [[Avatar Rendering Cost|Learn all about it!]]

== [[Scripting]] ==

* '''Height at which scripts reactivate on a no-script parcel''' - 50 m above terrain mesh. Scripted objects that take controls continue to remain active when you fly down or enter a no-script parcel.
* '''Maximum height where scripts can run''' - none, as long as the object remains rezzed or attached.
* '''Maximum script source code size''' - 65536 single byte characters.
* For specific scripting limits, lookup calls in the '''[[LSL Portal]]'''.

== [[Sound]] ==

* '''Maximum Sound Length:''' 10 seconds

== [[Textures]] ==
* '''[http://en.wikipedia.org/wiki/Aspect_ratio Aspect ratios]''' of profile, place, etc. pictures — all of these were measured at UI size (Edit menu > Preferences > General tab > UI Size) = 1.000:

=== 1.x Series Viewers ===

(official Viewer up to 1.23.5, most [[Alternate viewers|Third Party Viewers]])
* '''Search > All for "Classifieds", "People", and "Places"''' - 4:3 (256×192 pi×els)
* '''Search > Places and Classified tabs''' - ~7:5 (398×282 pixels)
* '''Search > Land tab''' - ~7:5 (358×252 pixels)
* '''Profile > 2nd Life tab''' - ~4:3 (178×133 pixels)
* '''Profile > Picks tab''' - 16:9 (288×162 pixels)
* '''Profile > 1st Life tab''' - 1:1 (133×133 pixels)
* '''Profile > Classifieds tab''' - ~3:2 (206×137 pixels)
* '''Profile > Web tab''' - 1:1 (400×400 pixels)
** A scrollbar uses 15 pixels on the right-hand side.
* '''About Land > Options tab''' - ~3:2 (178×117 pixels)
* '''Group Information > General tab's "Group Insignia"''' - 1:1 (126×126 pixels)
** Some of these textures are shared (for example, Search > All place pages, Search > Places, and About Land > Options use the same image), so you should pick a well-balanced ratio and size.
** [[Texture_aspect_ratios|Learn how to get correct texture aspect ratios when editing images.]]

=== 2.x Series Viewers ===

* '''Search > Classifieds thumbnail''' - 4:3 (60×45 pixels)
* '''Search > Classifieds expanded''' - ~4:3 (252×188 pixels)
* '''Search > Classifieds expanded > Details''' - 17:7 (272×112 pixels)
* '''Search > People''' - 4:3 (188×141 pixels)
* '''Search > Destination Guide thumbnail''' - ~4:3 (45×34 pixels)
* '''Search > Destination Guide expanded''' - 5:3 (250×150 pixels)
* '''Profile > 2nd Life tab''' - ~1:1 (100×99 pixels)
* '''Profile > Picks thumbnail''' - 8:5 (88×55 pixels)
* '''Profile > Pick expanded''' - ~5:3 (285×172 pixels)
* '''About Land > Options tab''' - ~20:13 (193×125 pixels)
* '''Places > More information''' - ~11:7 (272×173 pixels)

=== All Viewers ===

* '''Maximum texture size''' - 1024×1024 pixels
** All Second Life textures are constrained to [http://en.wikipedia.org/wiki/Power_of_2 powers of 2] (e.g., 128, 256, 512).
** Some textures inworld have a resolution as high as 2048×2048; this is due to a previous limit that was higher.
** We strongly recommend you use as small textures as possible because larger ones consume more memory and take substantially longer to load.
** Where large textures are being forced by import to only 512×512, lower your ...> Preferences >...> UI Size under 1.0, to increase import size to the max 1024×1024.

[[Category:Creation]] [[Category:Tutorials]] [[Category:Lists]]

=== Notes ===
In general 1 byte is enough to contain one character.

Limits

2012-11-01T13:14:22Z

Stickman Ingmann: num_motions > LL_CHARACTER_MAX_JOINTS, so 31 not 32.

<noinclude>{{KBmaster}}</noinclude>
== Summary ==
{{RightToc}}
The Second Life Viewer and simulators have a division of labor, keeping track of the data that makes Second Life run. The Viewer's job is to:

* Handle locations of objects.
* Get velocities and other physics information, and does simple physics to keep track of what is moving where.

The simulator's job is to:

* Run the physics engine.
* Detect collisions.
* Keep track of where everything is
* Send locations of content to the Viewer along with updates when certain changes occur.

Limits are necessary for all of these components to work together. The list below outlines many of the '''Second Life numerical limits that affect your inworld experience'''. Some of these will likely change over time, so if you spot something incorrect/outdated, please take a moment to update it.

{{KBcaution|1=The scope of this page is focused on Linden Lab's official Viewers, keeping in mind [[Third_Party_Viewer_Directory|3rd-party viewers may differ]]. Cite sources and provide substantiation for limits that aren't provided by Linden Lab. Also, unconfirmed speculation [[Talk:Limits|goes on this discussion page]]. Don't add data without a hard limit, and don't add obscure trivia that doesn't practically affect the general inworld experience.|width=80%}}

== [[Avatar]] ==

* '''Max. # of attachments''' - 38 combined [[HUD]] or body attachments.
** They can be viewed by right-clicking your avatar and choosing '''Take Off''' > '''HUD''' or '''Detach'''.
** With the formal introduction of [[multiple attachments|multiple attachments to a single point]] in Viewer 2.4, you can attach up to 38 total objects, and they can all be attached to a single point.
* '''Max. # of clothing layers per slot''' - 5 (this includes alpha and Tattoo Layers)
* '''Max. unassisted fly height''' - Stable hover at 4096m.
** You can easily acquire a flight attachment to fly high. Also see [[flight limit]] and [[Limits#Navigation|the Navigation section]] below.
* '''Common shoe sizes''' - Most women's shoes are designed for a size 0 (zero) foot. Men's generally scale up to 14.
** You can check this by going to Edit menu > Appearance and clicking on the Shape > Legs tab.

* '''Max. length of avatar name''' - 31 for first name, 31 for last name, 63 in total (including the space).

* '''Max. length of {{LSLGC|Username}}''' - All lower case and a maximum of 63 including the '.'(eg; firstname.lastname)
**Older account user names are a combination of the First and last name in lower case separated by a period(.)(eg; lilmix.pixelmaid)
**Modern user names are a single name(no period)(eg; john1234) - '''Max.''' length is 31 characters
**The {{LSLGC|Legacy Name}}s for modern user names always shows Resident as the last name. So the Max is 40 characters in total for a new avatar's legacy name(including the space and last name 'Resident')
*'''Min. length of [[Display_Names]]''' - At least one script character
*'''Max. length of Display Names''' - 31 characters
**Display Names can include most Unicode script characters, spaces, and some punctuation.

* '''Max. avatar speed''' - 250m/s (with only attachments to assist)
* '''Max. teleport speed'''
** '''Server 1.27.1''' - 10 teleports per 15 seconds
** '''Server 1.27.0''' - 3 teleports per 15 seconds

== [[Animation]] ==

* '''Max. length of animation:''' 30.0 seconds
* '''Min. animation priority:''' 0
* '''Max. animation priority:''' 4 (5 with custom tools)
* '''Max. unique joints per animation:''' 31

== Building ==

* '''Max. [[prim]] dimensions (non-[[megaprim]])''' - 64×64×64m
** it was 10×10×10m before Second Life Server 11.08.17.238770
* '''Min. prim dimensions''' - 0.01×0.01×0.01m
* '''Max. # of prims in a linkset''' - 256
** It was 255 before SL Server 1.26.
** with the addition of Mesh, LI is not a factor, So a max of 256 0.5 LI objects can be linked for a max LI of 128 in that case.
* '''Max. link distance''' - See [[Linkability Rules]].
* '''Max. physics weight for an object to be set physical''' - 32.0
** If you try to link more, it'll either say "Can't enable physics for objects with more than 32 primitives" or "Object has too many primitives -- its dynamics have been disabled.".
** On server versions 1.38 and below, each sitting avatar counted as 1 prim. From 1.40.2 the limit is only on actual prims.
* '''Max. build or rez height''' - 4,096m
** This is 768m for Viewers prior to SL 1.20
* '''Max. prim name length''' - 63 bytes UTF-8 [[string]]
** Note: This is the same total character limit as avatar names.
* '''Max. prim description length''' - 127 bytes UTF-8 [[string]]
** Note:
* '''Temporary prim lifetime''' - around 60 seconds
* '''Max. number of temporary prims''' - regular_prim_limit - current_regular_prims + minimum(0.5 * regular_prim_limit + 400, 1000)
** From [http://forums-archive.secondlife.com/8/cd/305651/1.html Andrew Linden's February 2009 discussion])
* '''Max. length of hovertext (via [[llSetText]] or [[PRIM_TEXT]])''' - 254 bytes UTF-8 [[string]]

== Chat (text) ==

* '''Whisper distance''' - 10 m
* '''Chat distance''' - 20 m
* '''Shout distance''' - 100 m
** ''Rule of thumb:'' when you're at default zoom ('''View''' > '''Reset View'''), if you can see another person's nametag, they can see your chat. If they're far enough away that you don't see a nametag, they won't "hear" you unless you shout.
** Text spoken as a "Chat" step in a gesture cannot be shouted or whispered
** Text spoken as "Replace with" text in a gesture can be whispered or shouted in Viewer 2 either by putting <code>/whisper</code> or <code>/shout</code> at the start of the "Replace with" text or by typing <code>/whisper</code> or <code>/shout</code> at the beginning of the nearby chat input bar, followed by the gesture's trigger text. (Though, if you do both, or if a gesture with built-in <code>/whisper</code> or <code>/shout</code> is used mid-sentence, the "/whisper" or "/shout" will appear literally.) Viewer 1 does not honor <code>/whisper</code> or <code>/shout</code> and will always send them literally.
* '''Max. length of a chat message''' - 1024 bytes/single-byte characters
* As of 8/13/2012 Instant Messages sent via llInstantMessage() can send a maximum of 1180 single byte characters.
** The same holds true for an IM <-> email replies.
*** When the receiver is offline, if they set an IM to Email feature ('''Edit''' > '''Preferences''' (or press {{K|Ctrl|P}}), go to the '''Communication''' tab and check the '''Send IM to Email''' checkbox), it will send offline messages directly to the mailbox connected to your account. When an offline message is received via Email, this message can also be answered via Email again. The length of properly delivered Email replies is limited to 1023 bytes/single-byte characters.
* '''Capped''' - Maximum number of offline messages (involving [[IM]]s, inventory offers, group notices and group invitations) received before messages get capped is 25.
** Senders can't know whether their messages were capped or not.
* '''Email -> IM''' replies can be sent up to 5 days after receiving the offline IM the email is meant to answer.<sup>[<span class="plainlinks">[https://blogs.secondlife.com/community/features/blog/2007/02/06/im-to-e-mail-return-addresses-changing blog]</span>]</sup>
* '''IMs''' are retained on Linden Lab's servers for up to 31 days before being discarded. For example, if someone sends you an Instant Message and the next time you login is 33 days later, you won't get it.
** Torley confirmed this with Kelly Linden.
* The number of '''IMs''' an object can send in one hour is 5000.

== [[Gesture]]s ==

* '''Shortcut key mapping:''' 33 unique combinations, since {{K|F2}}–{{K|F12}} can be used with the {{K|Ctrl}} or {{K|Shift}} modifiers.
* '''Maximum Chat step length:''' 127 single-byte characters.
* '''Maximum Wait time:''' 3600 seconds (one hour).

== [[Group]]s ==

* '''Maximum number of groups you can belong to:''' 42
** Roles within groups are sort of like sub-groups. In many cases, you can use them instead of creating new groups.
* '''Minimum number of members in a group:''' 2
** A group with only 1 person for 48 hours will be disbanded (cancelled). Unless the group owns land.
* '''Maximum number of roles allowed in a group:''' 10 (including "Owners" and "Everyone", which cannot be deleted)
* '''Maximum Group Name:''' 35 single-byte characters.
* '''Maximum Group Title:''' 20 single-byte characters.
* '''Maximum Length of a Group Notice:''' 512 single-byte characters.

== [[Inventory]] ==

* '''Maximum number of inventory items that can be sent in a folder:''' 42
** Folders count as items too. This has more to do with packet size limits than cheeky Douglas Adams references.
* '''Maximum notecard line:''' None, but scripts can only read the first 255 bytes.
* '''Maximum notecard size:''' 65,536 bytes
* '''Number of items in the Library:''' 1,248 as of 2010-06-17
** Verified by [[How_does_the_Library_work|hiding the Library]] and counting the difference.

== [[Land]] ==

* '''Maximum [[Land#Parcel|parcel]] size:''' 65,536 meters²
** Covering a whole region, or square on the World Map.
* '''Minimum parcel size:''' 16 meters²
* '''Maximum parcel name length:''' 63 single-byte characters
* '''Maximum parcel description length:''' 255 characters
* '''Region name length:''' Under Linden Concierge policy, minimum of 3 characters, and a maximum of 25 characters (including spaces). See [[Linden Lab Official:Guidelines for Private Region Naming|Guidelines for Private Region Naming]].
** Rare exceptions exist, like [http://slurl.com/secondlife/Q/128/128/24 Q].
* '''Maximum "NO ENTRY" ban line height:''' is for all options 80 meter. Only the option 'Banned Residents' (named) has a 5020 meter ban line high, which is visible up to a high of 800 meter above the terrain mesh.
* '''Maximum prims in a [[Land#Region|region]]:'''
** Full region: 15,000
** [[Land#Homestead|Homestead]]: 3,750
** [[Land#Openspace|Openspace]]: 750
* '''Maximum auto return value''': Besides "0" (which means ''never''), {{HoverText|999,999|Almost 23 months}} minutes is the highest auto return value.
* '''Terraforming limits:'''
** Most mainland can be raised/lowered by 4 meters (+/-).
** Some mainland cannot be terraformed, including: Bay City Regions, Blumfield, Boardman, Brown, De Haro, Nautilus City Regions, Nova Albion Regions, Shermerville Regions, and West Haven.
** A few, very old mainland Regions like Da Boom have a terraform range of 40 meters (+/-).
** Estate (private island) terraformability is settable to a maximum of 100 meters (+/-) by the estate owner or managers.
* '''Maximum water height:''' 100 meters using inworld controls (mainland limit), 255 meters by using a *.raw file upload.
** Region water height is usually 20 meters, and adjacent regions should have the same water height, or else they will look discontinuous.
* '''Maximum terrain height:''' 255 meters using inworld controls (mainland limit), 510 meters by using a *.raw file upload.
* '''Miscellaneous estate limits:''' You can have a maximum of 10 estate managers, 500 allowed Residents, 63 allowed groups, and 500 banned Residents.
** See World menu > Region/Estate > Estate tab.
* '''Mainland maximum number of agents'''
** Full region: 100 (Historically set to 40 by LL but this does vary. Some meeting areas have this set to 60 and higher.)
*** Recent server performance improvements make regions with 60 agents in them perform quite well excepting the issue described in {{JIRA|SVC-3895}}.
** [[Land#Homestead|Homestead]]: 20
** [[Land#Openspace|Openspace]]: 10
* '''Island maximum number of agents:'''
** Full region: 100
** [[Land#Homestead|Homestead]]: 20
** [[Land#Openspace|Openspace]]: 10
* '''Freeze Time:''' Land owners can [[freeze]] other Residents for up to 30 seconds. Members of land owning groups can also be granted this ability.
* '''Minimum parcel that can be listed in Places or All search:''' 144 meters² 
* '''Minimum parcel that can be listed in Events:''' 512 meters²
* '''Maximum altitude for event listings:''' 768 meters ({{JIRA|WEB-814}})
* '''Maximum heights that objects can be seen on the [[World Map]]:''' 400.005m
* '''[[Classic clouds]] layer:''' Approximately 150-225 meters, although the edges of particles can appear to exceed that.

== [[Mesh]] ==

* '''Maximum Vertices:''' 65536 vertices per LOD for each Mesh.
* '''Maximum COLLADA File Size:''' The maximum mesh asset size after compression is 8MB, roughly equivalent to a 256MB raw COLLADA file.
* '''Maximum Bone Influence Weights Per Vertex:''' 4
* '''Maximum Materials per Mesh:''' 8
* '''Maximum Materials per Face:''' 1

== Misc. ==

*'''[https://secondlife.com/currency/describe-limits.php Billing and Trading Limits]''' - Includes [https://secondlife.com/whatis/economy-market.php LindeX] currency exchange limits.
*'''Contacts in Communication > Friends tab ''' - A maximum of 20 simultaneous contacts can be selected to change permissions, remove, or invite for a conference chat.

== Navigation ==

[[File:Max Alt.jpg|thumb|right|435px|'''Height counter error above 2147483647 meters''']]
* '''Absolute height limit:''' [http://en.wikipedia.org/wiki/2147483647#2147483647_in_computing 2147483647] = 2<sup>31</sup> − 1 meters, which causes the altitude counter to roll over. Altitudes well below this cause graphics errors probably due to limited floating point number precision.
* '''Highest z-value of an [[SLurl]], that will still teleport you to a positive altitude:''' 2147483583
** This is lower than the ''Absolute height limit'' above probably because of precision issues. Any value higher than 2147483583 would be rounded up to something beyond 2147483647 and thus cause an [http://en.wikipedia.org/wiki/Arithmetic_overflow overflow], while 2147483583 will still be rounded down to 2147483520 (see below).
* '''Highest altitude you can teleport to with an SLurl:''' 2147483520 meters

== [[Profile]] ==

Each 7-bit ASCII character is encoded in one byte. International characters might need more bytes. When pasting text instead of typing, you can get in one byte more into each of the below.

* '''2nd Life tab's About field''' - 510 bytes
* '''Picks tab''' - 10 picks with 1022 bytes each
* '''1st Life tab's Info field''' - 253 bytes
* '''Classified tab''' - 100 listings with x bytes each
* '''My Notes''' - 1022 bytes

== Performance ==

* '''Healthy Viewer FPS''' - Generally, FPS above 15 is good. The higher it gets, the smoother. You can check via Help menu > Lag Meter, or for more advanced usage, see View menu > Statistics Bar.
* '''Avatar Rendering Cost scores''' - [[Avatar Rendering Cost|Learn all about it!]]

== [[Scripting]] ==

* '''Height at which scripts reactivate on a no-script parcel''' - 50 m above terrain mesh. Scripted objects that take controls continue to remain active when you fly down or enter a no-script parcel.
* '''Maximum height where scripts can run''' - none, as long as the object remains rezzed or attached.
* '''Maximum script source code size''' - 65536 single byte characters.
* For specific scripting limits, lookup calls in the '''[[LSL Portal]]'''.

== [[Sound]] ==

* '''Maximum Sound Length:''' 10 seconds

== [[Textures]] ==
* '''[http://en.wikipedia.org/wiki/Aspect_ratio Aspect ratios]''' of profile, place, etc. pictures — all of these were measured at UI size (Edit menu > Preferences > General tab > UI Size) = 1.000:

=== 1.x Series Viewers ===

(official Viewer up to 1.23.5, most [[Alternate viewers|Third Party Viewers]])
* '''Search > All for "Classifieds", "People", and "Places"''' - 4:3 (256×192 pi×els)
* '''Search > Places and Classified tabs''' - ~7:5 (398×282 pixels)
* '''Search > Land tab''' - ~7:5 (358×252 pixels)
* '''Profile > 2nd Life tab''' - ~4:3 (178×133 pixels)
* '''Profile > Picks tab''' - 16:9 (288×162 pixels)
* '''Profile > 1st Life tab''' - 1:1 (133×133 pixels)
* '''Profile > Classifieds tab''' - ~3:2 (206×137 pixels)
* '''Profile > Web tab''' - 1:1 (400×400 pixels)
** A scrollbar uses 15 pixels on the right-hand side.
* '''About Land > Options tab''' - ~3:2 (178×117 pixels)
* '''Group Information > General tab's "Group Insignia"''' - 1:1 (126×126 pixels)
** Some of these textures are shared (for example, Search > All place pages, Search > Places, and About Land > Options use the same image), so you should pick a well-balanced ratio and size.
** [[Texture_aspect_ratios|Learn how to get correct texture aspect ratios when editing images.]]

=== 2.x Series Viewers ===

* '''Search > Classifieds thumbnail''' - 4:3 (60×45 pixels)
* '''Search > Classifieds expanded''' - ~4:3 (252×188 pixels)
* '''Search > Classifieds expanded > Details''' - 17:7 (272×112 pixels)
* '''Search > People''' - 4:3 (188×141 pixels)
* '''Search > Destination Guide thumbnail''' - ~4:3 (45×34 pixels)
* '''Search > Destination Guide expanded''' - 5:3 (250×150 pixels)
* '''Profile > 2nd Life tab''' - ~1:1 (100×99 pixels)
* '''Profile > Picks thumbnail''' - 8:5 (88×55 pixels)
* '''Profile > Pick expanded''' - ~5:3 (285×172 pixels)
* '''About Land > Options tab''' - ~20:13 (193×125 pixels)
* '''Places > More information''' - ~11:7 (272×173 pixels)

=== All Viewers ===

* '''Maximum texture size''' - 1024×1024 pixels
** All Second Life textures are constrained to [http://en.wikipedia.org/wiki/Power_of_2 powers of 2] (e.g., 128, 256, 512).
** Some textures inworld have a resolution as high as 2048×2048; this is due to a previous limit that was higher.
** We strongly recommend you use as small textures as possible because larger ones consume more memory and take substantially longer to load.
** Where large textures are being forced by import to only 512×512, lower your ...> Preferences >...> UI Size under 1.0, to increase import size to the max 1024×1024.

[[Category:Creation]] [[Category:Tutorials]] [[Category:Lists]]

=== Notes ===
In general 1 byte is enough to contain one character.

Limits

2012-11-01T12:43:47Z

Stickman Ingmann:

Path update

2012-09-06T23:17:32Z

Stickman Ingmann: Removed "RC only" notice. On main channel.

[[Category:Pathfinding]]{{LSL_Event
|event=path_update
|event_desc=Event description goes here.
|p1_type=integer|p1_name=type
|p1_desc=A <code>PU_*</code>, it's the path event type
|p1_hover=A PU_* flag, it's the path event type
|p2_type=list|p2_name=reserved
|p2_desc=Reserved; not currently used.
|constants={{LSL_Constants/path_update}}
|caveats=
* Note that if wandering, the "stop" (<code>{{LSL Const|PU_GOAL_REACHED|hex=0x01|ihex=1}}</code>) type may never occur as a new goal may be chosen when near (<code>{{LSL Const|PU_SLOWDOWN_DISTANCE_REACHED|hex=0x00|ihex=0}}</code>) the previous goal.
* When the character cannot navigate from the current position (<code>{{LSL Const|PU_FAILURE_INVALID_START|hex=0x02|ihex=2}}</code>) [[llNavigateTo]] with the <code>{{LSL Const|FORCE_DIRECT_PATH|value=1}}</code> option may be helpful.
|examples=
<lsl>
default
{
state_entry()
{
llDeleteCharacter(); // Clear any previous character behaviors
llCreateCharacter([CHARACTER_MAX_SPEED, 25, CHARACTER_DESIRED_SPEED, 15.0]);
//MAX_SPEED is @ 20 by default

llWanderWithin(llGetPos(), <10.0, 10.0, 10.0>, []);
}

path_update(integer type, list reserved)
{
if (type == 0)
{
llOwnerSay("Near");
}
else if (type == 1)
{
llOwnerSay("Stopping");
}
else if (type == 2)
{
llOwnerSay("Cannot path find from current location! Attempting to go to the center of the region.");

llNavigateTo(<128.0, 128.0, llGround(<128.0, 128.0, 0.0> - llGetPos())>, [FORCE_DIRECT_PATH, TRUE]);
}
else if (type == 3)
{
llOwnerSay("Goal not on navmesh!");
}
else if (type == 4)
{
llOwnerSay("Goal unreachable!");
}
else if (type == 5)
{
llOwnerSay("Target gone!");
}
else if (type == 6)
{
llOwnerSay("No place to go!");
}
else if (type == 7)
{
llOwnerSay("Hiding from pursuer...");
}
else if (type == 8)
{
llOwnerSay("Switched from hiding to running...");
}
else if (type == 9)
{
llOwnerSay("Region has no nav mesh..");
}
else if (type == 10)
{
llOwnerSay("Dynamic pathfinding is disabled in this region.");
}
else if (type == 11)
{
llOwnerSay("Parcel entry problem (is the parcel full?).");
}
else if (type == 1000000)
{
llOwnerSay("Hit an unspecified failure");
}
else
{
llOwnerSay("Unknown failure");
}
}
}
</lsl>
|also_functions=
* [[llCreateCharacter]]
* [[llDeleteCharacter]]
* [[llEvade]]
* [[llExecCharacterCmd]]
* [[llGetClosestNavPoint]]
* [[llFleeFrom]]
* [[llNavigateTo]]
* [[llPatrolPoints]]
* [[llPursue]]
* [[llUpdateCharacter]]
* [[llWanderWithin]]
|also_events
}}

Advanced menu/1.23/1.23

2012-08-12T03:12:27Z

Stickman Ingmann:

{{KBcaution|[http://blogs.secondlife.com/community/community/tnt/blog/2010/12/07/viewer-24-beta-much-easier-to-enable-advanced-menu-and-run-multiple-viewers '''Viewer 2.4 Beta lets you enable Advanced menu with a checkbox!''']}}

{{KBwarning|The '''Advanced''' menu and the unique features within it are NOT supported by Linden Lab, because they're intended for technical debugging. You may find the Advanced menu beneficial and Lindens appreciate Residents documenting its use, but '''LL does NOT guarantee it to function correctly. USE AT YOUR OWN RISK.'''}}

{{Help|Viewer=*|Glossary=*}}
{{GettingStartedNav}}

This page is part of the ''Resident-contributed, unofficial'' Second Life User's Manual, describing how the Viewer software works. Please see the main [[User's Manual]] page as a starting point.

==What is this menu for?==

The '''Advanced''' menu contains more technical settings than the rest of the Second Life Viewer, which is why they're usually hidden. Some of them are useful, but none of them are essential in order to use any of Second Life's features. If you'd like to enable the '''Advanced''' menu, use the following shortcuts:

* '''Windows''' - {{K|Ctrl|Alt|D}}
* '''Mac''' - {{K|Ctrl|Opt|D}}
* '''Linux''' - {{K|Ctrl|Alt|D}}

{{KBnote| In some cases on Windows, there may be a shortcut conflict with another application. In which case, hold down {{K|Ctrl|Alt|Shift|D}}.}}

{{KBnote| In Viewer 2, the Linux binding changed to {{K|Ctrl|Alt|D}}, which may conflict with window manager specific default shortcuts. In Ubuntu, for example, it's necessary to change Gnome's "Keyboard Shortcuts" preference for "Hide all normal windows and set focus to the desktop" in order for the key chord to be passed through to SL.}}

Video of how to do it in Viewer 2:

{{KBvideo|LL4g5Iersq4|640|505|type=youtube}}

Additionally, there are two related menus:

* '''Develop''' - Choose '''Advanced''' menu > '''Show Develop Menu''' to enable it. This contains even more technical features for [[Snowstorm|Viewer developers]]. Some features are casually useful, however. (For example, if you find "{{xref|facelight|facelights}}" annoying, disable '''Develop''' > '''Rendering''' > '''Render Attached Lights'''.)
* '''Admin''' - Not unlike [http://www.belolats.com/2010/07/5-inception-levels-4-dream-levels.html descending into another dream level], choose '''Develop''' menu > '''Show Admin Menu'''. Unlike '''Advanced''' and '''Develop''', the options here are view-only, and can only be used by Linden Lab employees. Unless there's been an actual [[security issues|security exploit]], don't worry.

== More details ==
{{Todo|Many details below are for the older Viewer 1.23 and need to be updated.}}

=== Useful Items for General Users ===

* Stop Animating me - Cancels all animations affecting your avatar.

* '''[[Rebake Textures]]''' - Forces your computer to redo and send your avatar skin + clothing again. Sometimes this does not happen correctly the first time, and other users will see your avatar as a persistent cloud (avatar did not load at all), grey (shape loaded but not textures), or parts look wrong (some textures did not load properly).

* Set UI Size to Default

* Set Windows Size - use this to take video at a specific resolution

* Limit Select Distance - disable to edit far-away objects

* Disable Camera Constraints - disable it to zoom around freely

* '''High Res Snapshot''' - doubles the pixel count of snapshots saved to disk

* Quiet Snapshots to Disk - enable to take snapshots without the usual sound and avatar animation

* '''Show Debug Settings''' - Enter "RenderFarClip" to set draw distance to non-standard values. Values below normal 64m minimum are useful to reduce lag. '''Caution:''' randomly changing debug settings can mess up your viewer program and cause it to crash; in that case you can delete or rename your ''settings.xml'' file to force all settings to their default values.

=== All Advanced Menu Items (obsolete 1.23 picture) ===

[[File:V1.23 Advanced Menu.jpg|thumb|300px|left]]

== Consoles (should be moved to Develop menu page) ==

==== '''Consoles Submenu >''' ====

Displays fixed windows with technical information about the viewer program:

> '''''Frame Console''''' - it's no more in V2 !

> '''''[[Texture Console]]''''' - Shows progress and status information about textures while they are being fetched or decoded (size, memory taken up by them, level of detail...)

> '''''Debug Console''''' - Shows a console window that displays technical information about the client's actions as it does them

> '''''[[Fast Timers]]''''' - Shows how much time different tasks that are executed for each frame take (in other words, how much of each frame in the client is taken up by specific processes)

> '''''Notifications Console''''' -

> '''''Region Info to Debug Console''''' -

> '''''Group Info to Debug Console''''' -

> '''''Capabilities Info to Debug Console''''' -

==== '''HUD Info Submenu >''' ====

Displays fixed overlay on the 3D view with the following choices:

> '''''Velocity''''' - Shows a scale with current avatar velocity in m/s

> '''''Camera''''' - Shows avatar and camera positions in grid coordinates

> '''''Wind''''' - Shows wind speed and direction

> '''''FOV''''' - Shows camera field of view

* '''High-res Snapshot''' - When set, makes a snapshot double the screen size instead of equal to the screen size.
* '''[[Quiet Snapshots to Disk]]''' - When set snapshot sound and animation are not played.
* '''Show Mouselook Crosshairs'''
* '''[[Debug Permissions]]''' - Shows detailed information about object permissions in the edit menu.
* '''Clear Group Cache''' - Clears the cached groupmembers lists.

==== '''Rendering Submenu >''' ====

Controls many aspects of how the graphics card or chip displays the 3D view

> '''''Types''''' > - The items below are displayed when checked

::> > '''''Simple''''' -
::> > '''''Alpha''''' - [[Transparency]]/opacity
::> > '''''Tree''''' - Toggles rendering of [[terrain]] plants.
::> > '''''Character''''' - Toggles rendering of the avatar mesh.
::> > '''''SurfacePatch''''' - [[Ground]]
::> > '''''Sky''''' - Toggles rendering of the sky box.
::> > '''''Water''''' - Toggles rendering of water.
::> > '''''Ground''''' - ''not sure what it renders but disabling it has not effect other than speeding up the client. -spitfire clary''
::> > '''''Volume''''' - [[Prim]]s
::> > '''''Grass''''' - [[Grass]] and other terrain vegetation
::> > '''''Clouds''''' - [[Cloud]]s
::> > '''''Particles''''' - Toggles rendering of [[particles]].
::> > '''''Bump''''' - [[Bumpmapping]]

> '''''Features''''' > -

::> > '''''UI''''' - Toggle rendering of the [[user interface]]. Make sure to remember the key shortcut, as once you disable this the menus will disappear.
::> > '''''Selected''''' -
::> > '''''Highlighted''''' -
::> > '''''Dynamic Textures''''' -
::> > '''''Foot Shadows''''' - Toggles rendering of the small [[shadow]]s that appear at any [[avatar]]'s feet.
::> > '''''Fog''''' - [[Fog]]
::> > '''''Test FRInfo''''' -
::> > '''''Flexible Object''''' - [[Flexible]] objects

> '''''Info Displays''''' > -

::> > '''''Verify ''''' -
::> > '''''BBoxes ''''' - Bounding boxes
::> > '''''Points ''''' - Vertices
::> > '''''Octree ''''' - Occlusion tree
::> > '''''Shadow Frusta ''''' -
::> > '''''Occlusion ''''' - Occlusion planes
::> > '''''Render Batches ''''' -
::> > '''''Animated Textures ''''' -
::> > '''''Texture Priority ''''' -
::> > '''''Avatar Rendering Cost ''''' - Shows a score above each avatar, indicating, how ''expensive'' it is to render. A higher score will lag the viewer more than a low score. Read [[Avatar Rendering Cost]] for more details.
::> > '''''Texture Area (sqrt(A)) ''''' -
::> > '''''Face Area (sqrt(A)) ''''' -
::> > '''''Lights ''''' - [[Light]]s
::> > '''''Particles ''''' - [[Particles]]
::> > '''''Composition ''''' -
::> > '''''Glow ''''' - [[Glow]]
::> > '''''Raycasting ''''' -
::> > '''''Sculpt ''''' - [[Sculpted prim]]s
::> > '''''Vectorize Perf Test''''' -

> '''''Render Tests''''' > -

::> > '''''Camera Offset''''' -
::> > '''''Randomize Framerate''''' -
::> > '''''Periodic Slow Frame''''' -
::> > '''''Frame Test''''' -

> '''''Axes''''' - Render coordinate frame at your position

> '''''Hide Selected''''' - Stops rendering of any selected object.

> '''''Tangent Basis''''' - Render normal and binormal (debugging bump mapping)

> '''''Selected Texture Info''''' - When modify rights are granted, this outputs the texture UUIDs placed on a selected object.

> '''''Wireframe''''' - Shows the world in [[wireframe]] mode.

> '''''Object-Object Occlusion''''' - Skips rendering of objects that are out of view.

> '''''Debug GL''''' - Enable strict GL debugging.

> '''''Debug Pipeline''''' - Enable strict pipeline debugging.

> '''''Fast Alpha''''' - Use lossy alpha rendering optimization (opaque/nonexistent small alpha faces).

> '''''Animate Textures''''' - Enable texture animation (debug)

> '''''Disable Textures''''' -

> '''''Run Multiple Threads''''' > - Improves performance by allowing threads to run in the background while rendering. You should enable this option!

> '''''Cheesy Beacon''''' - Changes the default tracking beacon to an animated "pulsing" beacon.

> '''''Attached Lights''''' - Disables [[attach]]ed lightsources when unticked.

> '''''Attached Particles''''' - Disables attached particle sources when unticked.

==== '''World Submenu >''' ====

* '''''> Sim Sun Override''''' -

* '''''> Dump Scripted Camera''''' -

* '''''> Fixed Weather''''' -

* '''''> Dump Region Object Cache''''' -

==== '''UI Submenu >''' ====

* '''''> Rotate Mini-Map''''' - If is checked ("X") the Mini-Map rotates with the movement of your avatar. If uncheck, the north (N) is always up, the compass don't rotate.

* '''''> Use default system color picker''''' -

* '''''> Show search panel in overlay bar''''' -

* '''''> Web Browser Test''''' -

* '''''> Editable UI''''' -

* '''''> Dump SelectMgr''''' -

* '''''> Dump Inventory''''' -

* '''''> Dump Focus Holder''''' -

* '''''> Print Selected Object Info''''' -

* '''''> Print Agent Info''''' -

* '''''> Memory Stats''''' -

* '''''> Double-Click Auto-Pilot''''' - Torley Linden wrote [[User:Torley Linden/Debug Settings|here]]: ''"Some of you may find it useful for navigation. Set it to TRUE, then anywhere you double-click (with the left mouse button) inworld, you'll automatically walk, run, or fly towards. Our autopilot is kind of flakey, so don't be surprised if this doesn't always work and you get an "Autopilot canceled" message. Nevertheless, a fun novelty."''

* '''''> Debug SelectMgr''''' -

* '''''> Debug Clicks''''' -

* '''''> Debug Views''''' -

* '''''> Show Name Tooltips''''' -

* '''''> Debug Mouse Events''''' -

* '''''> Debug Keys''''' -

* '''''> Debug WindowProc''''' -

* '''''> Debug Text Editor Tips''''' -

* '''''> Show Time''''' -

* '''''> Show Render Info''''' -

* '''''> Matrices''''' -

* '''''> Show Color Under Cursor''''' - Show the RGB color values of the pixel the cursor is on. (Note: The fourth number in the sequence shows the opacity values for UI elements, and for post-process effects such as glow. This number will remain at zero unless the cursor is over such an item.)

==== '''XUI Submenu >''' ====

* '''''> Floater Test...''''' -

* '''''> Font Test...''''' -

* '''''> Export Menus to XML...''''' -

* '''''> Edit UI...''''' -

* '''''> Load from XML...''''' -

* '''''> Save to XML...''''' -

* '''''> Show XUI Names''''' -

==== '''Character Submenu >''' ====

* '''''> Grab Baked Texture >''''' -

:> > ''''' Iris''''' -

:> > ''''' Head''''' -

:> > ''''' Upper Body''''' -

:> > ''''' Lower Body''''' -

:> > ''''' Skirt''''' -

:> > ''''' Hair''''' -

* '''''> Character Tests >''''' -

:> > ''''' Go Away/AFK When Idle''''' - When checked, this item uses an idle timer to set (away) and auto-logout. It is enabled by default. If you do nothing with keyboard or mouse for 5 minutes, your avatar will show (Away) status, and after 30 minutes will be logged out automatically.

:> > ''''' Appearance to XML''''' - Saves your current appearance settings (avatar shape) to C:\Users\(username)\AppData\Roaming\SecondLife\user_settings\new archetype.xml

:> > ''''' Toggle Character Geometry''''' -

:> > ''''' Test Male''''' - Changes the avatar's appearance to a default male avatar.

:> > ''''' Test Female''''' - Changes the avatar's appearance to a default female avatar.

:> > ''''' Toggle PG''''' -

:> > ''''' Allow Select Avatar''''' -

* '''''> Enable Lip Sync (Beta)''''' - Makes your avatar's mouth move in sync with voice chat(?).

* '''''> [[Tap-Tap-Hold To Run]]''''' - When toggled on, pressing the up-arrow key {{Keypress|↑}} twice shortly after another results in running.

* '''''> Force Params to Default''''' -

* '''''> Reload Vertex Shader''''' -

* '''''> Animation Info''''' - Displays currently active animation [[UUID]]s above avatar's heads.

* '''''> Slow Motion Animations''''' -

* '''''> Show Look At''''' - Indicates via crosshairs where agents are focusing their camera(s). It's not distinguishable which crosshair belongs to which agent. See the document about [[Show Look At]].

* '''''> Show Point At''''' - See video tutorial about [[Video Tutorial/See where you're pointing with Show Point At|Show Point At]].

* '''''> Debug Joint Updates''''' -

* '''''> Disable LOD''''' -

* '''''> Debug Character Vis''''' -

* '''''> Show Collision Skeleton''''' -

* '''''> Display Agent Target''''' -

* '''''> Debug Rotation''''' -

* '''''> Dump Attachments''''' -

* '''''> [[Rebaking textures|Rebake Textures]]''''' - Forces your computer to redo and send your avatar skin + clothing again. Sometimes this does not happen correctly the first time, and other users will see your avatar as a persistent cloud (avatar did not load at all), grey (shape loaded but not textures), or parts look wrong (some textures did not load properly).

==== '''Network Submenu >''' ====

* '''''> Enable Message Log''''' -

* '''''> Disable Message Log''''' -

* '''''> Velocity Interpolate Objects''''' -

* '''''> Ping Interpolate Object Positions''''' -

* '''''> Drop a Packet''''' -

==== '''Recorder Submenu >''' ====

* '''''> Full Session Logging''''' -

* '''''> Start Logging''''' -

* '''''> Stop Logging''''' -

* '''''> Log 10 Seconds''''' -

* '''''> Log 30 Seconds''''' -

* '''''> Log 60 Seconds''''' -

* '''''> Start Playback''''' -

* '''''> Stop Playback''''' -

* '''''> Loop Playback''''' -

* '''''> Start Record''''' -

* '''''> Stop Record''''' -

==== '''Remainder of Advanced Menu''' ====

* '''Show Updates''' - Indicates visually which objects were updated recently. See [[I see blue, green, or red triangles coming from objects inworld that I think shouldn't be there.]]

* '''Compress Images'''

* '''Limit Select Distance''' - Limits the distance in which you're allowed to select and edit objects.

* '''Disable Camera Constraints''' - Your camera movement is constrained in a maximum distance to your avatar. Ticking this option will allow you to move the camera further away.

* '''Mouse Smoothing'''

* '''Console Window'''

* '''Output Debug Minidump'''

* '''[[Debug Settings]]''' - Opens the "Debug Settings" floating window. Allows manually setting essentially every Viewer setting. '''Warning:''' randomly playing with these settings can make the viewer program unusable.

* '''View Admin Options''' - Makes the client act as if it has owner permissions on all objects and land. Any action the user does not have permission for will generate an error message. Also toggles visibility of the "Admin" dropdown menu on the top menu bar.

* '''Request Admin Status''' - Also known as "[[God Mode]]". Enables administrative functions. This only works for Linden Staff.

* '''Leave Admin Status''' - Ends Admin Status or "[[God Mode]]".

<br clear="all"/>

=== Admin Menu ===

[[File:V1.23 Admin Menu.jpg|thumb|300px|left]]

{{KBwarning| This menu is off by default. Nobody who is not a [[Linden]] can use the options in the '''Admin''' menu. The options in the '''Admin''' menu are for viewing purposes only!}}

==== '''Object Submenu >''' ====

* '''''> Take Copy''''' - Allows a Linden to take a copy of an object, regardless of ownership.

* '''''> Force Owner to Me''''' - Allows a Linden to make themselves the owner of any object. However, copy/mod/trans permissions are unaffected.

* '''''> Force Owner Permissive''''' - Allows a Linden to make themselves the owner of any object and also gives them full permissions to copy, modify and transfer that object.

* '''''> Delete''''' - Allows a Linden to delete an object, regardless of ownership.

* '''''> Lock''''' - Unknown at this time (Probably allows a Linden to lock an object so that nobody, even its creator and/or owner, can edit it).

* '''''> Get Asset IDs''''' - Unknown at this time (Probably allows a Linden to get the [[UUID]]s of an object and its associated assets).

==== '''Parcel Submenu >''' ====

* '''''> Owner to Me''''' -

* '''''> Set to Linden Content''''' -

* '''''> Claim Public Land''''' -

==== '''Region Submenu >''' ====

* '''''> Dump Temp Asset Data'''''

* '''God Tools...''' - Opens "God Tools" floating window

* '''Save Region State'''
<br clear="all"/>

[[Category:Advanced menu]]

LlAttachToAvatar

2012-08-04T23:27:30Z

Stickman Ingmann: Added link to new function, llAttachToAvatarTemp

{{LSL_Function
|inject-2=
{{LSL_Function/permission|PERMISSION_ATTACH|grant=the owner}}
{{Issues/VWR-12525}}{{Issues/SCR-137}}{{Issues/SVC-890}}{{Issues/SCR-277}}
|func_id=113|func_sleep=0.0|func_energy=10.0
|func=llAttachToAvatar
|p1_type=integer|p1_name=attach_point|p1_desc=ATTACH_* constant or valid value (see the tables below)
|func_desc=Attaches the object to the avatar who has granted permission to the script. The object is taken into the users inventory and attached to '''attach_point'''.
|func_footnote=If '''attach_point''' is zero, then the object attaches to the attach point it was most recently attached to.
|return_text
|spec
|caveats=*Attach points can be occupied by multiple attachments.{{Footnote|Multiple attachments per attach point were added as result of {{Jira|SCR-277}}|Multiple attachments per attach point were added as result of SCR-277}}
**This was not always the case, previously if '''attach_point''' was occupied, the existing object was detached and the new attachment took it's place.
*Objects attached to the head (and any attachment position within the head) will not be visible in First Person view (aka [[Mouselook]]) if "show attachments in mouselook" is disable.
*If '''attach_point''' is zero but the object was never previously attached, it defaults to the right hand ({{LSL Const|ATTACH_RHAND|integer|6|c=right hand}}).
*If the object is already attached the function fails silently, regardless if the '''attach_point''' is a different [[llGetAttached|attach point]]. -- [[Template:Issues/SCR-137|SCR-137]]
|examples=
<lsl>//-- rez object on ground, drop in this script, it will request permissions to attach,
//-- and then attach to the left hand if permission is granted. if permission is denied,
//-- then the script complains.
default
{
state_entry()
{
llRequestPermissions( llGetOwner(), PERMISSION_ATTACH );
}

run_time_permissions( integer vBitPermissions )
{
if( vBitPermissions & PERMISSION_ATTACH )
{
llAttachToAvatar( ATTACH_LHAND );
}
else
{
llOwnerSay( "Permission to attach denied" );
}
}

on_rez(integer rez)
{
if(!llGetAttached())
{ //reset the script if it's not attached.
llResetScript();
}
}

attach(key AvatarKey)
{
if(AvatarKey)
{//event is called on both attach and detach, but Key is only valid on attach
integer test = llGetAttached();
if (test) {
llOwnerSay( "The object is attached" );
} else {
llOwnerSay( "The object is not attached");
}
}
}
}</lsl>
|helpers
|also_functions={{LSL DefineRow||[[llAttachToAvatarTemp]]|Attach an object to any avatar}}
{{LSL DefineRow||[[llDetachFromAvatar]]|Detaches the object from the avatar}}
{{LSL DefineRow||[[llGetAttached]]|Gets the attach point number}}
|also_articles
|also_events
|constants={{LSL_Constants_Attachment}}
|notes
|cat1=Attachment
|cat2=Avatar
|cat3
|cat4
}}

Content Creation/Mesh Import User Group

2012-07-16T19:06:33Z

Stickman Ingmann:

{{User Group Page
|purpose=
Come discuss any issues around content creation - its challenges, limitations in the tools, workarounds and successes. Land is provided next to the office build for rezzing example content.
Bug reports and feature requests should have JIRA ticket numbers if at all possible, as it makes it easier to collaborate on issues both internally and externally.

Priority will be given to topics that are posted in advance and are relevant to the goals of the office hour. Feel free to include relevant links to JIRA or wiki pages.

<br clear="all"/>
{{Navbox/Mesh|project}}
|date-time=
Mondays at Noon in Pacific time (SL standard time)

|location=
[http://maps.secondlife.com/secondlife/Borrowdale/79/225/32 Borrowdale on AGNI]

|team=
Nyx Linden, Runitai Linden, and occasional other guest lindens. Please contact one of us if you are unsure if your topic is relevant or appropriate.
|agenda=
<br><br>

Please add topics below '''prior to 11:50 AM'''. Also, please put your SL name down so we can follow up if we have questions. Thanks!

Enter agenda items here (with name, please)
# Any chance we will ever see support for more riggable extremities (like a tail or true taur style avatars) ? [[User:Squirrel Wood|Squirrel Wood]] 10:22, 16 July 2012 (PDT)
# I've seen a lot of marketplace failed deliveries. when can we expect a system that just works? [[User:GM Nikolaidis|GM Nikolaidis]] 10:37, 16 July 2012 (PDT)
# Is there a known fix for transparent textures not showing up as transparent unless highlighted? [[User:Aki Shichiroji|Aki Shichiroji]] 12:05, 16 July 2012 (PDT)
# Are morph targets back on the table? [[User:Stickman Ingmann|Stickman]] 12:06, 16 July 2012 (PDT)
# Are custom skeletons still in the works? How about object/non-avatar skeleton and animations to go along with the pathfinding project? [[User:Stickman Ingmann|Stickman]] 12:06, 16 July 2012 (PDT)
# your topic here! End with 3 or 4 ~ to add your name or name and date

|archive=
{{:Content_Creation,_Mesh_Import_User_Group/Archive}}
}}
[[Category:Mesh]]

Content Creation Improvement Informal User Group

2012-07-03T17:26:04Z

Stickman Ingmann:

{{Oz/User Group Page
|purpose=
User group for improving content creation on Second Life either through creating new features, or enhancing existing features.
All topics relating to the improvement of content creation, whether it's adding new features or improving existing features, are valid topics for discussion. When in doubt about whether or not a topic is appropriate, contact Geenz Spad.
|date-time=
Every Tuesday 03:00-04:00 PM SLT
|location={{SLurl|region=Hippotropolis|x=118|y=110|z=31|title=Hippotropolis Auditorium}}
|team=Chaired by [[User:Geenz Spad|Geenz Spad]], [[User:Siddean Munro|Siddean Munro]]. Linden Liason: [[User:Oz Linden|Oz Linden]].
|agenda=

#Introduction to the first Content Creation Improvement UG meeting. [[User:Geenz Spad|Geenz Spad]]
# Educating users on efficiency, and Linden Lab setting building standards. ([[User:Stickman Ingmann|Stickman]])

}}

LSL Delay

2012-06-05T11:44:29Z

Stickman Ingmann: Testing says touch() is 0.05s, not 0.1.

{{LSL Header|ml=*}}
{{RightToc}}
{{LSLC|}}

==Functions==
Some LSL functions delay script execution when they are called.

The delay is measured in seconds (it's a float value).

{|
|- valign="top"
|
{|{{Prettytable}}
|- {{Hl2}}
! {{HoverText|Delay|The delay in seconds}}
! Function
|-
|| 20.0
|| [[llRefreshPrimURL]]
|-
|| 20.0
|| [[llSetPrimURL]]
|-
|| 20.0
|| [[llEmail]]
|-
|| 10.0
|| [[llLoadURL]]
|-
|| 10.0
|| [[llGetSimulatorHostname]]
|-
|| 5.0
|| [[llTeleportAgentHome]]
|-
|| 3.0
|| [[llSendRemoteData]]
|-
|| 3.0
|| [[llRemoteLoadScriptPin]]
|-
|| 3.0
|| [[llRemoteLoadScript]]
|-
|| 3.0
|| [[llRemoteDataReply]]
|-
|| 3.0
|| [[llGiveInventoryList]]
|-
|| 2.0
|| [[llSetParcelMusicURL]]
|-
|| 2.0
|| [[llParcelMediaQuery]]
|-
|| 2.0
|| [[llParcelMediaCommandList]]
|-
|| 2.0
|| [[llInstantMessage]]
|-
|| 2.0
|| [[llGetParcelPrimOwners]]
|-
|| 1.0
|| [[llTextBox]]
|-
|| 1.0
|| [[llRequestSimulatorData]]
|}
|
{|{{Prettytable}}
|- {{Hl2}}
! {{HoverText|Delay|The delay in seconds}}
! Function
|-
|| 1.0
|| [[llRequestInventoryData]]
|-
|| 1.0
|| [[llPreloadSound]]
|-
|| 1.0
|| [[llOpenRemoteDataChannel]]
|-
|| 1.0
|| [[llModPow]]
|-
|| 1.0
|| [[llMapDestination]]
|-
|| 1.0
|| [[llDialog]]
|-
|| 1.0
|| [[llCreateLink]]
|-
|| 1.0
|| [[llCloseRemoteDataChannel]]
|-
|| 0.3
|| [[llXorBase64Strings]]
|-
|| 0.2
|| [[llSetTexture]]
|-
|| 0.2
|| [[llSetRot]]
|-
|| 0.2
|| [[llSetRemoteScriptAccessPin]]
|-
|| 0.2
|| [[llSetPrimitiveParams]]
|-
|| 0.2
|| [[llSetPos]]
|-
|| 0.2
|| [[llSetLocalRot]]
|-
|| 0.2
|| [[llSetLinkTexture]]
|-
|| 0.2
|| [[llSetLinkPrimitiveParams]]
|-
|| 0.2
|| [[llScaleTexture]]
|-
|| 0.2
|| [[llRotateTexture]]
|}
|
{|{{Prettytable}}
|- {{Hl2}}
! {{HoverText|Delay|The delay in seconds}}
! Function
|-
|| 0.2
|| [[llOffsetTexture]]
|-
|| 0.2
|| [[llGetPrimitiveParams]]
|-
|| 0.1
|| [[llRezObject]]
|-
|| 0.1
|| [[llRezAtRoot]]
|-
|| 0.1
|| [[llResetLandPassList]]
|-
|| 0.1
|| [[llResetLandBanList]]
|-
|| 0.1
|| [[llRequestAgentData]]
|-
|| 0.1
|| [[llRemoveFromLandPassList]]
|-
|| 0.1
|| [[llRemoveFromLandBanList]]
|-
|| 0.1
|| [[llMakeSmoke]]
|-
|| 0.1
|| [[llMakeFountain]]
|-
|| 0.1
|| [[llMakeFire]]
|-
|| 0.1
|| [[llMakeExplosion]]
|-
|| 0.1
|| [[llGetNumberOfNotecardLines]]
|-
|| 0.1
|| [[llGetNotecardLine]]
|-
|| 0.1
|| [[llAdjustSoundVolume]]
|-
|| 0.1
|| [[llAddToLandPassList]]
|-
|| 0.1
|| [[llAddToLandBanList]]
|-
|| variable
|| [[llSleep|llSleep(float variable)]]
|}
|}

==Events==
All events have a min delay, the default delay between events is 0.05 seconds, a longer delay can be specified with [[llMinEventDelay]]. A delay less than the default will have the same effect as if it were the default.

{|
|- valign="top"
|
{|{{Prettytable}}
|- {{Hl2}}
! {{HoverText|Delay|The minimum delay in seconds}}
! Events
|-
||
||[[at_rot_target]]
|-
||
||[[at_target]]
|-
||
||[[attach]]
|-
||
||[[changed]]
|-
||
||[[collision]]
|-
||
||[[collision_end]]
|-
||
||[[collision_start]]
|-
||0.05
||[[control]]
|-
||
||[[dataserver]]
|-
||
||[[email]]
|-
||
||[[http_response]]
|}
|
{|{{Prettytable}}
|- {{Hl2}}
! {{HoverText|Delay|The minimum delay in seconds}}
! Events
|-
||
||[[http_request]]
|-
||
||[[land_collision]]
|-
||
||[[land_collision_end]]
|-
||
||[[land_collision_start]]
|-
||
||[[link_message]]
|-
||
||[[listen]]
|-
||
||[[money]]
|-
||
||[[moving_end]]
|-
||
||[[moving_start]]
|-
||
||[[no_sensor]]
|-
||
||[[not_at_rot_target]]
|-
||
||[[not_at_target]]
|}
|
{|{{Prettytable}}
|- {{Hl2}}
! {{HoverText|Delay|The minimum delay in seconds}}
! Events
|-
||
||[[object_rez]]
|-
||
||[[on_rez]]
|-
||
||[[remote_data]]
|-
||
||[[run_time_permissions]]
|-
||
||[[sensor]]
|-
||
||[[state_entry]]
|-
||
||[[state_exit]]
|-
||
||[[timer]]
|-
||0.05
||[[touch]]
|-
||0.05
||[[touch_end]]
|-
||0.05
||[[touch_start]]
|}
|}

LlSetKeyframedMotion

2012-01-17T23:09:30Z

Stickman Ingmann: Doesn't work on attachments.

{{LSL_Function
|func=llSetKeyframedMotion
|func_id=?
|func_desc=Specify a list of times, positions, and orientations to be followed by an object. The object will be smoothly moved between keyframes by the simulator. Collisions with other nonphysical or keyframed objects will be ignored (no script events will fire and collision processing will not occur). Collisions with physical objects will be computed and reported, but the keyframed object will be unaffected by those collisions. (The physical object will be affected, however.)

|func_sleep
|func_energy

|func_footnote
|p1_type=list|p1_name=keyframes|p1_hover=Strided keyframe list of the form: [vector position, rotation orientation, float time]
|p1_desc=Strided keyframe list of the form:
* ''vector'' position (optional via KFM_TRANSLATION and KFM_DATA)
* ''rotation'' orientation (optional via KFM_ROTATION and KFM_DATA)
* ''float'' time

Each keyframe is interpreted relative to the previous transform of the object. For example, consider the following list of keyframes: [<0, 0, 10>, [[ZERO_ROTATION]], 5, <0, 0, 0>, [[ZERO_ROTATION]], 5, <0, 0, -10>, [[ZERO_ROTATION]], 5]. This would cause the object to move up 10m over the course of 5s. It would then remain at the location for 5s before moving down 10m over the course of another 5s.
Time values must be greater than 0.1s.
Linear and angular velocities will be clamped to limits set by the simulator (values TBD).
An empty list will terminate any keyframed animation currently playing.

|p2_type=list|p2_name=options|p2_desc=modifiers and future options

|spec=
The following flags will be supported within the ''options'' list:
*KFM_MODE followed by one of: KFM_LOOP, KFM_REVERSE, KFM_FORWARD, or KFM_PING_PONG will specify the playback mode. Defaults to KFM_FORWARD. Must be specified when the keyframe list is provided.
*KFM_DATA followed by a bitwise combination of: KFM_TRANSLATION and KFM_ROTATION. By default both rotations and translations must be provided. If you specify one or the other, you should only include translations or rotations in your keyframe list. Must be specified at the time the keyframe list is provided.
*KFM_COMMAND followed by one of: KFM_CMD_STOP, KFM_CMD_PLAY, KFM_CMD_PAUSE. STOP will pause the animation AND reset it to the beginning. PAUSE will pause the animation without resetting. PLAY will resume a paused or stopped animation.
Note that if KFM_COMMAND is provided in the options list, it must be the only option in the list, and cannot be specified in the same function call that sets the keyframes list.

Inter-region are supported.

|caveats=
*This function does not work in attachments.
*This function can only be called on NON-physical objects. In the future it could be extended to support physical objects, but this is more complicated as collisions could prevent the object from reaching its goal positions on time.
*Collisions with avatars affect the angular movement of the object and it may not reach the final rotation.
*This function can only be called on the root prim of a linkset.
*This function requires the linkset to use the Prim Equivalency system. However, it keyframed objects will not receive the dynamics penalty and can have a physics {{HoverText|PE|Prim Equivalency}} of up to 64.
*llSetKeyframedMotion is implemented in terms of frames and not real time. To avoid a drift from the expected positions and rotations, use times which are integer multiples of 1/45, e.g. 20.0/45.0, 40.0/45.0, 90.0/45.0, etc. [http://community.secondlife.com/t5/LSL-Scripting/llSetKeyframedMotion-turning-a-corner/td-p/1225219 Forum Thread]
*There are a few bugs in the avatar animation system that may cause strange looking animations to play when standing on a moving platform (e.g., walking in place, feet-at-pelvis). We hope to fix these in the future, but doing so is out of scope for this feature.
*As with dynamic objects, objects moving using this function are paused when they are selected by an avatar with adequate permissions (object owner, passenger, etc). When such an avatar deselects the object, motion resumes, even if the object had been paused using KFM_CMD_PAUSE.
|examples=
<code>// If your client is not mesh-aware use the following line:

llSetLinkPrimitiveParamsFast(LINK_THIS, [PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_CONVEX]);

//</code>

<code>llSetKeyframedMotion([<0,0,10>, 5, <0,0,-10>, 5], [KFM_DATA, KFM_TRANSLATION, KFM_MODE, KFM_PING_PONG]);</code>
<code>llSetKeyframedMotion([<0,0,10>, llEuler2Rot(<90, 45, 180> * DEG_TO_RAD), 5, <0,0,-10>, llEuler2Rot(<270, 225, 360> * DEG_TO_RAD), 5], [KFM_MODE, KFM_REVERSE]);</code>
|notes=
Potential Use Cases:
* Elevators
* Moving platforms
* Trains/Fixed-Track Vehicles
* Moving doors/walls/gates
* Windmills and other machines
Targeted coordinate systems: The Translation is in Global coordinates, the Rotation in Local coordinates
* Say: a move on the X-axis will move the object along the global, region X-axis no matter how the object is rotated
* Say: a rotate around the X-axis will rotate the object around it's local, prim X-axis no matter the object's rotation
* When the object is not rotated in the global system you won't notice the difference
|signature=
{{LSL Const/Signature|KFM_MODE|integer}}
{{LSL Const/Signature|KFM_LOOP|integer}}
{{LSL Const/Signature|KFM_REVERSE|integer}}
{{LSL Const/Signature|KFM_FORWARD|integer}}
{{LSL Const/Signature|KFM_PING_PONG|integer}}
{{LSL Const/Signature|KFM_DATA|integer}}
{{LSL Const/Signature|KFM_TRANSLATION|integer}}
{{LSL Const/Signature|KFM_ROTATION|integer}}
{{LSL Const/Signature|KFM_COMMAND|integer}}
{{LSL Const/Signature|KFM_CMD_STOP|integer}}
{{LSL Const/Signature|KFM_CMD_PLAY|integer}}
{{LSL Const/Signature|KFM_CMD_PAUSE|integer}}
|cat1=Physics
|cat2
|cat3
|cat4
}}

Limits

2011-09-13T09:31:10Z

Stickman Ingmann: Limit of 5000 IMs per object per hour.

<noinclude>{{KBmaster}}</noinclude>
== Summary ==
{{RightToc}}
The Second Life Viewer and simulators have a division of labor, keeping track of the data that makes Second Life run. The Viewer's job is to:

* Handle locations of objects.
* Get velocities and other physics information, and does simple physics to keep track of what is moving where.

The simulator's job is to:

* Run the physics engine.
* Detect collisions.
* Keep track of where everything is
* Send locations of content to the Viewer along with updates when certain changes occur.

Limits are necessary for all of these components to work together. The list below outlines many of the '''Second Life numerical limits that affect your inworld experience'''. Some of these will likely change over time, so if you spot something incorrect/outdated, please take a moment to update it.

{{KBcaution|1=The scope of this page is focused on Linden Lab's official Viewers, keeping in mind [[Third_Party_Viewer_Directory|3rd-party viewers may differ]]. Cite sources and provide substantiation for limits that aren't provided by Linden Lab. Also, unconfirmed speculation [[Talk:Limits|goes on this discussion page]]. Don't add data without a hard limit, and don't add obscure trivia that doesn't practically affect the general inworld experience.}}

== [[Avatar]] ==

* '''Max. # of attachment points''' - 30 for avatar, 8 for [[HUD]].
** They can be viewed by right-clicking your avatar and choosing '''Take Off''' > '''HUD''' or '''Detach'''.
** With the formal introduction of [[multiple attachments|multiple attachments to a single point]] in Viewer 2.4, you can attach up to 38 total objects, and they can all be attached to a single point.
* '''Max. unassisted fly height''' - Stable hover almost 150m above the ground (terrain mesh).
** You can easily acquire a flight attachment to fly high. Also see [[flight limit]] and [[Limits#Navigation|the Navigation section]] below.
* '''Common shoe sizes''' - Most women's shoes are designed for a size 0 (zero) foot. Men's generally scale up to 14.
** You can check this by going to Edit menu > Appearance and clicking on the Shape > Legs tab.

* '''Max. length of avatar name''' - 31 for first name, 31 for last name, 63 in total (including the space).
* '''Max. avatar speed''' - 250m/s (with only attachments to assist)
* '''Max. teleport speed'''
** '''Server 1.27.1''' - 10 teleports per 15 seconds
** '''Server 1.27.0''' - 3 teleports per 15 seconds

== [[Animation]] ==

* '''Max. length of animation:''' 30.0 seconds
* '''Min. animation priority:''' 0
* '''Max. animation priority:''' 4

== Building ==

* '''Max. [[prim]] dimensions (non-[[megaprim]])''' - 64×64×64m
** it was 10×10×10m before SL Server 3.0.0 (238864)
* '''Min. prim dimensions''' - 0.01×0.01×0.01m
* '''Max. # of prims in a linkset''' - 256
** It was 255 before SL Server 1.26.
* '''Max. link distance''' - See [[Linkability Rules]].
* '''Max. # of prims in a physical object''' - 32
** If you try to link more, it'll either say "Can't enable physics for objects with more than 32 primitives" or "Object has too many primitives -- its dynamics have been disabled.".
** On server versions 1.38 and below, each sitting avatar counted as 1 prim. From 1.40.2 the limit is only on actual prims.
* '''Max. build or rez height''' - 4,096m
** This is 768m for Viewers prior to SL 1.20
* '''Max. prim name length''' - 63 bytes UTF-8 [[string]]
** Note: This is the same total character limit as avatar names.
* '''Max. prim description length''' - 127 bytes UTF-8 [[string]]
** Note:
* '''Temporary prim lifetime''' - around 60 seconds
* '''Max. number of temporary prims''' - regular_prim_limit - current_regular_prims + minimum(0.5 * regular_prim_limit + 400, 1000)
** From [http://forums-archive.secondlife.com/8/cd/305651/1.html Andrew Linden's February 2009 discussion])
* '''Max. length of hovertext (via [[llSetText]] or [[PRIM_TEXT]])''' - 254 bytes UTF-8 [[string]]

== Chat (text) ==

* '''Whisper distance''' - 10 m
* '''Chat distance''' - 20 m
* '''Shout distance''' - 100 m
** ''Rule of thumb:'' when you're at default zoom ('''View''' > '''Reset View'''), if you can see another person's nametag, they can see your chat. If they're far enough away that you don't see a nametag, they won't "hear" you unless you shout.
** Text spoken as a "Chat" step in a gesture cannot be shouted or whispered
** Text spoken as "Replace with" text in a gesture can be whispered or shouted in Viewer 2 either by putting <code>/whisper</code> or <code>/shout</code> at the start of the "Replace with" text or by typing <code>/whisper</code> or <code>/shout</code> at the beginning of the nearby chat input bar, followed by the gesture's trigger text. (Though, if you do both, or if a gesture with built-in <code>/whisper</code> or <code>/shout</code> is used mid-sentence, the "/whisper" or "/shout" will appear literally.) Viewer 1 does not honor <code>/whisper</code> or <code>/shout</code> and will always send them literally.
* '''Max. length of a chat message''' - 1023 bytes/single-byte characters
** The same holds true for an IM <-> email replies.
*** When the receiver is offline, if they set an IM to Email feature ('''Edit''' > '''Preferences''' (or press {{K|Ctrl|P}}), go to the '''Communication''' tab and check the '''Send IM to Email''' checkbox), it will send offline messages directly to the mailbox connected to your account. When an offline message is received via Email, this message can also be answered via Email again. The length of properly delivered Email replies is limited to 1023 bytes/single-byte characters.
* '''Capped''' - Maximum number of offline messages (involving [[IM]]s, inventory offers, group notices and group invitations) received before messages get capped is 25.
** Senders can't know whether their messages were capped or not.
* '''Email -> IM''' replies can be sent up to 5 days after receiving the offline IM the email is meant to answer.<sup>[<span class="plainlinks">[https://blogs.secondlife.com/community/features/blog/2007/02/06/im-to-e-mail-return-addresses-changing blog]</span>]</sup>
* '''IMs''' are retained on Linden Lab's servers for up to 31 days before being discarded. For example, if someone sends you an Instant Message and the next time you login is 33 days later, you won't get it.
** Torley confirmed this with Kelly Linden.
* The number of '''IMs''' an object can send in one hour is 5000.

== [[Gesture]]s ==

* '''Shortcut key mapping:''' 33 unique combinations, since {{K|F2}}–{{K|F12}} can be used with the {{K|Ctrl}} or {{K|Shift}} modifiers.
* '''Maximum Chat step length:''' 127 single-byte characters.
* '''Maximum Wait time:''' 3600 seconds (one hour).

== [[Group]]s ==

* '''Maximum number of groups you can belong to:''' 42
** Roles within groups are sort of like sub-groups. In many cases, you can use them instead of creating new groups.
* '''Minimum number of members in a group:''' 2
** A group with only 1 person for 48 hours will be disbanded (cancelled). Unless the group owns land.
* '''Maximum number of roles allowed in a group:''' 10 (including "Owners" and "Everyone", which cannot be deleted)
* '''Maximum Group Name:''' 35 single-byte characters.
* '''Maximum Group Title:''' 20 single-byte characters.
* '''Maximum Length of a Group Notice:''' 512 single-byte characters.

== [[Inventory]] ==

* '''Maximum number of inventory items that can be sent in a folder:''' 42
** Folders count as items too. This has more to do with packet size limits than cheeky Douglas Adams references.
* '''Maximum notecard line:''' None, but scripts can only read the first 255 bytes.
* '''Maximum notecard size:''' 65,536 bytes
* '''Number of items in the Library:''' 1,248 as of 2010-06-17
** Verified by [[How_does_the_Library_work|hiding the Library]] and counting the difference.

== [[Land]] ==

* '''Maximum [[Land#Parcel|parcel]] size:''' 65,536 meters²
** Covering a whole region, or square on the World Map.
* '''Minimum parcel size:''' 16 meters²
* '''Maximum parcel name length:''' 63 single-byte characters
* '''Maximum parcel description length:''' 255 characters
* '''Region name length:''' Under Linden Concierge policy, minimum of 3 characters, and a maximum of 25 characters (including spaces). See [[Linden Lab Official:Guidelines for Private Region Naming|Guidelines for Private Region Naming]].
** Rare exceptions exist, like [http://slurl.com/secondlife/Q/128/128/24 Q].
* '''Maximum "NO ENTRY" ban line height:''' 768 meters above the terrain mesh.
** This is if you are explicitly banned from a parcel. If the parcel is simply not public access or restricted to certain Residents or a group, then the access lines go up to 50 meters above the terrain mesh.
* '''Maximum prims in a [[Land#Region|region]]:'''
** Full region: 15,000
** [[Land#Homestead|Homestead]]: 3,750
** [[Land#Openspace|Openspace]]: 750
* '''Maximum auto return value''': Besides "0" (which means ''never''), {{HoverText|999,999|Almost 23 months}} minutes is the highest auto return value.
* '''Terraforming limits:'''
** Most mainland can be raised/lowered by 4 meters (+/-).
** Some mainland cannot be terraformed, including: Bay City Regions, Blumfield, Boardman, Brown, De Haro, Nautilus City Regions, Nova Albion Regions, Shermerville Regions, and West Haven.
** A few, very old mainland Regions like Da Boom have a terraform range of 40 meters (+/-).
** Estate (private island) terraformability is settable to a maximum of 100 meters (+/-) by the estate owner or managers.
* '''Maximum water height:''' 100 meters using inworld controls (mainland limit), 255 meters by using a *.raw file upload.
** Region water height is usually 20 meters, and adjacent regions should have the same water height, or else they will look discontinuous.
* '''Maximum terrain height:''' 255 meters using inworld controls (mainland limit), 510 meters by using a *.raw file upload.
* '''Miscellaneous estate limits:''' You can have a maximum of 10 estate managers, 500 allowed Residents, 63 allowed groups, and 500 banned Residents.
** See World menu > Region/Estate > Estate tab.
* '''Mainland maximum number of agents'''
** Full region: 100 (Historically set to 40 by LL but this does vary. Some meeting areas have this set to 60 and higher.)
*** Recent server performance improvements make regions with 60 agents in them perform quite well excepting the issue described in {{JIRA|SVC-3895}}.
** [[Land#Homestead|Homestead]]: 20
** [[Land#Openspace|Openspace]]: 10
* '''Island maximum number of agents:'''
** Full region: 100
** [[Land#Homestead|Homestead]]: 20
** [[Land#Openspace|Openspace]]: 10
* '''Freeze Time:''' Land owners can [[freeze]] other Residents for up to 30 seconds. Members of land owning groups can also be granted this ability.
* '''Minimum parcel that can be listed in Places or All search:''' 144 meters² 
* '''Minimum parcel that can be listed in Events:''' 512 meters²
* '''Maximum altitude for event listings:''' 768 meters ({{JIRA|WEB-814}})
* '''Maximum heights that objects can be seen on the [[World Map]]:''' 400.005m
* '''[[Classic clouds]] layer:''' Approximately 150-225 meters, although the edges of particles can appear to exceed that.

== Misc. ==

*'''[https://secondlife.com/currency/describe-limits.php Billing and Trading Limits]''' - Includes [https://secondlife.com/whatis/economy-market.php LindeX] currency exchange limits.
*'''Contacts in Communication > Friends tab ''' - A maximum of 20 simultaneous contacts can be selected to change permissions, remove, or invite for a conference chat.

== Navigation ==

[[File:Max Alt.jpg|thumb|right|435px|'''Height counter error above 2147483647 meters''']]
* '''Absolute height limit:''' [http://en.wikipedia.org/wiki/2147483647#2147483647_in_computing 2147483647] = 2<sup>31</sup> − 1 meters, which causes the altitude counter to roll over. Altitudes well below this cause graphics errors probably due to limited floating point number precision.
* '''Highest z-value of an [[SLurl]], that will still teleport you to a positive altitude:''' 2147483583
** This is lower than the ''Absolute height limit'' above probably because of precision issues. Any value higher than 2147483583 would be rounded up to something beyond 2147483647 and thus cause an [http://en.wikipedia.org/wiki/Arithmetic_overflow overflow], while 2147483583 will still be rounded down to 2147483520 (see below).
* '''Highest altitude you can teleport to with an SLurl:''' 2147483520 meters

== [[Profile]] ==

Each 7-bit ASCII character is encoded in one byte. International characters might need more bytes. When pasting text instead of typing, you can get in one byte more into each of the below.

* '''2nd Life tab's About field''' - 510 bytes
* '''Picks tab''' - 10 picks with 1022 bytes each
* '''1st Life tab's Info field''' - 253 bytes
* '''Classified tab''' - 100 listings with x bytes each
* '''My Notes''' - 1022 bytes

== Performance ==

* '''Healthy Viewer FPS''' - Generally, FPS above 15 is good. The higher it gets, the smoother. You can check via Help menu > Lag Meter, or for more advanced usage, see View menu > Statistics Bar.
* '''Avatar Rendering Cost scores''' - [[Avatar Rendering Cost|Learn all about it!]]

== [[Scripting]] ==

* '''Height at which scripts reactivate on a no-script parcel''' - 50 m above terrain mesh. Scripted objects that take controls continue to remain active when you fly down or enter a no-script parcel.
* '''Maximum height where scripts can run''' - none, as long as the object remains rezzed or attached.
* '''Maximum script source code size''' - 65536 single byte characters.
* For specific scripting limits, lookup calls in the '''[[LSL Portal]]'''.

== [[Textures]] ==
* '''[http://en.wikipedia.org/wiki/Aspect_ratio Aspect ratios]''' of profile, place, etc. pictures — all of these were measured at UI size (Edit menu > Preferences > General tab > UI Size) = 1.000:

=== 1.x Series Viewers ===

(official Viewer up to 1.23.5, most [[Alternate viewers|Third Party Viewers]])
* '''Search > All for "Classifieds", "People", and "Places"''' - 4:3 (256×192 pi×els)
* '''Search > Places and Classified tabs''' - ~7:5 (398×282 pixels)
* '''Search > Land tab''' - ~7:5 (358×252 pixels)
* '''Profile > 2nd Life tab''' - ~4:3 (178×133 pixels)
* '''Profile > Picks tab''' - 16:9 (288×162 pixels)
* '''Profile > 1st Life tab''' - 1:1 (133×133 pixels)
* '''Profile > Classifieds tab''' - ~3:2 (206×137 pixels)
* '''Profile > Web tab''' - 1:1 (400×400 pixels)
** A scrollbar uses 15 pixels on the right-hand side.
* '''About Land > Options tab''' - ~3:2 (178×117 pixels)
* '''Group Information > General tab's "Group Insignia"''' - 1:1 (126×126 pixels)
** Some of these textures are shared (for example, Search > All place pages, Search > Places, and About Land > Options use the same image), so you should pick a well-balanced ratio and size.
** [[Texture_aspect_ratios|Learn how to get correct texture aspect ratios when editing images.]]

=== 2.x Series Viewers ===

* '''Search > Classifieds thumbnail''' - 4:3 (60×45 pixels)
* '''Search > Classifieds expanded''' - ~4:3 (252×188 pixels)
* '''Search > Classifieds expanded > Details''' - 17:7 (272×112 pixels)
* '''Search > People''' - 4:3 (188×141 pixels)
* '''Search > Destination Guide thumbnail''' - ~4:3 (45×34 pixels)
* '''Search > Destination Guide expanded''' - 5:3 (250×150 pixels)
* '''Profile > 2nd Life tab''' - ~1:1 (100×99 pixels)
* '''Profile > Picks thumbnail''' - 8:5 (88×55 pixels)
* '''Profile > Pick expanded''' - ~5:3 (285×172 pixels)
* '''About Land > Options tab''' - ~20:13 (193×125 pixels)
* '''Places > More information''' - ~11:7 (272×173 pixels)

=== All Viewers ===

* '''Maximum texture size''' - 1024×1024 pixels
** All Second Life textures are constrained to [http://en.wikipedia.org/wiki/Power_of_2 powers of 2] (e.g., 128, 256, 512).
** Some textures inworld have a resolution as high as 2048×2048; this is due to a previous limit that was higher.
** We strongly recommend you use as small textures as possible because larger ones consume more memory and take substantially longer to load.
** Where large textures are being forced by import to only 512×512, lower your ...> Preferences >...> UI Size under 1.0, to increase import size to the max 1024×1024.

[[Category:Creation]] [[Category:Tutorials]] [[Category:Lists]]

Content Creation/Mesh Import User Group

2011-08-01T19:31:20Z

Stickman Ingmann:

{{User Group Page
|purpose=
Currently topics are focused on anything related to the mesh import project. Feature requests, bug reports, design feedback, questions, comments, or example content are welcome.

Priority will be given to topics that are posted in advance and are relevant to the goals of the office hour. Feel free to include relevant links to JIRA or wiki pages.
<br clear="all"/>
{{Navbox/Mesh|project}}
|date-time=
Mondays at Noon in Pacific time (SL standard time)

Next meeting scheduled for: '''July 18, 2011'''
|location=
[secondlife://Aditi/secondlife/MeshHQ%201/214/243/23 Mesh HQ on Aditi]

|team=
Charlar Linden, Nyx Linden, and Runitai Linden. Please contact one of us if you are unsure if your topic is relevant or appropriate.
|agenda=
<br><br>
Please add topics below '''prior to 11:50 AM'''. Also, please put your SL name down so we can follow up if we have questions. Thanks!

Enter agenda items here (with name, please)
# Why do mesh objects have a +0.5PE penalty and a +1PE script penalty per object per linkset compared to regular prims which have none? (York Jessop)
# Can we have both physics and streaming cost displayed somewhere in the edit window? It was useful to be able to tell which was larger without having to go into the developer menu. (Brookston Holiday)
# (Perhaps related)When edit linked is checked, the number of prims gets updated in the edit window but the PE of the entire object is still shown. Is it possible to show the PE contribution of the one prim that has been selected, again without going into developer menu? (Brookston Holiday)
# What is the hidden agenda (assuming there is one) behind the new dropdown on the uploader that asks what the uploaded model is for? [Drongle McMahon]
# SH-2044 has been set to fixed, but the automated build at http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/mesh-development/rev/237321/index.html doesn't seem to have the fix even though it's listed. It's likely a mistake on my part, but please confirm whether the fix is in or not in the install. (Raz Welles)
#I'm having problems getting the streaming cost formula to work. Is this wiki up-to-date? : http://wiki.secondlife.com/wiki/Mesh/Mesh_Streaming_Cost#LOD_Transition_Distances I read elsewhere that the LOD transition distances have different values now. Also, is "max_area=65536", "cost_scalar = 0.125" and is "radius = 0.5 * llSqrt(x*x + y*y + z*z)"? [Ashasekayi Ra]
#In the streaming cost formula, kbytes for each LOD are listed. Is there a way to approximate that value for ourselves offline since I assume this is a compressed value? [Ashasekayi Ra]
#You still can't have textures automatically load with a model exported from Blender 2.49. Is this a known issue? Or, does it need a jira? [Ashasekayi Ra]
#Adding a script to a linkset that has a PE count lower the the prim count results in rounding up to the prim count and voiding out any efficient mesh models that are below 1 PE in a linsket... why? My example was a 128 prim, 64 PE going up to 130 PE whit a "new script" added... [Moo Spyker]
#In the modernisation of SL, why has all effeort for new features seemed to be targeted at Mesh? I feel that the biggest immersion killer, and the area where SL is lagging behind other MMOs the most, right now is not having seamless sim crossings, and not being able to traverse the seas. [Davido Chrome]
#Please can you add to the Loginscreen from the Mesh Cleint Links to the mesh-wiki tips for handle the mesh upload. [bigjr Slade]
#When can we expect a viewer version that works with lion (macOS 10.7)? [Mikki Miles]
#Jira CTS-606 is marked as fixed, but it isn't. I made a comment, but i suspect nobody read it. So, on both my machines, MBP and a recent iMac I get a black screen when I try to display physic shapes, it would really be helpful to have this working [Mikki Miles]
#How do normal prims and meshes compare in rendering cost? Comparing, say, 1024 prim-based triangles and 1024 mesh-based triangles. [Stickman Ingmann]

|archive=
{{:Content_Creation,_Mesh_Import_User_Group/Archive}}
}}
[[Category:Mesh]]

Mesh/Troubleshooting

2011-06-21T01:26:12Z

Stickman Ingmann: /* Rigging */ Missing linebreak

{{Multi-lang}}
{{Navbox/Mesh}}

To troubleshoot your model, please make sure your model complies with these guidelines.

If the problem you're having isn't covered here, please check the tool-specific pages on [[:Category:Mesh|this wiki]] and the [http://blogs.secondlife.com/community/forums/mesh mesh forum].

===COLLADA file format===
We support the COLLADA 1.4 specification.

===Export triangles===
We support triangles and polygons, not nurbs, surface patches, etc.

===Skin weights===
We support up to 4 influences per vertex.

===Rigging===
Your skeleton names and hierarchy must match the [[Avatar_Appearance#Linden_skeleton_definition_file|Second Life avatar skeleton]].

''Note: The following was pulled directly from the XML file mentioned in the above link. It includes an extra "head" bone (mSkull) which is, I believe, where the avatar's hair rest and the "skull" attachment point resides, and the mToeLeft and mToeRight bones, which are more than I expected to exist on the foot as I've been wanting a toe bone for years. I haven't tested if these are usable, animating bones yet.'' -[[User:Stickman Ingmann|Stickman]] 18:21, 20 June 2011 (PDT)

That is, your skeleton should include the following bones:

'''Torso and Head'''
*mPelvis (root)
*mTorso (child of mPelvis)
*mChest (child of mTorso)
*mNeck (child of mChest)
*mHead (child of mNeck)
*mSkull (child of mHead)
*mEyeRight (child of mHead)
*mEyeLeft (child of mHead)
'''Arms'''
*mCollarLeft (child of mChest)
*mShoulderLeft (child of mCollarLeft)
*mElbowLeft (child of mShoulderLeft)
*mWristLeft (child of mElbowLeft)
*mCollarRight (child of mChest)
*mShoulderRight (child of mCollarRight)
*mElbowRight (child of mShoulderRight)
*mWristRight (child of mElbowRight)
'''Legs'''
*mHipLeft (child of mPelvis)
*mKneeLeft (child of mHipLeft)
*mAnkleLeft (child of mKneeLeft)
*mFootLeft (child of mAnkleLeft)
*mToeLeft (child of mFootLeft)
*mHipRight (child of mPelvis)
*mKneeRight (child of mHipRight)
*mAnkleRight (child of mKneeRight)
*mFootRight (child of mAnkleRight)
*mToeRight (child of mFootRight)

===Model size===
If the model you're importing is too small or too big, please check the unit settings in your modeling software.

===Axis===
In Second Life, the Z-axis is the vertical axis.

Mesh/Exporting a mesh from Blender

2011-06-21T01:25:01Z

Stickman Ingmann: /* Bones and rigging */ Added useful links.

{{Multi-lang}}
{{Navbox/Mesh}}
== Video tutorial ==

Check out this '''[http://blog.machinimatrix.org/3d-creation/blender-meshes-trail/ 3-part Blender tutorial for static meshes.]'''

There's also a detailed Blender rigging tutorial here: '''BlanderMan rigging tutorial [http://vimeo.com/5067809 part 1-1], [http://vimeo.com/5068722 part 1-2], [http://vimeo.com/5070359 part 2]'''.

=== Simple tube avatar ===
{{KBvideo|3JHWDdrIeD0|640|505|type=youtube}}

=== Mancandy avatar ===
{{KBvideo|8w88B7F7v_k|640|505|type=youtube}}

== Basic workflow ==
=== Create a box (or monkey or teapot or hippo) ===
=== Reduce polygons ===

The easiest way to reduce the polygon count of your mesh is via the "Poly Reducer" script, accessible via the Mesh -> Scripts -> Poly Reducer. This script reduces the number of polygons in the model without affecting its shape, much like the "Decimate" tool, but also maintains the mesh's UV mapping.

To quickly and easily produce a set of LOD meshes:
# Make sure your blender file is saved
# Export your full-detail mesh to COLLADA
# Run Poly Reducer with a poly reduce setting of 0.5 (to reduce your polygon count by half).
#* If you make any manual changes to tweak the resulting mesh, remember to update the UV map to match.
# Export your mesh to COLLADA; this will be the "medium" level of detail.
# Reload your original full-detail mesh. It's good to start from the full-detail mesh each time to prevent errors from accumulating, though this may not be a significant concern for simple meshes such as attachments.
# Run Poly Reducer with a poly reduce setting of 0.25 (to reduce your polygon count by three quarters).
# Export your mesh to COLLADA; this will be your "low" level of detail.
# Reload your original full-detail mesh.
# Run Poly Reducer with a poly reduce setting of 0.125 (to reduce your polygon count by seven eighths).
# Export your mesh to COLLADA; this will be your "lowest" level of detail. You may also want to use this mesh when defining your model's physics.

Unfortunately the Poly Reducer script is currently only available for version 2.4x of Blender. The "Decimate" modifier is a serviceable substitute but the downside is that you'll need to redo the UV map for each LOD level.

=== Apply textures ===
=== Scale to meters ===
Scaling is somewhat arbitrary. In principle you just have to know how the mapping is between your 3D program (Blender) and the target environment (Second Life). Then all you need to do is to work in the correct scale. You even can later rescale your model in your target system.

So, what is the issue with blender ? It is all so simple that the Collada Exporter for blender assumes that one Measurement Unit is mapped to one real life centimeter. But the common expectation in Second Life is that one Measurement Unit is mapped to 1 Second Life Meter. Unfortunately this missmatch very often leads to the import of "tiny objects". The common fix is to scale up the models in Blender by a factor of 100.

But there is a nicer fix, which adjust the Collada Exporter to behave according to our expectations.
See this video to find out, how you can fix the Measurement missmatch between Blender-2.49b and Second Life once and for ever:

{{KBvideo|18354783|640|370|type=vimeo}}

If you don't want to watch the entire video:

find the file <blender script dir>\bpymodules\colladaImEx\translator.py and change these two lines:

daeAsset.unit.name = 'centimeter'
daeAsset.unit.meter = '0.01'

to

daeAsset.unit.name = 'meter'
daeAsset.unit.meter = '1.00'

To find the scripts directory, do Help > System Information in blender, and look in the text file for "Default dir for scripts:". The path for me is:
C:\Documents and Settings\tapple\Application Data\Blender Foundation\Blender\.blender\scripts
and thus the file is:
C:\Documents and Settings\tapple\Application Data\Blender Foundation\Blender\.blender\scripts\bpymodules\colladaImEx\translator.py

=== Export to COLLADA ===
=== Import to SL ===

== Best Practices ==
[http://blogs.secondlife.com/message/460796#41935 Forum thread on optimizing your mesh in Blender for Second Life]

[http://blogs.secondlife.com/message/552002#552002 Forum thread on installing Blender]
=== Bones and rigging ===
It's possible to import one of the default BVH animations that can be found linked in the header of the [[Internal_Animations#User-playable_animations]]. This will get you a slightly inaccurate skeleton to work from.

Please note that the bones are all the wrong names for mesh import, as mentioned in [[Mesh/Troubleshooting#Rigging]].

[http://blogs.secondlife.com/message/534554#52305 Forum tip for exporting joint positions with Blender]

=== Gotchas and workarounds ===

=== Optimization techniques ===

== Tutorial links ==
== Blender 2.5x specefic ==

http://blog.machinimatrix.org/3d-creation/blender-meshes-trail/

http://blendernewbies.blogspot.com/search/label/Blender%202.5

http://www.blendercookie.com/tag/2-5/

http://www.blenderguru.com/whered-that-button-go/

http://totallyblended.com/New/?page_id=705

http://blendernerd.com/?cat=5

https://sites.google.com/site/satishgoda/blender

http://3d-synthesis.com/tutorialsenglish.html

http://www.youtube.com/user/super3boy (has been updating his tutorials for 2.5)

http://www.katsbits.com/tutorials/index.php

http://cogfilms.com/index.html

http://www.3dbuzz.com/vbforum/showthread.php?188849-Blender-Fundamentals-First-drop-of-videos-now-available-to-the-public

Mesh/Troubleshooting

2011-06-21T01:21:30Z

Stickman Ingmann: Added the hierarchy skeleton to the page, as found in the XML file.

{{Multi-lang}}
{{Navbox/Mesh}}

To troubleshoot your model, please make sure your model complies with these guidelines.

If the problem you're having isn't covered here, please check the tool-specific pages on [[:Category:Mesh|this wiki]] and the [http://blogs.secondlife.com/community/forums/mesh mesh forum].

===COLLADA file format===
We support the COLLADA 1.4 specification.

===Export triangles===
We support triangles and polygons, not nurbs, surface patches, etc.

===Skin weights===
We support up to 4 influences per vertex.

===Rigging===
Your skeleton names and hierarchy must match the [[Avatar_Appearance#Linden_skeleton_definition_file|Second Life avatar skeleton]].

''Note: The following was pulled directly from the XML file mentioned in the above link. It includes an extra "head" bone (mSkull) which is, I believe, where the avatar's hair rest and the "skull" attachment point resides, and the mToeLeft and mToeRight bones, which are more than I expected to exist on the foot as I've been wanting a toe bone for years. I haven't tested if these are usable, animating bones yet.'' -[[User:Stickman Ingmann|Stickman]] 18:21, 20 June 2011 (PDT)

That is, your skeleton should include the following bones:
'''Torso and Head'''
*mPelvis (root)
*mTorso (child of mPelvis)
*mChest (child of mTorso)
*mNeck (child of mChest)
*mHead (child of mNeck)
*mSkull (child of mHead)
*mEyeRight (child of mHead)
*mEyeLeft (child of mHead)
'''Arms'''
*mCollarLeft (child of mChest)
*mShoulderLeft (child of mCollarLeft)
*mElbowLeft (child of mShoulderLeft)
*mWristLeft (child of mElbowLeft)
*mCollarRight (child of mChest)
*mShoulderRight (child of mCollarRight)
*mElbowRight (child of mShoulderRight)
*mWristRight (child of mElbowRight)
'''Legs'''
*mHipLeft (child of mPelvis)
*mKneeLeft (child of mHipLeft)
*mAnkleLeft (child of mKneeLeft)
*mFootLeft (child of mAnkleLeft)
*mToeLeft (child of mFootLeft)
*mHipRight (child of mPelvis)
*mKneeRight (child of mHipRight)
*mAnkleRight (child of mKneeRight)
*mFootRight (child of mAnkleRight)
*mToeRight (child of mFootRight)

===Model size===
If the model you're importing is too small or too big, please check the unit settings in your modeling software.

===Axis===
In Second Life, the Z-axis is the vertical axis.

Mesh/Uploading a multi-face mesh

2011-06-18T00:28:46Z

Stickman Ingmann: Added links to the Blender manual that explain material manipulation.

{{Multi-lang}}
{{Navbox/Mesh}}
__NOTOC__

[[File:MeshWalkthrough-Complex_Mesh_Upload-Splash.png|300px]]

Just as we can texture individual faces of a primitive differently, we can texture individual faces of meshes differently if the mesh has been properly set up for materials before import.

{{KBvideo|qorvd6KJSuE|640|505|type=youtube}}

== Adding Materials With Your 3D Program ==
To add Materials in Blender, refer to these two pages in the Blender Manual regarding creating/adding materials, and applying multiple materials to a model.
* http://wiki.blender.org/index.php/Doc:2.5/Manual/Materials/Options
* http://wiki.blender.org/index.php/Doc:2.5/Manual/Materials/Multiple_Materials

== Get a Second Life compatible mesh file ==
The first step is to get a multi-face mesh file that you want to upload to Second Life. Second Life's mesh import is able to read [https://collada.org/mediawiki/index.php/COLLADA_-_Digital_Asset_and_FX_Exchange_Schema COLLADA] ("''.dae''") files.
# Click this link -- https://collada.org/owl/download.php?sess=0&parent=131&expand=1&order=name&curview=0&binary=1&id=707 -- to download the "''seymour.dae''" COLLADA file.
# Save the file anywhere on your hard drive where you can find it later.

== Upload the mesh file to Second Life ==
[[File:Mesh_upload_model_seymour.png|300px|thumb|Upload Model window]]
Upload the mesh file from your computer to Second Life:
# Select '''Build''' > '''Upload''' > '''Model''' from the menu at the top of the Second Life Viewer.
#: Alternatively, open '''My Inventory''', click the '''+''' button, and select '''Upload''' > '''Model'''.
#: A file upload window opens.
# Find and select the <code>seymour.dae</code> file from your computer.
#: The Upload Model window appears.
# Enter a name for your model in the '''Name''' field.
# Click the '''Upload''' button.
#: Two new assets appear in your inventory: one in your '''Meshes''' folder, the other in your '''Objects''' folder.
#: For the seymour object, these new assets are named '''boyShape'''.
#: Note: In this tutorial, we only care about the asset in your '''Object''' folder.
{{Warning|While the Seymour asset does contain a rig, it is incompatible with the current Mesh Project Viewer code. If you enable '''Skin Weight''', Seymour's skin will be generated incorrectly. You'll see the incorrect behavior in the tool preview window, and if uploaded, you'll see a group of large flickering triangles inworld.}}

== Add your mesh object to the world and edit it ==
[[Image:MeshWalkthrough-Complex Mesh Upload-Edit Face.png|right|300px|thumb|Edit goggle color]]
You can now manipulate your mesh as if it were any other object in your inventory:
# Find your '''boyShape''' object in your '''Objects''' folder; if you're having trouble or have a large inventory, use your inventory's '''RECENT''' tab.
# Drag the new object from your '''Objects''' folder to anywhere on the ground where you have permissions to build.
#: The model appears on the ground.
# Right-click the model and select '''Edit'''.
#: The Edit Object window appears.
# Click the '''Select Face''' radio button.
# Left-click the goggle lenses of the model.
# Click the color swatch in the Texture tab and change the color, or click the texture swatch and change the texture.
# Add color and/or textures to other parts of the model (gloves, goggle frame, face, or cap) in the same way.

Continue on to '''[[Mesh/Uploading and wearing a rigged mesh|Uploading and wearing a rigged mesh]]'''.

Content Creation, Mesh Import, Scripting User Group

2011-06-13T19:14:40Z

Stickman Ingmann:

{{User Group Page
|purpose=
Although the header says "Content Creation/Mesh Import/Scripting", currently topics are focused on anything related to the mesh import project. Feature requests, bug reports, design feedback, questions, comments, or example content are welcome.

Priority will be given to topics that are posted in advance and are relevant to the goals of the office hour. Feel free to include relevant links to JIRA or wiki pages.

|date-time=
Mondays at Noon in Pacific time (SL standard time)

Next meeting scheduled for: '''June 13, 2011'''

|location=
[secondlife://Aditi/secondlife/MeshHQ%201/251/250/24 Mesh HQ on Aditi]
|team=
Charlar Linden, Nyx Linden, and Runitai Linden. Please contact one of us if you are unsure if your topic is relevant or appropriate.
|agenda=
<br><br>
Please add topics below '''prior to 11:50 AM'''. Also, please put your SL name down so we can follow up if we have questions. Thanks!
# I thought the decision to limit mesh uploads to payment info on file/used was discussed and shot down a long time back during the closed beta days. Why has it returned all of a sudden as a near-certainty? (Tiberious Neruda)
# It seems there are upload issues with specific Collada files. Namely, Collada v1.4.0 is ok, but the newer v1.4.1 files (as outputted from i.e. 3dsMax2012) show problems. (Forum post at http://community.secondlife.com/t5/Mesh/Collada-Version-Supported/m-p/923127 ). Therefore which Collada version(s), XML tags, or 3D programs are *supported* by the Second Life model importer? Supported = if it doesn't work, you will treat it as a bug in the importer. (DanielRavenNest Noe)
# An extra complication of the above issue remains the one described at JIRA CTS-603 which particularly seems to hit Maya users, even when the collada output is 1.4.0 (Maya 2011 with FBX 2011.x), due to the way the materials are handled with it. The viewer still ignores material names but sticks to the order that they are written in each LOD Collada file, resulting in jumbled materials. (Angel Alphaville)
# To expand on the above issues, the proper question is not whether we should waste time with specific programs (as put in the forum), but whether the 3D builder demographics are restricted strictly to Blender users or not. "Blender" is the most frequently written word in the forum as if it's the start and end of 3D software (which is not the case). (Angel Alphaville)
# Please update us on offset pivots, AssetPivot and potential use of <geometry> origin. [Drongle McMahon]
# Is it still true that a vertex can be assigned to a max of 4 groups? [Ashasekayi Ra]
# I'm still having an issue with the uploader closing the opening on an arch when Step 1: Analysis and Step 2: Simplification are used. http://community.secondlife.com/t5/Mesh/Physics-Uploader-Closing-Holes/td-p/924041 So, do I need to use Step 1 and Step 2 if the physics mesh that I created is low poly to begin with? (In this arch example, the physics mesh had 16 triangles.) Does the hull generated after Step 1 and 2 somehow make the physics shape more efficient? [Ashasekayi Ra]
#If I wanted to get the most accurate idea of how many prims a mesh object converts to, do I look at the "selection streaming cost" number under "Show Render Info"? [Ashasekayi Ra]
# Can you please update us on recent progress and tell us what your current priorities are? [Vivienne Daguerre]
# Is there anything in particular you need us to focus our testing on? [Vivienne Daguerre]
# In the recent and current mesh viewer, when I enable lighting and shadow my screen goes black. I can see things like the minimap and hovertext above my avatar, but HUD textures are messed up. I am using 2 ATI 5870 video cards in my Alienware laptop. Anyone else having this problem? The development viewer works just fine for me. Should I file a jira or are you aware of this issue? [Vivienne Daguerre]
# the black screen appears on my screen also when i set full screen (30''). When i make it smaller, the scene reappears. [Gaia]
# Why are slm files binary ? And does it make sense to get a generateable XML file instead to prepare for easy (scripted) support from 3D editors? See [[https://jira.secondlife.com/browse/CTS-634 CTS-634]] [Gaia]
# Is there documentation in laymen's terms yet? [Eleanora Newell]
# Is there a repository of videos on mesh techniques? I know Gaia is working on some thngs? I am looking specifically for information on offsetting bones for avatars that are micro and not human. [Eleanora Newell]
# Is there a matrix of what actually last known to be working build download works on which beta region?
# Recently Richard Linden marked http://jira.secondlife.com/browse/VWR-2242 as "fixed" but provided no information. Is this mesh related, or do I need to bug Andrew and Simon about it tomorrow to see if they have an answer? -[[User:Stickman Ingmann|Stickman]] 12:14, 13 June 2011 (PDT)
# please add your agenda items here

|archive=
* [[Content Creation, Mesh Import, Scripting User Group/Archive]]
* [[User:Nyx_Linden/Mesh_Office_Hours_Agenda_Archive|Older archives]]
}}
[[Category:Mesh]]

Face

2011-05-26T21:59:37Z

Stickman Ingmann: fixed bad emphasis

{{Help|Object=*}}
A [[prim]] has one or more '''faces''' (or '''sides''') depending on its basic shape and shape parameters. Each face of a prim can have its own [[texture]] properties, [[color]], [[alpha]], and attributes ([[shiny]], [[full-bright]], and [[bump-map]]). The texture properties that each face can have are: texture, texture map (standard or planar), scale, offset, and [[rotation]]. The properties of a prim face can be changed individually by using its face number or all of the prim faces can be modified at once using the <tt>[[ALL_SIDES]]</tt> face number.

Prims are formed by moving a circle, triangle, or square through a path in 3D space. For boxes, prisms, and cylinders the path is a line. For tori, rings, and tubes the path is a circle. For a sphere the path is rotation of a half-circle around a point. A circle (or half-circle) defines one face along its path, a triangle defines three faces along its path, and a square defines four faces along its path. The interior face of a hollow prim is always one face, even if the hollow shape is a triangle or a square.

===Using the face list table===
The following table lists all of the possible faces for the eight different prim types and the rule for whether a particular face exists. A given prim will have some subset of this list depending on its shape parameters. The face number of a prim face is determined by its position in the face list after non-existent faces have been removed. The first face in the list that exists will be face zero, the next existing face will be face one, and so on. The positions of the faces listed in the table are in the local coordinate space of the prim, assuming no twist. If beginning twist or end twist is non-zero then some faces will rotate with respect to the prim's local coordinate space.

{| {{prettytable}}
|| '''[[PRIM_TYPE_CYLINDER|Cylinder]]'''
* top (+z) ''always exists''
* outside ''always exists''
* hollow ''if hollow''
* bottom (-z) ''always exists''
* path cut begin ''if path cut''
* path cut end ''if path cut''
|| '''[[PRIM_TYPE_TORUS|Torus]]'''
* path cut end ''if path is cut or broken''
* outside ''always exists''
* hollow ''if hollow''
* path cut begin ''if path is cut or broken''
* profile cut begin ''if profile cut''
* profile cut end ''if profile cut''
|| '''[[PRIM_TYPE_SPHERE|Sphere]]'''
* path cut end ''if path cut or twisted''
* outside ''always exists''
* hollow ''if hollow''
* path cut begin ''if path cut or twisted''
* dimple begin ''if dimpled or hollow''
* dimple end ''if dimpled or hollow''
|-
|| '''[[PRIM_TYPE_PRISM|Prism]]'''
* top (+z) ''always exists''
* +y ''unless path cut away''
* -x ''unless path cut away''
* -y ''unless path cut away''
* hollow ''if hollow''
* bottom (-z) ''always exists''
* path cut begin ''if path cut''
* path cut end ''if path cut''
|| '''[[PRIM_TYPE_RING|Ring]]'''
* path cut end ''if path is cut or broken''
* inside face ''unless profile cut away''
* +x ''unless profile cut away''
* outside face ''unless profile cut away''
* hollow ''if hollow''
* path cut begin ''if path is cut or broken''
* profile cut begin ''if profile cut''
* profile cut end ''if profile cut''
||
|-
|| '''[[PRIM_TYPE_BOX|Box]]'''
* top (+z) ''always exists''
* -y ''unless path cut away''
* +x ''unless path cut away''
* +y ''unless path cut away''
* -x ''unless path cut away''
* hollow ''if hollow''
* bottom (-z) ''always exists''
* path cut begin ''if path cut''
* path cut end ''if path cut''
|| '''[[PRIM_TYPE_TUBE|Tube]]'''
* path cut end ''if path is cut or broken''
* outside face ''unless profile cut away''
* -x ''unless profile cut away''
* inside face ''unless profile cut away''
* +x ''unless profile cut away''
* hollow ''if hollow''
* path cut begin ''if path is cut or broken''
* profile cut begin ''if profile cut''
* profile cut end ''if profile cut''
||
|-
|| '''[[PRIM_TYPE_SCULPT|Sculpted]]'''
* outside ''always exists''
||
||
|}

Here are the face existence rules in greater detail:
* The outside face always exists on circle derived prims (sphere, cylinder, and torus)
* The top and bottom faces always exist on line path prims (cylinder, prism, and box)
* Both path cut faces exist if path cut begin > 0 or path cut end < 1
* Both path cut faces exist on circular path prims (torus, ring, and tube) if the circular path is broken: path cut, skewed, begin twist ≠ end twist, radius delta ≠ 0, revolutions > 1, or taper parameters ≠ 0
** ''even if begin twist &equiv; end twist ''mod'' 360''
* Both path cut faces exist on sphere prims if begin twist ≠ end twist (even if &equiv; ''mod'' 360)
* Both sphere dimple faces exist if either dimple begin > 0 or dimple end < 1 or hollow > 0
** ''even if you can't see the dimple face because dimple begin = 0 or dimple end = 1, it exists and can have its parameters set''
* The hollow face only exists if hollow > 0
* Both profile cut faces exist if profile cut begin > 0 or profile cut end < 1
* If the path cut of a prism or box completely eliminates a face then that face doesn't exist
* If the profile cut of a ring or tube completely eliminates a face then that face doesn't exist
* A face ''still exists'' even if it is shrunk all the way to a line or a point by the taper parameters

==== An example ====
If you have a box prim that has a path cut beginning of 0.30, a path cut ending of 1.00, and no hollow then your face list looks like this:
{|
{{LSL DefineRow|top (+z)|''always exists''}}
{{LSL DefineRow|-y|''doesn't exist because the path cut beginning is ≥ 0.25''}}
{{LSL DefineRow|+x|''exists''}}
{{LSL DefineRow|+y|''exists''}}
{{LSL DefineRow|-x|''exists''}}
{{LSL DefineRow|hollow|''doesn't exist because the hollow parameter is 0''}}
{{LSL DefineRow|bottom (-z)|''always exists''}}
{{LSL DefineRow|path cut begin|''exists because path cut beginning > 0''}}
{{LSL DefineRow|path cut end|''exists because path cut beginning > 0''}}
|}
So the face numbering for this prim is:
{| {{prettytable}}
| 0 || top (+z)
|-
| 1 || +x
|-
| 2 || +y
|-
| 3 || -x
|-
| 4 || bottom (-z)
|-
| 5 || path cut begin
|-
| 6 || path cut end
|}

===Finding the value of a face===
If you are unsure about which face number to use, following these steps will give you the face number to use.

* Enable the Develop menu by pressing {{K|Ctrl|Alt|Q}}. (On version 1.x viewers, instead enable the [[Advanced menu]] by pressing {{K|Ctrl|Alt|D}}.)
* Select the Face Using the "Select Texture" Tool
* Pick Develop > Rendering > Selected Texture Info from the menu, or press {{K|Ctrl|Alt|Shift|T}}

The face number will be shown in your local chat window.
[[Category:LSL Face| ]]

Content Creation, Mesh Import, Scripting User Group

2011-05-09T18:03:51Z

Stickman Ingmann:

LlWhisper

2011-04-23T00:07:52Z

Stickman Ingmann: Testing shows the limit is 1023 bytes.

{{LSL_Function/chat|channel|msg}}{{LSL_Function
|func_id=22
|func_sleep=0.0
|func_energy=10.0
|func=llWhisper
|sort=Whisper
|p1_type=integer|p1_name=channel
|p2_type=string|p2_name=msg
|func_desc=Whispers the text supplied in string '''msg''' on channel supplied in integer '''channel'''.
|return_text
|spec
|constants
|caveats=*Text can only be a maximum of 1023 bytes.
*Whispers can only be heard within 10 meters of the speaking prim (rather than the root). This is contrary to how [[listen]]s work, where a message can only be heard by any prim in the object if and only if the root prim is capable of hearing it.
*A prim can '''not''' hear itself, to prevent problems with recursion.
|examples=<lsl>default
{
state_entry()
{
llWhisper(0,"This is an incredibly useless program." );
}
}</lsl>
For communicating with the user or owner it is much better to use [[llDialog]], [[llOwnerSay]] or [[llInstantMessage]] as they won't spam other users.
|helpers
|also_events={{LSL DefineRow||[[listen]]|}}
|also_functions=
{{LSL DefineRow||[[llListen]]|}}
{{LSL DefineRow||[[llOwnerSay]]|}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat region wide}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llInstantMessage]]|}}
|also
|notes
|cat1=Communications
|cat2=Chat
|cat3
|cat4
}}

LlShout

2011-04-23T00:07:47Z

Stickman Ingmann: Testing shows the limit is 1023 bytes.

{{LSL_Function/chat|channel|msg}}{{LSL_Function
|func_id=24
|func_sleep=0.0
|func_energy=10.0
|func=llShout
|sort=Shout
|p1_type=integer|p1_name=channel
|p2_type=string|p2_name=msg
|func_desc=Shouts the text supplied in string '''msg''' on channel supplied in integer '''channel'''.
|spec
|constants
|caveats=*Text can only be a maximum of 1023 bytes.
*Shouts can only be heard within 100 meters of the speaking prim (rather than the root). This is contrary to how [[listen]]s work, where a message can only be heard by any prim in the object if and only if the root prim is capable of hearing it.
*A prim can '''not''' hear itself, to prevent problems with recursion.
|examples=<lsl>default
{
state_entry()
{
llShout(0,"This is an incredibly useless program!" );
}
}</lsl>
For communicating with the user or owner it is much better to use [[llDialog]], [[llOwnerSay]] or [[llInstantMessage]] as they won't spam other users.
|helpers
|also_events={{LSL DefineRow||[[listen]]|}}
|also_functions=
{{LSL DefineRow||[[llListen]]|}}
{{LSL DefineRow||[[llOwnerSay]]|}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat region wide}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llInstantMessage]]|}}
|also_tests
|also_articles
|notes
|cat1=Communications
|cat2=Chat
|cat3
|cat4
}}

LlInstantMessage

2011-04-23T00:01:57Z

Stickman Ingmann: [17:01] Andrew Linden: llInstantMessage was built to fit within one UDP packet (1.5kB)

{{Issues/SVC-92}}{{LSL_Function/avatar|user}}{{LSL_Function
|func_id=118|func_sleep=2.0|func_energy=10.0
|func=llInstantMessage
|p1_type=key|p1_name=user|p1_desc
|p2_type=string|p2_name=message|p2_desc
|func_desc=Sends an Instant Message specified in the string '''message''' to the user specified by '''key'''.
|return_text
|spec
|caveats=**For applications where this is problematic, it's possible to place the call to llInstantMessage in a child script and pass the information to that script via [[llMessageLinked]].
*'''message''' will be truncated if it exceeds 1199 bytes.
*'''message''' will appear in the chat window and will not logged by the InstantMessage logging facility. (If a the specified user is not signed it, the messages will be delivered to their email just like a regular instant message, if the user has enabled email for their account.)
|examples=Tell the owner somebody touched the object:
<lsl>// This particular example is for demonstration only.
// Use llOwnerSay() for the same functionality, in case the owner is known to be in the same Region.

key owner;

default
{
on_rez(integer start_param)
{
owner=llGetOwner(); // get the key of the objects owner.
}
touch_start(integer total_num)
{
llInstantMessage(owner,llKey2Name(owner)+", " + (string)total_num +" Avatar(s) touched me!");
}
}</lsl>
Send a confirmation to the Avatar that touches an object without spamming other Avatars:
<lsl>default
{
touch_start(integer total_num)
{
llInstantMessage(llDetectedKey(0),"You have been registered!");
}
}</lsl>
|helpers
|also_functions=
{{LSL DefineRow||[[llOwnerSay]]|}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat region wide}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
|also_tests
|also_articles
|also_events
|notes=Instant Messaging has the benefit of allowing communication from an object to an avatar anywhere in the Grid. The downside is that an object cannot receive an Instant Message, therefore an avatar cannot send an Instant Message to an object. It's a one-way communication avenue. Also, the two-second script delay can be considered a downside in some applications.
|cat1=Communications
|cat2=Instant Message
|cat3
|cat4
}}

LlSay

2011-04-22T23:56:53Z

Stickman Ingmann: 1023 is the maximum determined by testing.

{{LSL_Function/chat|channel|msg}}{{LSL_Function
|func_id=23
|func_sleep=0.0
|func_energy=10.0
|func=llSay
|sort=Say
|p1_type=integer|p1_name=channel
|p2_type=string|p2_name=msg
|func_desc=Says the text supplied in string '''msg''' on channel supplied in integer '''channel'''.
|return_text
|spec
|constants
|caveats=
*Text spoken can only be heard within 20 meters of the speaking prim (rather than the root). This is contrary to how the event [[listen]] works, where a message can only be heard by any prim in the object if and only if the root prim is capable of hearing it.
*Text can only be a maximum of 1023 bytes.
*A prim cannot hear itself, to prevent problems with recursion.
|examples=<lsl>default
{
state_entry()
{
llSay(0,"Hello, Avatar!");
}
}</lsl>
To avoid making your object spam its neighborhood, use [[llInstantMessage]] or [[llOwnerSay]].
|helpers
|also_events=
{{LSL DefineRow||[[listen]]                |Receives chat}}
|also_functions=
{{LSL DefineRow||[[llListen]]|Ask for listen events}}
{{LSL DefineRow||[[llInstantMessage]]|Sends chat to the owner only (or to some other user only) to avoid spamming the {{#var:PUBLIC_CHANNEL}}}}
{{LSL DefineRow||[[llOwnerSay]]|Sends chat to the owner only to avoid spamming the PUBLIC_CHANNEL}}
{{LSL DefineRow||[[llRegionSay]]|Sends chat region wide}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
|also_tests
|also_articles={{LSL DefineRow||[[Hello Avatar]]}}
|notes=
* Channel {{HoverText|0|Zero}} is the {{#var:PUBLIC_CHANNEL}}. Everyone can hear chat transmitted on this channel. All other channels are private channels (not sent to users, with the exception of {{#var:DEBUG_CHANNEL}}).
* Consider using llInstantMessage, llOwnerSay, or the {{#var:DEBUG_CHANNEL}} for debugging purposes. If {{#var:DEBUG_CHANNEL}} is used as '''channel''', the script will say '''msg''' to the Script Warning/Error window.
* If one object 'says' something to another object (''e.g''., a button that, when touched, turns on a lamp), it is a good idea to use a very negative channel, ''e.g.'',
<lsl>
llSay(-5243212,"turn on");
</lsl>
Negative channels are popular for script communications because the client is unable to chat directly on those channels ("/-xxxx message" won't chat "message" on channel "-xxxx", it will chat "/-xxxx message" on channel zero). The only way to do so prior to [[llTextBox]] was to use [[llDialog]] which was limited to 24 bytes.
|cat1
|cat2
|cat3
|cat4
}}

LlOwnerSay

2011-04-22T23:56:15Z

Stickman Ingmann: 1023 is the maximum determined by testing.

{{LSL_Function/limits}}{{LSL_Function
|func_id=292|func_sleep=0.0|func_energy=10.0
|func=llOwnerSay|p1_type=string|p1_name=msg
|func_desc=Says '''msg''' to the owner only.
|return_text
|spec
|caveats=
* If '''msg''' is longer than 1023 bytes, it will be truncated to 1023 bytes.
* Silently fails ~45 seconds after the owner leaves the region the object is in.
* Silently fails when the object to which the script is attached is [[deed]]ed to a group.
|constants
|examples=<lsl>default
{
touch_start(integer total_number)
{
llOwnerSay("Ouch!" );
}
}</lsl>
|helpers=
<lsl> //-- llOwnerSay extension for preventing silent failures
//-- paste this code at the top of the script and replace
//-- any calls to llOwnerSay below it with uOwnerSayPlus
uOwnerSayPlus( string vStrMsg ){
key owner = llGetOwner();
if (llKey2Name( owner )){
llOwnerSay( vStrMsg ); //-- single owner that the region still has a handle for
}else if (llList2Key( llGetObjectDetails( llGetKey(), [OBJECT_GROUP] ), 0 ) == owner){
llWhisper( 0, "/me : " +vStrMsg ); //-- group owned, must send the message publicly
}else{
llInstantMessage( owner, vStrMsg ); //-- single owner, not present, send them an IM
}
}</lsl>
|also_functions=
{{LSL DefineRow||[[llRegionSay]]|Sends chat region wide}}
{{LSL DefineRow||[[llWhisper]]|Sends chat limited to 10 meters}}
{{LSL DefineRow||[[llSay]]|Sends chat limited to 20 meters}}
{{LSL DefineRow||[[llShout]]|Sends chat limited to 100 meters}}
{{LSL DefineRow||[[llInstantMessage]]|}}
|also_events
|also_tests=
{{LSL DefineRow|[[llOwnerSay Test]]|}}
|also_articles
|notes
|permission
|negative_index
|cat1=Communications
|cat2
|cat3
|cat4
}}

User:Ama Omega/archive/office hour topics

2011-04-11T01:11:03Z

Stickman Ingmann: /* Suggested Topics */

Please add any topics you want to discuss at the next general scripting office hours below.

===Standing Topics===
* Updates on any scripting projects

===Suggested Topics===
*Should https://jira.secondlife.com/browse/SVC-4011 be closed as fixed? [[User:Stickman Ingmann|Stickman]] 18:11, 10 April 2011 (PDT)

===Previously Discussed Topics===
====''Discussed at [[User:Kelly_Linden/Office Hours/2010-11-08 | 2010-11-08 DISCUSSION]]''====
* [[Talk:LSL Useful Function WishList#backwards-compatible ways to save typing or be more like C or Javascript]] (please see for discussion of merits):
**(1) compound declarations, "integer i, j;"
**(2) declaration initialization, "integer i=1;"
**(3) Brackets for list index access, "l[5]=5;"
**(4) a pragma which offers synonyms for functions without the "ll" and/or their C or Javascript short common names, if any;
**(5) double precision floating point;
**(6) long integers.
** Mephistopheles Thalheimer suggests also:
**(7) function overloads; and
**(8) classes.

* [[Talk:Rotation#Useful snippets]] quaternion library improvements, e.g., SLERP, [http://www.isner.com/tutorials/quatSpells/quaternion_spells_12.htm], and [http://lslwiki.net/lslwiki/wakka.php?wakka=LibraryRotationFunctions]

* Clarification of how scripting JIRA issues are resolved. Specifically minor or trivial, how/when do these get picked up to be worked on, could one or more Lindens dedicate some time each week to picking up a few smaller issues and working on them, using the JIRA list sorted by age (oldest first) to clear them by developing them, or trying to design a solution if required beforehand ([[User:Haravikk Mistral|Haravikk Mistral]]).

====''Discussed at [[User:Kelly_Linden/Office Hours/2010-10-25 | 2010-10-25 DISCUSSION / TRIAGE]]''====
* LSL library calls for mesh

LSL 101/LSL in Focus: Integers

2011-04-07T06:31:44Z

Stickman Ingmann: Casting a float to an integer floors it.

{{NavNextPrev|prefix=LSL in Focus:_|prev=Types|topic=Language Topics in Focus|next=Floats}}

__TOC__

Integers in LSL roughly correspond to integers in mathematics. They can be written in either the familiar decimal (e.g. 20, 0, -1) or [[#Hexadecimal Notation|hexadecimal]] (e.g. 0x14, 0x0, 0xFFFFFFFF).

Integers in LSL are used in four distinct ways:
* Signed integers
* Truth values (Booleans)
* Enumerations
* Bit vectors

There are a three operators, namely = (assignment), == (test for equality) and != (test for inequality) that are common to all uses of integers. Other than those, the four different uses of integers generally involve separate sets of operators.

== Signed Integers ==
This is the use of integers that corresponds to the normal use in mathematics. The only substantive difference is that in mathematics, there are infinitely many integers, while in LSL integers are limited to the range −2,147,483,648 to 2,147,483,647. Also, in LSL, no commas or other separators are allowed when writing integers, so these numbers would be written −2147483648 and 2147483647.

=== Arithmetic Operators ===
LSL has the normal arithmetic operators +, -, * and / (for division). The first three have the same meaning as what you used in grade school '''as long as the result is in the range −2147483648 to 2147483647'''. If the result is outside that range, different rules apply. The typical scripter doesn't need to use numbers that are so big (or small), so there's nor reason to feel you need to learn the details of what happens when the limits are exceeded. But there are instances where it is actually useful to allow numbers to exceed the limits. For the details of what happens in that case, see the Integer Overflow section, below.

Division of integers in LSL is a variation on what you learned in elementary school. If the division results in a whole number, say 10/2, the answer is 5. But 15/2 is neither 7.5 nor 7 with a remainder of 1. Instead, it is exactly 7. Any remainder is simply thrown away. Alternatively, you can think of it as being rounded toward zero. It's more accurate to say "rounded toward zero" than "rounded down", because -15/2 is -7, not -8. If you're scripting something where you really want 15 divided by 2 to be 7.5, don't despair. You'll just need to use the "float" type instead of integers.

Closely related to integer division is the remainder operator, written as %. It gives you what would remain if you were to ask for integer division on the same numbers. Here are some examples:
<lsl> integer i;
i = 15 % 2; // i is assigned the value 1
i = 15 % 4; // i is assigned the value 3
i = -15 % 4; // i is assigned the value -3</lsl>

If an attempt is made to divide by 0 (using either / or %), a run-time error occurs and script execution halts.

Each of the arithmetic operators also has a corresponding assignment type operation. For example
<lsl> integer x;
integer y;
x += y; // Synonymous with x = x + y;
x -= y; // Synonymous with x = x - y;
x *= y; // Synonymous with x = x * y;
x /= y; // Synonymous with x = x / y;</lsl>

In addition, since incrementing or decrementing by 1 is quite common, is special unary operator for that. The operator is written ++ and is pronounced plus-plus. To increment the variable i by 1, we can write either ++i or i++. So for example

<lsl> integer i = 0;
i++; // i now has the value of 1
++i; // i now has the value of 2</lsl>

But the two operators are not identical, because i++ and ++i are expressions that can occur as part of a larger expression. When used as part of a larger expression, i++ contributes its value to the expression ''before'' it is incremented. For example, the fragment

<lsl> integer i = 0;
if (i++ == 0)
llSay( 0, "The value of i was 0 when the comparison was done" )
else
llSay( 0, "The value of i was 1 when the comparison was done" )</lsl>

would chat "The value of i was 0 when the comparison was done" even though i ends up with the value of 1. On the other hand, if we switch i++ to ++i, i.e.

<lsl> integer i = 0;
if (++i == 0)
llSay( 0, "The value of i was 0 when the comparison was done" )
else
llSay( 0, "The value of i was 1 when the comparison was done" )</lsl>

the chat output would be "The value of i was 1 when the comparison was done".

The operator minus-minus (written --) works similarly.

=== Comparison Operators ===
In addition to the arithmetic operators, there are also the normal integer comparison operators < (less than) and > (greater than). For "less than or equal", or "greater than or equal", there are two-character operators <= and >=. There can't be any space between the two characters of a two-character operator.

The result of a comparison operator is either 0 (representing '''FALSE''') or 1 (representing '''TRUE'''). See [[#Truth Values (Booleans)|Truth Values (Booleans)]].

=== Integer Overflow ===
* During script execution, integers wraps from 2147483647 to -2147483648 in the normal way
* The compiler treats integers outside the range -2147483648 to 2147483647 somewhat strangely. No compile time warning or error is generated. (If the following explanation, doesn't make sense to you don't worry -- just know to avoid using numbers outside the valid range in your script.)
** For an integer outside the range -2147483648 to 2147483647, the absolute value of the number is reduced to fall in the range 0 to 4294967295 (0xFFFFFFFF).
** This number is then parsed as an unsigned 32 bit integer and cast to the corresponding signed integer.
** If the value in the script had a negative sign, the sign of the internal representation is switched.
** The net effect is that very large positive numbers get mapped to -1 and very large negative numbers get mapped to 1.

== Truth Values (Booleans) ==
There is not a special type for TRUE and FALSE in LSL. Instead, TRUE is defined to be the integer 1 and FALSE is defined to be the integer 0.

This has an interesting consequence in a conditional statement. Consider the following example

<lsl> integer i = 3; // 3 is neither TRUE nor FALSE
if (i)
llSay( 0, "i is treated as being true." );
else
llSay( 0, "i is treated as being false." );
if (i == TRUE)
llSay( 0, "i is equal to TRUE." );
else
llSay( 0, "i is not equal to TRUE." );</lsl>

When run, the output will be

i is treated as being true.
i is not equal to TRUE.

This is because the condition in the '''if''' statement can be any integer. Any non-zero value will cause the ''true'' block or statement to be executed, while a zero value will cause the ''false'' block or statement to be executed.

The same zero/non-zero distinction is made wherever a truth value is expected. In what follows, we'll use the word '''true''' and '''false''' to mean non-zero versus zero, while '''TRUE''' and '''FALSE''' will mean one and zero.

=== Truth Value Operators ===

There are three truth value operators in LSL:
* ! (representing '''not''')
* && (representing '''and''')
* || (representing '''or''')

The ! operator takes a single operand and evaluates to '''TRUE''' if the operand is false, and '''FALSE''' otherwise. For example

<lsl> integer i;
i = !(3 == 7); // 3 == 7 is FALSE, so i gets the value TRUE</lsl>

The && operator takes two operands and evaluates to '''TRUE''' if both its operands are true, and '''FALSE''' otherwise.

<lsl> i = (3 < 7) && (3 > 7); // 3 < 7 is TRUE, but (3 > 7) is FALSE, so i gets the value FALSE</lsl>

The || operator takes two operands and evaluates to '''TRUE''' if either one of its operands are true, and '''FALSE''' otherwise.

<lsl> i = (3 < 7) || (3 > 7); // one of the operands (3 < 7) is TRUE, so i gets the value TRUE</lsl>

Like the binary arithmetic operators, && and || have a corresponding assignment type operator.

<lsl> integer x;
integer y;
x &&= y; // Synonymous with x = x && y;
x ||= y; // Synonymous with x = x || y;</lsl>

=== Statements Requiring Truth Values ===
There are four statement types that require a truth value condition:
* if
* for
* while
* do-while

== Enumerations ==
Many built-in functions have a parameter or return value that takes one of a fixed number of alternatives. For example, [[llAttachToAvatar]] has a single parameter which specifies the attachment point. The attachment point is specified to be an integer, but the specific integer corresponding to each attachment point is arbitrary. Since the numbers themselves have no significance, LSL defines names such as [[ATTACH_HEAD]], [[ATTACH_LFOOT]] and [[ATTACH_BELLY]], which are simply meaningful names for the arbitrary integers. Integers used in this way are called '''enumerations'''.

Generally, no operators besides the ubiquitous =, == and != are used with enumerations because there is no expected relationship between the arbitrarily selected integer values.

== Bit Vectors ==

=== Bit Vector Operators ===
Analogous to the truth value operators, LSL defines three operators specifically for bit vectors:

* ~ (bitwise not)
* & (bitwise and)
* | (bitwise or)

In contract to the truth value operators, these operate independently on each bit position.

== Other Uses of Integers ==

Although the four uses described above cover all the ways that integers are used with LSL built-in functions, they are not really exhaustive of the ways integers ''can'' be used. There are algorithms in mathematics and computer science that mix arithmetic and bit vector operations, along with bit shift operators. LSL supports this kind of computation with the bit shift operators inherited from C:

* << shift bits left
* >> shift bits right

and their assignment analogs

* >>=
* <<=

Discussion of these algorithms is beyond the scope of this article, but see [http://graphics.stanford.edu/~seander/bithacks.html Bit Twiddling Hacks] for some examples.

== Type conversions ==
=== Other types to integers ===
Casting a float to an integer has the same end effect as using the [[llFloor]] function.
=== Integers to other types ===

== Differences between Integers in LSL and in C ==
Much of LSL is patterned after the C programming language, and integers are no exception. Programmers who already know C can immediately apply most of their understanding of integers to LSL.

Differences to note are
* The type must be spelled ''integer'' instead of ''int''.
* There are no size modifiers (short, long, ...). All integers are 32 bits.
* There is no unsigned modifier. All integers are signed.
* Comparison operators evaluate to an integer (1 or 0), as they did in C prior to C99.
* The && and || operators are strict, i.e. both operands are always evaluated, even if the result can be determined after evaluating the left operand.

== Hexadecimal Notation ==
There's actually not much use for hexadecimal notation in LSL. If you do feel a need to use it, you probably already know how it works. If not, you can consult {{Wikipedia|Hexadecimal notation|Wikipedia}}.

Content Creation, Mesh Import, Scripting User Group

2011-04-04T18:07:29Z

Stickman Ingmann:

{{User Group Page
|purpose=
Topics are focused on anything related to the mesh import project. Feature requests, bug reports, design feedback, questions, comments, or example content are welcome.

Priority will be given to topics that are posted in advance and are relevant to the goals of the office hour. Feel free to include relevant links to JIRA or wiki pages.

|date-time=
Mondays at 11 AM in Pacific time (SL standard time)

Next meeting scheduled for: '''April 4, 2011'''

|location=
[secondlife://Aditi/secondlife/MeshHQ%201/251/250/24 Mesh HQ on Aditi]
|team=
Charlar Linden, Nyx Linden, and Runitai Linden. Please contact one of us if you are unsure if your topic is relevant or appropriate.
|agenda=
<br><br>
Please add topics below '''prior to 10:50 AM'''. Also, please put your SL name down so we can follow up if we have questions. Thanks!
# Can you update us on recent progress and what your curent priorities are? Anything in particular we can test for you?
# Are we there yet?
# Seems like almost everything is broken. What's going on? [Drongle McMahon]
# Have you seen the error of your ways and decided to allow UUID swapping for meshes yet? -Stickman
|archive=
[https://wiki.secondlife.com/wiki/Mesh_User_Group/Archive Agenda and notes archive]. Older archives are [https://wiki.secondlife.com/wiki/User:Nyx_Linden/Mesh_Office_Hours_Agenda_Archive here].
}}
[[Category:Mesh]]

User:Nyx Linden/Mesh Office Hours Agenda

2011-02-14T18:58:24Z

Stickman Ingmann: /* February 14, 2011 */

==Mesh Team's Office Hours Agenda==

Office hours are on Mondays at 11 AM in Pacific time (SL standard time) located on the beta grid (Aditi) in Mesh HQ 1 at: [secondlife://Aditi/secondlife/MeshHQ%201/251/250/24 Mesh HQ on Aditi]

Topics are focused on anything related to the mesh import project. Feature requests, bug reports, design feedback, questions, comments, or example content are welcome.

Please add topics for discussion / agenda items to the end of the list below prior to 10:50 AM. Priority will be given to topics that are posted in advance and are relevant to the goals of the office hour. Feel free to include relevant links to JIRA or wiki pages. Contact Nyx Linden, Runitai Linden, or Charlar Linden if you are unsure if your topic is relevant or appropriate.

Archived agendas can be found at the [[User:Nyx_Linden/Mesh_Office_Hours_Agenda_Archive|agenda archive]].

Next meeting scheduled for: February 14, 2011.

===Agenda===

== February 14, 2011 ==
# Plan on moving to the current Mesh View build; Plans for older mesh content on Aditi in the coming month - charlar
# What is the license of the Collada file made from the avatar OBJ file?
# Any estimate when we will see API Documentation for uploading of content ? (Sculpties or meshes or even regular prims)
# Upload pricing finalized yet? Subscription based?
# Release date? Or at least an indication? Over a month? Over three months?
# Using a project timeline rather than a time-based timeline, where does the custom skeleton project sit? Immediately after meshes? With two or three other projects in front of it? Is it a high priority?
# Your item here

Talk:Creating Tattoos

2010-12-24T01:53:21Z

Stickman Ingmann: Does baking resize tattoos?

Is there a maximum texture size for tattoos? They can be uploaded as any resolution, but are they resized to something else when they're baked into the avatar? --[[User:Stickman Ingmann|Stickman]] 01:53, 24 December 2010 (UTC)

User:Nyx Linden/Office Hours Agenda

2010-11-03T16:47:28Z

Stickman Ingmann: Clarified linking rules, neck attachment slot. UUID swap/bone mesh question /* November 3, 2010 */

==Nyx Linden's Office Hours Agenda==

Office hours are on Wednesdays at Noon in Pacific time (SL standard time) located in Borrowdale at: http://slurl.com/secondlife/Borrowdale/74/217/32

Topics are focused on avatars, content creation efficiency, content creation tools and methods, rendering issues, and many related random topics.

Please add topics for discussion / agenda items to the end of the list below prior to 11:50 AM. Priority will be given to topics that are posted in advance and are relevant to the goals of the office hour. Feel free to include relevant links to JIRA or wiki pages. Contact Nyx Linden if you are unsure if your topic is relevant or appropriate.

Archived agendas can be found at the [[User:Nyx_Linden/Office_Hours_Agenda_Archive|agenda archive]].

Next meeting scheduled for: November 3, 2010.

===Agenda===

== November 3, 2010 ==
# Will the new prim size also mean a new rule set for linking prims together, in other words, will the 30 meter limit change?
#* Andrew Linden is working on new linkability rules that simplify the equation to 54m from the center of objects being linked, regardless of scale. 54m is the current maximum linking distance. --[[User:Stickman Ingmann|Stickman]] 16:47, 3 November 2010 (UTC)
# Is this a bug or expected behavior? https://jira.secondlife.com/browse/CTS-309 Should mirroring be allowed for meshes?
# (General rendering, not Mesh) Shiny and especially pre-defined bumpmaps are broken (for me) with experimental "Lighting and Shadows" enabled (although "brightness" / "darkness" bitmaps still work). Is this intended? (Breaks some of my content, but if it's a necessary step for future Materials or something, I won't jira it.) [[User:Qie Niangao|Qie]] 13:27, 3 November 2010 (UTC)
# (Another general rendering) Experimental shadows from sun and projected lights passing through an 8-bit alpha-textured surface appear (to me) to be 1-bit alpha-masked, regardless of rendering settings. Is that intentional (perhaps for computability)? [[User:Qie Niangao|Qie]] 13:37, 3 November 2010 (UTC)
# What happened to the neck attachment slot! :( --[[User:Stickman Ingmann|Stickman]] 16:47, 3 November 2010 (UTC)
# What's the current status on UUID swapping for meshes, and custom bones at release? --[[User:Stickman Ingmann|Stickman]] 16:47, 3 November 2010 (UTC)
# Your Question Here!

LlGetOwnerKey

2010-09-29T04:05:38Z

Stickman Ingmann: Documented attach speak on detach, owner not found bug.

{{LSL_Function/uuid|id|sim=*}}{{LSL_Function
|func_id=182|func_sleep=0.0|func_energy=10.0
|func=llGetOwnerKey|sort=GetOwnerKey
|return_type=key|p1_type=key|p1_name=id
|func_footnote
|func_desc
|return_text=that is the owner of object '''id'''
|spec
|caveats=
* Returns '''id''' if '''id''' is not found in the region or is not an object.
** If an attached object speaks on detach, the id of the object, not the owner, will be returned. [[https://jira.secondlife.com/browse/SVC-5095 SVC-5095]]
* '''id''' can be any prim in the object.
|constants
|examples=<lsl>key owner;

default
{
state_entry()
{
owner = llGetOwner();
llListen(1, "", "", "");
}
on_rez(integer a)
{
owner = llGetOwner();
}
listen(integer chan, string name, key id, string msg)
{
if(llGetOwnerKey(id) == owner)
{//Only triggers if what spoke is the owner or if they share the same owner
llOwnerSay(name + " has the same owner as me ^_^");
}
}
}</lsl>
|helpers
|also_functions={{LSL DefineRow||[[llKey2Name]]|}}
{{LSL DefineRow||[[llRequestAgentData]]|}}
{{LSL DefineRow||[[llGetObjectDetails]]|}}
{{LSL DefineRow||[[llGetOwner]]|}}
|also_tests
|also_events
|also_articles
|notes=When used on an avatars key, the key of that avatar is returned again. So avatars are owned by themself.
|cat1=Owner
|cat2=Key
|cat3
|cat4
}}

Linden Lab Official talk:Private Region Transfer FAQ

2010-08-05T22:11:08Z

Stickman Ingmann: KB article needs an update. Here's the info it needs.

_____________________________

This section doesn't appear to make sense:

Is there a transfer fee?

Yes. The USD$100 (or L$28,000 for L$ transfers) Region Transfer fee, which is always debited from the '''seller''''s account..... This means '''buyers''' need valid payment information on file with Linden Lab

[[User:Chaz Longstaff|Chaz Longstaff]] 03:12, 30 December 2009 (UTC)

_____________________________

The initial instructions have different wording now.

3. Select Ticket Type: '''Land & Region''' with these details:
* Land & Region: '''Initiate Region Sale''' or '''Initiate Region Purchase'''

It should be mentioned that a value of "0" can be entered if the island is not being sold but transferred or traded, and that selecting USD or L$ will determine how the transfer fee is payed. Mentioning that selling it for USD$100 or L$28000 will make the seller "pay" the transfer fee would be useful -- some people don't notice these things.

Also, I can't seem to edit the ticket after submission. Would be nice to know if support prefers the buyer or seller input the other's ticket number, as you can't have both.

[[User:Stickman Ingmann|Stickman]] 22:11, 5 August 2010 (UTC)

User:Oz Linden/Office Hours Topics

2010-07-28T20:01:18Z

Stickman Ingmann:

I am currently holding office hours twice a week - see [[User:Oz_Linden/Office_Hours]]

If you have particular topics you would like to discuss, feel free to add them below. If there is sufficient interest, we can also set up special sessions.

=== Future Topics ===
# Publish statistics on user hardware: http://jira.secondlife.com/browse/MISC-4405 -[[User:Stickman Ingmann|Stickman]] 20:01, 28 July 2010 (UTC)

User:Nyx Linden/Office Hours Agenda

2010-07-28T19:26:07Z

Stickman Ingmann:

==Nyx Linden's Office Hours Agenda==

Office hours are on Wednesdays at Noon in Pacific time (SL standard time) located in Borrowdale at: http://slurl.com/secondlife/Borrowdale/74/217/32

Topics are focused on avatars, content creation efficiency, content creation tools and methods, rendering issues, and many related random topics.

Please add topics for discussion / agenda items to the end of the list below prior to 11:50 AM. Priority will be given to topics that are posted in advance and are relevant to the goals of the office hour. Feel free to include relevant links to JIRA or wiki pages. Contact Nyx Linden if you are unsure if your topic is relevant or appropriate.

Archived agendas can be found at the [[User:Nyx_Linden/Office_Hours_Agenda_Archive|agenda archive]].

Next meeting scheduled for: July 28, 2010.

===Agenda===

== July 28, 2010 ==
# Owner-After-Next Permissions for 1st Tier Content Creators - https://jira.secondlife.com/browse/SVC-2622
# Shared Media does not allow for interaction or audio on HUDs in v2.1 (https://jira.secondlife.com/browse/VWR-20380).
# What happened to Samuel?
# Perhaps have a rendering Linden share this OH (and take BigPappy's place)?
# Mesh?
# UI! (had to be done)
# Custom skeletons -[[User:Stickman Ingmann|Stickman]] 19:06, 28 July 2010 (UTC)
# Any update on the incorrect height info in the appearance editor? ( https://jira.secondlife.com/browse/VWR-19767 )
# Scripted Controls of web Prims.
# specific timeframe for introduction of mesh imports, what restrictions will be imposed on them (vertex/poly wise) and what kind of rigging will be implimented.
# Windlight estate controls
# Your topic here.

User:Nyx Linden/Office Hours Agenda

2010-07-28T19:06:43Z

Stickman Ingmann: /* July 28, 2010 */

User:Nyx Linden/Office Hours Agenda

2010-07-14T18:41:45Z

Stickman Ingmann: /* July 14, 2010 */ multi-attachables

AW Groupies

2010-06-29T05:49:35Z

Stickman Ingmann: fixed mailing list info -- IRC info is out of date?

=Purpose=
Serious technical discussion about Linden Lab's [[Architecture Working Group|Architecture Working Group (AWG)]]. "AW Groupies" is an unofficial, Resident-operated group, though most (all?) members also participate in the AWG.

Invite only (apply in-world to [[User:Zha Ewry|Zha Ewry]]), but the criterion is simple. Show up and contribute to the AWG, at [[User:Zero Linden|Zero Linden]]'s office hours, or on the Wiki, or on SL-Dev or in the [irc://irc.freenode.net/#pyogp irc channel] for the [[Pyogp/Client_Lib|Python test client]].

=Activities=
The [[AW_Groupies#Architecture_Working_Group_meetings|main AWG meeting]] is held annually or semi-annually.
We now [[AW_Groupies#In-World_Meetings|meet up to 8 times a week in-world]], counting AW Groupies meeting, Zero's office hours, Which's office hours, Enus's office hours, Whump's office hours and the [[Pyogp#In_World_Meetings|pygop daily meetings]].

Our main focus these days is on the [[Open Grid Protocol]], the [[Open_Grid_Public_Beta]] and the [[Pyogp|pyogp Python test harness]] for protocol testing.

Also members are quite active on the wiki and in the SLDEV mailing list.

A public SVN repository is open to all AW Groupies members here:
* http://openmv.org/cgi-bin/viewvc.cgi/archwg/

Contact anyone with root on openmv.org for an account if you are in the AW Groupies group in-world.

==Architecture Working Group meetings==
* [[AWG_Meeting_1|AWG I annual meeting transcript, participants' responses, etc]]
* [[AWG_Meeting_2|AWG II annual meeting transcript, video, participants' responses, etc]]

==In-World Meetings==
===AW Groupies meeting===
Weekly meeting times are:

* '''Tuesdays''' ------ 9:30 AM SLT (weekly AWG meeting)

1st - 3rd Tuesdays of the month at [http://slurl.com/secondlife/ThorneBridgeTown/156/129/25 Zha's IBM Island at ThorneBridgeTown]

4th Tuesday of the month at [http://www.osgrid.org/elgg/index.php OSGrid] which you can access by using the login URI http://osgrid.org:8002. See the [http://www.osgrid.org/elgg/index.php Main OSGrid page] for more info or read the [http://www.osgrid.org/docs/instructions.htm instructions to log in] for help. Look for the region "Dahlia AWG" for the meeting!

* ------------------ Noon SLT [https://wiki.secondlife.com/wiki/AW_Groupies#OpenSim__meeting| Open Sim Meeting]

Meetings are scheduled via the "[http://www.google.com/calendar/embed?src=pdd5mpktklo89bgmfgi076mcc4%40group.calendar.google.com SL AW Groupies" google calendar]" (though the above schedule is generally more accurate).

* [http://www.google.com/calendar/feeds/pdd5mpktklo89bgmfgi076mcc4%40group.calendar.google.com/public/basic XML]
* [http://www.google.com/calendar/ical/pdd5mpktklo89bgmfgi076mcc4%40group.calendar.google.com/public/basic.ics ICal]
* Calendar ID: pdd5mpktklo89bgmfgi076mcc4@group.calendar.google.com
* [http://www.google.com/calendar/render?cid=pdd5mpktklo89bgmfgi076mcc4%40group.calendar.google.com Add to your Google Calendar]

====Meeting Agendas====

Each meeting should have an agenda --- which will be distributed via
* google calendar entry
* in-world notice to the SL "AW Groupies" group
* the [[AW Groupies In-World Meeting Agenda]] wiki page

===OpenSim meeting===
* Tuesdays/Saturdays noon SLT, at Wright Plaza sim in OSGrid. [http://osgrid.org/index.php?page=home&btn=1 Registration Page]

Set [[Client_parameters|client command line options]] to:
:-loginuri http://osgrid.org:8002
:-loginpage http://osgrid.org/loginscreen.php
:-helperuri http://osgrid.org/

===Chat Logs===

Chat logs of the in-world meetings are published and accessible via the links below:

====2007 meetings====
:* September: [[AW_Groupies/Chat_Logs/2007-09-28 | 28]]
:* October: [[AW Groupies/Chat Logs/2007-10-01 | 1]] [[AW Groupies/Chat Logs/2007-10-05 | 5]] [[User:Zero_Linden/Office_Hours/2007_Oct_09|9 --Zero's office]] [[AW Groupies/Chat Logs/2007-10-16| 16]]
:* November: [[AW Groupies/Chat Logs/2007-11-06 | 6]] [[AW Groupies/Chat Logs/2007-11-13 | 13]] [[AW Groupies/Chat Logs/2007-11-20| 20]]
====2008 meetings====
:* January: [[AW_Groupies/Chat_Logs/AWGroupies-2008-01-08|08]]
:*February: [[AW_Groupies/Chat_Logs/AWGroupies-2008-02-19|19]]
:*April: [[AW_Groupies/Chat_Logs/AWGroupies-2008-04-08|08]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-04-22|22]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-04-29|29]]
:*May: [[AW_Groupies/Chat_Logs/AWGroupies-2008-05-20|20]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-05-27|27]]
:*June: [[AW_Groupies/Chat_Logs/AWGroupies-2008-06-03|03]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-06-10|10]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-06-17|17]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-06-24|24]]
:*July: [[AW_Groupies/Chat_Logs/AWGroupies-2008-07-01|01]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-07-08| 08]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-07-15|15]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-07-22|22]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-07-29|29]]
:*August: [[AW_Groupies/Chat_Logs/AWGroupies-2008-08-05|05]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-08-12|12]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-08-19|19]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-08-26|26]]
:* September [[AW_Groupies/Chat_Logs/AWGroupies-2008-09-02|2]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-09-09|9]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-09-16|16]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-09-23|23]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-09-30|30]]
:* October [[AW_Groupies/Chat_Logs/AWGroupies-2008-10-07|7]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-10-14|14]] [[User:Zero_Linden/Office_Hours/2008_October_14|14 --Zero's O.H.]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-10-28|28]]
:* November [[AW_Groupies/Chat_Logs/AWGroupies-2008-11-11|11]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-11-18|18]]
:* December [[AW_Groupies/Chat_Logs/AWGroupies-2008-12-09|9]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-12-16|16]] [[AW_Groupies/Chat_Logs/AWGroupies-2008-12-23|23]]
====2009 meetings====
:*January [[AW_Groupies/Chat_Logs/AWGroupies-2009-01-06|6]] [[AW_Groupies/Chat_Logs/AWGroupies-2009-01-13|13]] [[AW_Groupies/Chat_Logs/AWGroupies-2009-01-20|20]] [[AW_Groupies/Chat_Logs/AWGroupies-2009-01-27|27]]
:*February [[AW_Groupies/Chat_Logs/AWGroupies-2009-02-03|3]] [[AW_Groupies/Chat_Logs/AWGroupies-2009-02-10|10]] [[AW_Groupies/Chat_Logs/AWGroupies-2009-02-17|17]] [[AW_Groupies/Chat_Logs/AWGroupies-2009-02-24|24]]
:*March [[AW_Groupies/Chat_Logs/AWGroupies-2009-03-03|3]] [[AW_Groupies/Chat_Logs/AWGroupies-2009-03-10|10]]
:*April [[AW_Groupies/Chat_Logs/AWGroupies-2009-04-07|7]] [[AW_Groupies/Chat_Logs/AWGroupies-2009-04-14|14]] [[AW_Groupies/Chat_Logs/AWGroupies-2009-04-28|28]]
:*June [[AW_Groupies/Chat_Logs/AWGroupies-2009-06-02|2]] [[AW_Groupies/Chat_Logs/AWGroupies-2009-06-16|16]]
:*July [[AW_Groupies/Chat_Logs/AWGroupies-2009-07-21|21]]
:*September [[AW_Groupies/Chat_Logs/AWGroupies-2009-09-15|15]]
:*October [[AW_Groupies/Chat_Logs/AWGroupies-2009-10-20|20]]
====2010 meetings====
:*March [[AW_Groupies/Chat_Logs/AWGroupies-2010-03-02|2]] [[AW_Groupies/Chat_Logs/AWGroupies-2010-03-09|9]]
:*April [[AW_Groupies/Chat_Logs/JoeLindenTPVBrownbag-2010-04-13|13joe]] [[AW_Groupies/Chat_Logs/AWGroupies-2010-04-20|20joshua]] [[AW_Groupies/Chat_Logs/JoeLindenTPVBrownbag-2010-04-20|20joe]]
:*May [[AW_Groupies/Chat_Logs/AWGroupies-2010-05-04|04proxies]] [[AW_Groupies/Chat_Logs/AWGroupies-2010-05-19|18meadhbh]] [[AW_Groupies/Chat_Logs/AWGroupies-2010-05-25|25]]
:*June [[AW_Groupies/Chat_Logs/AWGroupies-2010-06-01|04mojito]]
*
* [[MMOX#Chat_logs|MMOX chat logs]] -- in-world transcripts with non-SL/Opensim participants
* [https://wiki.secondlife.com/wiki/Category:Grid_Interoperability_Chat_Logs All Grid Interoperability chat logs]
* [https://wiki.secondlife.com/wiki/Category:AW_Groupies_Transcripts All AW Groupies chat logs]
* [https://wiki.secondlife.com/wiki/Category:Pyogp_Transcripts All Pyogp chat logs]
* [https://wiki.secondlife.com/wiki/Category:Open_Grid_Public_Beta_Transcripts All Open Grid Public Beta Transcripts]
*
* [[User:Zero_Linden#Transcripts_of_previous_office_hours|Zero Linden's Office Hour Transcripts]]
* [[User:Which_Linden|Which Linden's Office Hour Transcripts]]
* [[User:Enus_Linden| Enus Linden Office Hour Transcripts]]
* [[User:Whump_Linden| Whump Linden Office Hour Transcripts]]
*
* [http://opensimulator.org/wiki/Special:Search?search=chat+log OpenSim chat logs]
* [[Mono/2008-04-04 | mono beta meeting discussion of het-grid]]

(if you post chat logs, you might want to use the [[User:Dr_Scofield/logtransform|sllog2wiki perl script]] to turn them into a more readable wiki table format ready to copy & paste into the chat log page)

Chat logs of AWGroupies meetings should be summarized on the wiki.

==Viewpoint Advocacy Groups==

[[Viewpoint Advocacy Groups]] - groups to focus on specific requirements.
=== AWG-specific VAGs===

* [[Core Grid Services, Protocols, and Structures VAG]]
* [[Event Scalability VAG]]
* [[Geometry and Physics VAG]]
* [[Live Performances VAG]]
* [[Quality Assurance VAG]]
* [[Scalability VAG]]
=== AWG-related VAGs===
* [[Map_API_VAG]]
* [[Multi-Process Client VAG -- draft]]

=Work-In-Progress=

Work-in-progress wiki pages are architecture pages that are (as the name implies ;-)) work in progress. Once the group has reached consensus that a particular topic is "good-to-go" we'll graduate that page to the [[Architecture Working Group|main AWG page]].

==General Concerns==
* [[Scoping]]
* [[Architecture Working Group Glossary|Glossary]]
* [[Use Cases]]
===Open Grid Protocol (OGP)===
====Linden Pages====

====User Pages====

==Communications==
* [[Initial CAPS seed]]
* [[AWG initial flows]]
* [[AWG flows login]]

* [[Mudata]]
* [[Streamlet]]
===Documenting current protocols===
* [[Pyogp|Python test harness for OGP]]
** [[User:Which_Linden/Office_Hours/2008_May_22| Which Linden office hours 22 May 2008]]
====AWG and citizen pages====
* [[Current_login_protocols]]
* [[Current_Sim_Capabilities]]
* [[Example_protocol_code]]
* [[Hegemons_Login_Analysis#Very_simple_C.23__server]]
* [[User:Gareth_Ellison/Supergrid|Litesim grid interop]]
* [[EventQueueGet_CAP| Event Queue Get CAP]]

====Linden Lab pages====
* [[Service_Disruptions|"Satellite's Eye" view of the Second Life architecture from a service disruption POV]]
* [[Message_System_and_Capabilities]]
* [[Viewer_Authentication]]
* [[Viewer_Architecture]]
* [[Protocol]]
* [[LLSD]]
* [[Certified_HTTP_Escrow]]
* [[ImprovedInstantMessage]]
* [[Client_parameters|client command line parameters and stuff]]

====libsecondlife reference pages====
* [http://www.libsecondlife.org/wiki/Login Login page]
* [http://www.libsecondlife.org/wiki/Protocol_%28network%29 Protocol page]
* [http://www.libsecondlife.org/wiki/Category:Packets packets index]
* [http://www.libsecondlife.org/wiki/Movement Movement]

====opensim reference pages====
* [http://opensimulator.org/wiki/Grid_Architecture_Diagram opensim grid architecture diagram]
* [http://opensimulator.org/images/3/3c/OGS1Login_Sequence.jpg login diagram (same general sequence as current LL login)]

=== Future Protocols===
* [[Second_Life_Login_API_Strawman]]
:deprecated in favor of:
* [[Open Grid Protocol]]
** [[SLGOGP_Teleport_Strawman]]
*[[Architecture_Working_Group#Design_Documents | Ongoing next generation protocols documentation effort by Linden Lab]]

=== Possible future directions ===
* [http://en.wikipedia.org/wiki/OpenID| OpenID A decentralized single sign-on system]
* [http://en.wikipedia.org/wiki/Yadis| Yardis A digital identity protocol]

==Asset Security and Trust==
* [https://wiki.secondlife.com/wiki/User:Dale_Innis/Asset_handling_in_OGP Asset Handling in OGP]
* [[Protecting content in an open grid]]
* [https://wiki.secondlife.com/wiki/User:Infinity_Linden/OGP_Trust_Model OGP Trust Model]

==Scaling Issues==
* [[Brainstorming#ANALYSIS:_Region_Subdivision_as_a_scaling_method| Region Subdivision]]
* [[Brainstorming#ANALYSIS:_Scalability_through_reverse_proxies:_the_paravirtual_grid| Reverse Proxies]]
* [[AWG Scalability through per-resident subdivision of the Grid| Resident Subdivision]]
===Group IM===
* [[Message_Queue_Evaluation_Notes| Which Linden's message queue evaluation notes]]

==Other==
* [[Use_Cases#Extended_Capability_Clients|Extended Capability Clients]]

=Thinking-in-Progress=

* Have a look and contribute to the [[Brainstorming|brainstorming]] page.

* It's early days on the [[Multi-Process Client VAG -- draft]], but we would highly appreciate input to help with design choices and direction.
==Misc User Pages==
* Have an AWG idea? Don't know where in the wiki it should be indexed? Make sure that folks can find it by adding it to the [https://wiki.secondlife.com/wiki/Category:AW_Groupies_User_Pages AW_Groupies_User_Pages] Add: <nowiki>'[[Category:AW Groupies User Pages]]'</nowiki> to the end of your user page.

=External Resources=

Stuff of interest to or in connection with the [[AW Groupies]] or the [[Architecture Working Group]]:

* [[Developer_communication_tools|Developer Communication Tools (Linden Lab)]]
* [[SLDev|SLDev Main Page]]
* [[Open_Grid_Public_Beta]]
* [[Pyogp]] {Linden Labs/ AWG Python-based protocols testing library)
*
* [http://openmv.org/ OpenMetaverse Home]
**[http://www.libsecondlife.org/wiki/Main_Page libsecondlife (libsl) homepage]
**[http://opensimulator.org/wiki/Main_Page opensim homepage]
**[http://openviewer.org openviewer homepage]
**[http://code.google.com/p/openmetaverse/wiki/SimianGrid SimianGrid]
*[http://www.osgrid.org OSGrid: open/non-profit OpenSim based grid]
* [http://www.realxtend.org/ realxtend homepage]
*
* [http://www-03.ibm.com/press/us/en/pressrelease/22428.wss IBM PR re: AWG]

Latha's quick list of interop relevant VW sites, 3/30/2010
* http://tools.ietf.org/wg/vwrap/
* http://opensimulator.org/wiki/Main_Page
* http://openwonderland.org/
* http://www.realxtend.org/
* http://code.google.com/p/openmetaverse/wiki/SimianGrid
* http://www.opencobalt.org/
* http://www.solipsis.org/
* http://www.web3d.org/

==Second Life Viewers==
Various viewers compatible with Second Life.

::*Note: the "Derived 3rd-party clients" page includes a few non GPL viewers plus some hybrids. I'll try to come up with a better way to index this stuff. [[User:Saijanai Kuhn|Saijanai Kuhn]]
::*Yeah, that redirect of "Alternate_viewers" to "Downloads" is nuts, and the "Downloads" page itself seems to have to have a variety of things bundled together --- it needs splitting. But don't split it by license, that's precisely what I sought to eliminate in this section's re-org. It makes no sense to classify clients by license, since GPL'd clients don't necessarily have anything to do with Linden's code, just like BSD clients don't necessarily have anything to do with libomv. It does make sense to keep a list of Linden-derived clients though, since they're all more alike than not alike, and share both code and license encumbrance. [[User:Morgaine Dinova|Morgaine Dinova]] 01:28, 16 June 2009 (UTC)

===Viewers based on the Linden Lab GPL code (C++)===

*[http://secondlife.com/support/downloads.php Main Second Life viewer/client]
:The main (official) Second Life viewer, produced by Linden Lab with the help of patches submitted by the community, and available for Linux, Mac and Windows.

*[[Snowglobe|Snowglobe]]

:A new version of the Second Life client in a public repository where Linden Lab permits direct committing from select community members alongside daily Linden work. There is also a new build system to keep this version continuously building when new submissions are received, with new builds available to everyone. This version will become available as an alternative Linden download alongside the main SL client, once it is sufficiently stable.

*[[Alternate_viewers|Derived 3rd-party clients]] (''currently links to a mixed "Downloads" page, to be fixed'')
:A large list of clients (not necessarily 3D) developed in the free and open-source community using GPL code from the above two official viewers.

===Viewers based on the libomv/libsl code (C#)===

* [http://forge.opensimulator.org/gf/project/idealistviewer/ Idealist]
:IdealistViewer is a new cross-platform viewer based on the Irrlicht engine, PrimMesher, and LibOpenmetaverse. It can either use the Second Life protocols as provided by LibOpenmetaverse or the MXP protocol. Since it uses the Irrlicht engine it can simultaneously display prim/sculptie content and objects and animated meshes/avatars from a wide variety of sources such as Collada, .OBJ, DirectX, and Blitz3D files. It is not derived from the LL GPL viewer and is made available under BSD style licensing. It is designed to work with OpenSimulator but may also work with Second Life. It is written in the C# language.

* [http://forge.opensimulator.org/gf/project/lookingglass/ LookingGlass]
:LookingGlass viewer is a modular viewer with pluggable communication and rendering engines. Initial communication plugin uses LibOpenMetaverse and the initial rendering plugin uses PrimMesher and Ogre. It is written in C# and BSD licensed. Home site at http://lookingglassviewer.org/ .

===Viewers based on other libraries (python, C, etc)===

* [[Pyogp]]
: Pyogp is an open source project between Linden Lab and the Architecture Working Group (AWG) to support testing the (Open Grid Protocol (OGP). Written in Python, Pyogp will consist initially of a client library and test functionality to enable testing OGP-enabled virtual worlds such as Second Life and compatible OpenSim implementations. These components will expand as the effort matures. Pyogp is released under the Apache v2 license.

==Mailing Lists==
* [https://lists.secondlife.com/cgi-bin/mailman/listinfo List of Linden Lab mailing lists]
** [https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev Opensource-Dev] Main mailing list for SL developers
** [https://lists.secondlife.com/cgi-bin/mailman/listinfo/sldev SLDEV] Archived mailing list for SL developers
** [https://lists.secondlife.com/cgi-bin/mailman/listinfo/gridnauts gridnauts] Mailing list for participants in Open Grid Public Beta
** [https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp PyOGP] Mailing List for Python-based client library and test harness for the Open Grid Protocols
* [http://www.libsecondlife.org/wiki/Resources#Mailing_Lists libsecondlife]
* [http://opensimulator.org/wiki/Main_Page opensim]
* [http://lists.berlios.de/mailman/listinfo/openviewer-dev openviewer]
* [http://www.ietf.org/mail-archive/web/vwrap/current/maillist.html VWRAP]

==IRC==
* irc://irc.freenode.net/#opensl
* irc://irc.freenode.net/#opensl-jira (real time updates of entries to jira.secondlife.com)
* irc://irc.freenode.net/#opensim
* irc://irc.freenode.net/#opensim-dev
* irc://irc.efnet.net/#libomv
* irc://irc.efnet.net/#libomv-dev
* irc://irc.freenode.net/#openviewer
* irc://irc.freenode.net/#openviewer-dev
* irc://irc.freenode.net/#realxtend (Finnish language but can handle English if needed)
* irc://irc.freenode.net/#pyogp (Python test harness/pyogp Second LIfe library irc)
* irc://irc.freenode.net/#gridnauts (Open Grid Public Beta irc)

==Forums==
* [http://groups.google.com/group/realxtend| realXtend google forum]

==Capabilities==

* [http://www.cap-lore.com/CapTheory/index.html Capabilities theory and practice]
* [http://wiki.erights.org/wiki/Zooko%27s_triangle Zook's Triangle index] -- short list of interesting articles about naming and capabilties
* [http://www.cs.washington.edu/homes/levy/capabook/ Capability-based Systems by Henry Levy] --online copy of 1984 book on early implementations of capabilities systems
* [http://www.erights.org/ E language home] [https://www.cypherpunks.to/erights/ E language home mirror] [http://wiki.erights.org/ E wiki] --computer language dedicated to handling distributed trust issues
** [https://www.cypherpunks.to/erights/elib/capability/index.html Capability Computation]
** irc://irc.freenode.net/#erights
** [http://www.eros-os.org/mailman/listinfo/e-lang E language mailing list]
* [http://www.eros-os.org/mailman/listinfo/cap-talk mailing list for capability systems]
* [http://mscheffler.wordpress.com/2008/01/20/diploma/ blog and thesis on caps in virtual worlds Martin Scheffler]
* [http://homepage.mac.com/kpreid/elang/den.html Cap-based MUD by Kevin Reid] --written in E
* [http://www.fudco.com/chip/lessons.html discussion of ancient (Commodore 64!) video game that used capabilities]

==Misc==

* [http://blog.signpostmarv.name/2008/07/29/non-unique-region-names-within-the-confines-of-a-single-grid-yay-or-nay/ non-unique region names within the confines of a single grid, yay or nay ?]
* [http://blog.signpostmarv.name/2008/01/04/map-api-in-new-location/ discussion of new Map API and related issues]
* [http://wiki.secondlife.com/wiki/Open_Source Open Source Portal] --index to all things Open Source for Linden Lab

=Members=

Founder [[User: Zha Ewry|Zha Ewry]]

[[User:Saijanai Kuhn|Saijanai Kuhn]]

[[User:Tao Takashi|Tao Takashi]]

[[User:Tillie Ariantho|Tillie Ariantho]]

[[User:Dr Scofield|Dr Scofield]]

[[User:Burhop Piccard|Burhop Piccard]]

[[User:Vicero Lambert|Vicero Lambert]]

[[User:Morgaine Dinova|Morgaine Dinova]]

[[User:Silicon Plunkett|Silicon Plunkett]]

[[User:Dale Innis|Dale Innis]]

[[Category:Architecture Working Group]]
[[Category:Grid_Interoperability]]
[[Category:AW Groupies]]
[[Category:MMOX]]

Microsoft Windows Builds

2010-06-16T14:12:11Z

Stickman Ingmann: /* Getting other development tools */ Compile required zlib-devel (mentioned in the troubleshooting section) from cygwin to work for me, adding as requirement.

{{multi-lang}}
{{CompileNav}}

On Windows, there are several options on build (compile) environment of the Second Life.

This page explains how you can compile the Viewer on Microsoft Windows.

Currently, only 32 bit binary is tested. There seems to be several trials to produce 64 bit Windows .EXE of the Viewer. If you did, please write your experience on [[Talk:Microsoft Windows Builds|the discussion page]] (regardless it was successful or not!)

== Choosing and preparing a compiler ==

=== Linden-supported compilers ===

Supported compiler: '''Visual Studio .NET 2005 Professional'''

You need to setup the compiler and Microsoft Development tools as follows:
* Setup [[Microsoft Visual Studio]]

=== Community experimental compilers ===

If you don't have Visual Studio .NET 2005 Professional, you may wish to try one of the following alternatives.

* Visual C++ 2005 Express ([[Microsoft Visual Studio|instructions]], but the screenshots for [[Compiling the Viewer (MSVS2008)|VS2008]] are worth a glance too)
* Visual Studio 2008 ([[Compiling the Viewer (MSVS2008)|instructions]])
* Visual C++ 2008 Express ([[Compiling the Viewer (MSVS2008)|instructions]])

{{Warning|Boost support with Visual Studio 2008 is problematic as of this writing. Check {{jira|VWR-9541}} before continuing on this path.}}

NOTE: Make sure you install to paths without spaces in it.

== Getting other development tools ==

You will need to install the following tools to compile the Viewer:
* '''UniCode NSIS'''([http://www.scratchpaper.com/home/downloads download Unicode NSIS])
** This is the package installer used to build Setup.exe. <b>Note</b>: As of this writing the file is downloaded with an *.exec extension that needs renamed *.exe.--[[User:Nicky Perian|Nicky Perian]] 16:22, 30 March 2010 (UTC)
* '''CMake''' ([http://www.cmake.org/HTML/Download.html download CMake])
** As of this writing, the latest version is 2.6.2. <b>Note</b>: There are many known issues with CMake 2.6.0 and 2.6.1 in conjunction with building the Second Life Viewer. CMake 2.4.8 is supported for compiling the 1.21 version of the Second Life Viewer, but 2.6.2 is likely to become the new minimum requirement in the near future.
* '''Cygwin''' ([http://www.cygwin.com/ download Cygwin])
** When you run the cygwin setup utility make sure you have selected to install '''patchutils''', '''flex''', '''bison''', and '''zlib-devel'''(all located under "devel") which are not part of the default install. (If you missed one of these, the easiest thing to do is to re-run the entire installation.)
* '''Python''' (download either [http://www.python.org/download/ Python.org Standard Python] or [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython]
** If you are using a version of Python newer than v2.5, you may need to change the Python.cmake file. See the [[Talk:CMake#CMake_and_Python_2.6|CMake discussion]] for details (this change was necessary as of 1.21-r99587 source branch). )
* '''The Windows Platform SDK'''
** Get the latest version (as of 23 March 2010) here: [http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=c17ba869-9671-4330-a63e-1fd44e0e2505&displayLang=en Windows SDK for Windows Server 2008 and .NET Framework 3.5 SP1]
* '''DirectX 9.0 SDK'''
** Get the latest version (as of 29 Oct 2008) here: [http://www.microsoft.com/downloads/details.aspx?FamilyID=ea4894b5-e98d-44f6-842d-e32147237638&DisplayLang=en DirectX 9.0 SDK (August 2008)]

Verify that Cygwin, CMake, and Python are in the windows "PATH".

'''NOTE:''' '''DO NOT''' use the Cygwin version of CMake or Python. The Build will fail. (CMake specifically excludes the Cygwin version of Python, in the <code>'Python.cmake'</code> file)

== Downloading source code ==

You can download the Viewer source code on the [[source downloads]] page. You can also use a [[version control repository]]. If you're just starting out, it's probably best to get the latest Release version, rather than a Release Candidate, because the Release Candidates get updated quite often. But if you would rather work with the latest code, go for the [[version control repository]] "trunk".

If you're downloading from the [[source downloads]] page, there are three packages to get: the source package, the artwork package, and the library package. In versions 1.20 and earlier, Linden packaged the library binaries in the Libs package. For 1.21 and beyond, the CMake develop.py script now downloads '''most''' of the libraries that were previously in the libs zip file. This saves developers who are tracking trunk from constantly downloading them every update and only downloads updated libraries. As of this writing, there are some pieces packages that still require downloading, so be sure to grab the library and artwork bundles from the [[source downloads]] page.

'''WARNING:'''
* If the directory path you keep the SL source in has a space in it, the batch file that copies message_template.msg will fail. So, if you unzip or checkout the source tree into, e.g., "C:\Projects\Dir with space in name\Etc\linden", it won't work!
* You should also avoid using non-ASCII (national) characters in the paths, although some localized versions of the tool puts some as a default...
* Unzip or checkout your source tree into a directory that has as short full pathname as possible, since long paths cause some unexpected trouble during the build.

In other words, the easiest way to get this working is to get '''source''', '''artwork''', and '''libs''' from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like '''sl_1_21_6'''.

== Installing libraries ==

SL Viewer depends on some third party libraries. Some of them are open source, some others are not.

=== Open source libraries ===

As of Viewer version 1.21, all open source libraries are automatically downloaded as part of the build process, unless you choose to configure a standalone build.

=== Proprietary libraries ===

Linden does not include the following proprietary libraries. You will need to follow the instructions to acquire below and copy them to the source path.

However, it probably is a good idea to build an empty directory tree for the files below and first copy the files there and once completed, copy the whole tree to the actual source folder (like ''XCOPY OLIB SL_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder). If you do not want to do this, of course you can just copy the files directly into the linden source paths.

rem OLIBS.CMD to build a folder tree for 3rd party libraries and includes
md olibs
md olibs\linden\
md olibs\linden\libraries
md olibs\linden\libraries\include
md olibs\linden\libraries\i686-win32
md olibs\linden\libraries\i686-win32\lib_release
md olibs\linden\libraries\i686-win32\lib_debug
md olibs\linden\libraries\i686-win32\include
md olibs\linden\libraries\i686-win32\include\GL
md olibs\linden\libraries\i686-win32\include\quicktime
md olibs\linden\indra
md olibs\linden\indra\newview

==== Fmod ====
* Download & extract [http://www.fmod.org/files/fmod3/fmodapi375win.zip FMOD3.75 API for Windows]. (later versions, like FMOD Ex, are incompatible).
* Copy "fmodapi375win\api\inc\fmod.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmod_errors.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmoddyn.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_release" and to "linden\libraries\i686-win32\lib_debug"
(If using cmake, copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib\release" and to "linden\libraries\i686-win32\lib\debug")
* Copy "fmodapi375win\api\fmod.dll" to "linden\indra\newview"

==== Quicktime ====

Currently - as of version 1.21 - CMake requires Quicktime to be installed.

'''Note:''' This download requires a registration at the Apple Quicktime website and take a bit of time. You can avoid using QuickTime if you want, see [[Compiling_older_Viewers_(1.20_and_earlier_with_MSVS)#QuickTime_removal|this]] for details. Remember that your Viewer '''can't play in-world movies''' if you do so.
* Download & install the [http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/203/wa/getSoftware?fileID=20525&code=y&source=x&wosid=4h16WcyMtVfd2P1EffGafkoxFcr Quicktime SDK for Windows]
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_release" and to "linden\libraries\i686-win32\lib_debug".

(If using CMake, copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib\release" and to "linden\libraries\i686-win32\lib\debug" instead)

* Copy the contents of "QuicktimeSDK\CIncludes" into "linden\libraries\i686-win32\include\quicktime".

== Building with CMake ==

At this point, you should be ready to use [[CMake]]. '''NOTE''': CMake is only supported for Viewer versions 1.21 and beyond. Before you first run a build, you'll need to configure things. There's a <code>develop.py</code> script that will create a reasonably sane default configuration for you.

You must make sure that cmake is registered in the Windows environment, or you will get strange errors from develop.py. Right click My Computer -> Properties -> Advanced -> Environment Variables -> Inside System Variables choose PATH (case insensitive) and click Edit. Now in the value field, go to the end of the value and add a semicolon (;), and then the folder containing necessary binaries (example: C:\Program Files\CMake 2.8\bin). This might already have been set by the cmake installer.

From the command line, '''cd into the indra subdirectory''' and run one of the following commands (depending on your choice of platform and build environment):
** VisualStudio 2005: <code>"python develop.py -G VC80"</code>
** VisualStudio 2008: <code>"python develop.py -G VC90"</code>

'''NOTE:''' The above commands will configure a "non-standalone" version of the source code tree. This means that the required third party library packages (as built by Linden Lab) will be downloaded during the CMake process.

=== Finding your build directory ===

In the CMake world, we keep source and object files separate. The <code>develop.py</code> script will create and populate a build directory for you. It should be in one of the following locations:
* VS 2005: <code>'build-vc80'</code>
* VS 2008: <code>'build-vc90'</code>

=== Compiling ===

To start a build, do one of the following:
* Run <code>python develop.py build</code> in the indra directory.
* Load it into your IDE. For MSVS VC++:
** Use "File -> Open -> Project/Solution", and navigate to linden/indra/build-VC80/Viewer.vcproj (or build-VC90, as appropriate).
** In the MSVS toolbar, just to the right of the triangular "Start Debugging" arrow, is a text box whose tooltip is "Solution Configurations". Select RelWithDebugInfo.
** If ALL_BUILD is not set as your StartUp Project (the StartUp Project is displayed in bold font), right-click on ALL_BUILD and choose "Set as StartUp Project".
** Right-click on ALL_BUILD and choose "Properties". In "Configuration Properties -> Debugging", find "Working Directory" and navigate to "linden\indra\newview".
** (For Snowglobe 1.x) In the Solution Explorer pane, right-click on the project named "prepare" and select Project Only -> Build Only prepare. This downloads and installs precompiled libraries and only needs to be done when the source tree is clean or if libraries in the list included in the source tree get updated. Running this when not required is brief and causes no harm.
** Build -> Build Solution (F7)
** Debug -> "Start Debugging" or "Start without debugging".
** MSVC might not be able to find the executable. If not, point it to "linden\indra\build-VC80\newview\relwithdebinfo\secondlife-bin.exe", and try again.
** You may see an error due to not being able to find fmod.dll. If so, find a copy (remember, you copied this in a step above) and copy it into "indra\build-VC80\newview\relwithdebinfo". Try again.
** You may see an error due to not finding llkdu.dll. If so, find it in the normal installed version (make sure it's the same version as your source) and copy it into "indra\build-VC80\newview\relwithdebinfo". Try again.
** Good luck!

=== Where's the built Viewer? ===

On Windows, the built Viewer ought to run from VS2005.

To run outside MS VS, see Discussion tab:
[[Talk:Microsoft_Windows_Builds#Running_Viewer_outside_of_MS_VC]]

=== Build instructions for 1.20 and earlier ===

See [[Compiling older Viewers (1.20 and earlier with MSVS)]] if you'd like to compile a version of the Viewer older than 1.20.

== What to do if it doesn't work for you ==

* Ask for help on [[IRC]] (irc.freenode.net #opensl)
* Find someone on the [[SLDev|SLDev mailing list]]
* Fix it: [[Modifying CMake Files‎]] (and please, submit a patch!)

Please also see the (user contributed) instructions at [[User:Michelle2_Zenovka/cmake]]

[[Category:Compiling viewer]]

LSL HTTP server

2010-06-02T06:47:16Z

Stickman Ingmann: /* Script API */ Added ports used by the HTTP server

{{LSL Header|ml=*}}
== Introduction ==
This is the counterpart to [[llHTTPRequest]]. While llHTTPRequest enables LSL scripts request data from HTTP-accessible sources, HTTP-in enables outside sources to request data from scripts in Second Life. The key difference is that llHTTPRequest exchanges data when the script in SL wants; HTTP-in allows outside sources to determine when they need to communicate with scripts in SL.

Prior to HTTP-in, similar functionality could be achieved by [[HTTP Polling|polling]] with [[llHTTPRequest]], [[llEmail]] and [[:Category:LSL_XML-RPC|XML-RPC]]. All three are cumbersome and the latter two have serious scalability bottlenecks.

It is important to note that LSL HTTP servers cannot use HTML. See [[#Other_Limitations|Other Limitations]] for details.

== Uses ==
* Easily get data from LSL scripts to outside viewers, scripts or servers.
** Web front end for a visitor counter or other statistics accumulator.
* Easily get data into LSL scripts from outside viewers, scripts or servers.
** A store with a web front end that communicates to an in-world object to exchange L$ and inventory items.
** Inworld game for which an external program handles the primary game logic that needs to manipulate inworld items.

Gory Technical Details follow. Or jump straight to the [[LSL_http_server/examples | Script Examples]].

== Script API ==
* '''[[LlRequestURL|key llRequestURL()]]'''
: Request a new LSL Server public URL.
: An http_request event will be triggered with success or failure and include the returned key
: HTTP-in uses port 12046, and HTTPS-in uses port 12043.
: NOTE: URL's are assigned to the script that called them, an http_request event will not be triggered in a script separate from the one that requested the URL.
<lsl>request_id = llRequestURL();</lsl>
* '''[[LlRequestSecureURL|key llRequestSecureURL()]]'''
: Similar to ''llRequestURL'' except requests an HTTPS / SSL URL.
: An http_request event will be triggered with success or failure and include the returned key
<lsl>request_id = llRequestSecureURL();</lsl>
* '''[[LlReleaseURL|llReleaseURL(string url)]]'''
: Clear the specific URL, used for both secure and non-secure URLs.
<lsl>llReleaseURL("http://sim3015.aditi.lindenlab.com:12046/cap/3ff4f3f2-ea08-76c1-cef6-a22b4a573a7c");</lsl>
* '''[[Http_request|http_request(key id, string method, string body)]]'''
: Event triggered when an URL is hit:
:* id is unique to this request
:* Supported methods are GET/POST/PUT/DELETE
:* body: The body of the request.
: Event also triggered with response to ''llRequestURL'' and ''llRequestSecureURL''
:* id matches the key returned by ''llRequestURL'' or ''llRequestSecureURL''
:* method == [[URL_REQUEST_GRANTED]] for success, [[URL_REQUEST_DENIED]] for failure to get an URL
:* body is the public URL. If unable to get a public URL body will be empty.
* '''[[LlHTTPResponse|llHTTPResponse(key id, integer status, string body)]]'''
: Send ''body'' to the requester with status code ''status''
:* id is the id from http_request that maps to the specific request
:* sending a response to the requestor will clear the request and delete information associated with it
* '''[[LlGetHTTPHeader|string llGetHTTPHeader(key id, string header)]]'''
: Returns the string for the specified header in the specified request. All received headers are converted to lower case and this function is case-sensitive. The returned string is limited to 255 characters.
:* Supported headers are:
::* "x-script-url": The base url, as originally received from [[llRequestURL]] or [[llRequestSecureURL]].
::* "x-path-info": Any trailing path information from the requested url
::* "x-query-string": Any query arguments, the text past a ? in the url
::* "x-remote-ip": IP address of the host that made the request
::* "user-agent": The user-agent header as reported by the requester
:* Supported headers sent by '''[[LlHTTPRequest|llHTTPRequest()]]'''
::* "x-secondlife-shard"
::* "x-secondlife-object-name"
::* "x-secondlife-object-key"
::* "x-secondlife-region"
::* "x-secondlife-local-position"
::* "x-secondlife-local-rotation"
::* "x-secondlife-local-velocity"
::* "x-secondlife-owner-name"
::* "x-secondlife-owner-key"
requested url: ''https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322/foo/bar?arg=gra''
x-script-url: ''https://sim3015.aditi.lindenlab.com:12043/cap/a7717681-2c04-e4ac-35e3-1f01c9861322''
x-path-info: ''/foo/bar''
x-query-string: ''arg=gra''
: This header information is valid for 30 seconds, or until [[llHTTPResponse]] is called.
* '''[[Changed|changed(integer change)]]'''
:* [[CHANGED_REGION_START]]: New changed() event triggered on region startup.
* '''[[LlGetFreeURLs|integer llGetFreeURLs()]]'''
: Returns the number of URLs available to this script.

== URL Lifetime Limitations ==
* URLs are '''temporary'''!
* URLs will be lost in the following cases, all detectable by the script events listed with them.
** On object derez/rez: [[on_rez]]
** On script save/reset: ''[[default]] [[state_entry]]() (trickier in multi-state scripts)
** On region cross or TP(attachments): [[changed]]() {{LSLGC|Events|event}}, [[CHANGED_REGION]] and [[CHANGED_TELEPORT]]
** On region restart: [[changed]]() event, ''new'' flag [[CHANGED_REGION_START]]
* When urls are 'lost' it means that all public urls for that script are gone, new ones will need to be requested and the new urls will '''''not''''' resemble the old ones.
* Maintaining persistent URLs will require building or using an external service similar to how [http://en.wikipedia.org/wiki/Dynamic_DNS Dynamic DNS] services work for tying domain names to dynamic IP addresses.

Contributed HTTP-in URL mapping implementations and services:
* A Dynamic DNS service running on Google App Engine (contributed as an example) can be found in the forums [http://forums-archive.secondlife.com/54/33/323981/1.html here].
* The [http://wiki.apez.biz/URLMap_API Virtual ID URLMap service] provides mapping from a static subdomain of your choice via a REST API (part of the free [http://www.apez.biz Apez Corp] [http://wiki.apez.biz/Development web-services API]).
* Yet another one, running on GAE, with password protected and private domains. http://wiki.secondlife.com/wiki/Public_Object_DNS
* The [http://www.silverday.net/sqndns SilverDay ObjectDNS] is an easy to use dns-mapping-service with many configurable options (password protection, write protection, etc.) and an optional web-interface. The scripts are available here on the wiki (LSL-Script Library/[[Silverday ObjectDNS]]).

== Resource Limitations ==
* There are a limited number of URLs available in each region, split by land ownership exactly like prim limits.
** Use [[llGetFreeURLs]] to get the exact number of available URLs for the script.
** The number of allowed URLs is the same as the number of allowed prims on the parcel the object is over.
**: ''Object owner does not matter, all objects over a parcel will use the resource pool for that parcel.''
**: ''Like prims, all the parcels owned by the same owner and in the same region share the same pool of resources.''
**: ''If you have two parcels in a region that each support 100 URLs, then you could use all 200 in object(s) on a single parcel.''
** The region's object bonus factor does not apply to available URLs.
**: ''If a parcel has a max of 300 prims in a region with a 2x bonus factor there will only be 150 urls allowed.''
* Each resident has their own unique pool of available URLs with a max of 38 URLs per resident.
** This is 1 per attachment point, but all 38 could be used by a single attachment for example.
* Vehicles are special and lazily moved to resident pools by the following logic:
** Any object that has a resident sitting on it is a 'vehicle'
** Vehicles will use the url resources from the parcel they are over until the cross a parcel border.
**: ''Specifically this prevents anyone from breaking your vending machine by sitting on it and making it a 'vehicle'.''
** When any object using URL resources with a resident sitting on it crosses a parcel boundary the resources will switch to the first sitting resident with enough resources. If no sitting agents have enough resources then the resources from the parcel being moved onto will be used. If even then there are not enough resources to use then the vehicle will be blocked from moving.
**: ''In short we do everything we can to find a pool to host the resources needed by the vehicle, but will block movement if we can't.''
* Parcel Sale: When a parcel is sold such that it changes the total available URLs in the region for either resident (seller or buyer) such that more URLs are being used than are available some objects will be returned.
** The objects returned will be from youngest object to oldest object of those using URLs in each category in order of object category: Temporary, Other, Group, Owner, Selected/Sat upon.
**: ''The '''only''' time objects are possibly returned is when parcels change owner, and only if more resources are being used than allowed.''
**: ''We return youngest temporary objects before older temporary objects before younger 'other' (owned by non-group, non-parcel-owner) objects etc.''

== Other Limitations ==
* Size of the body of the requests will be [[limit]]ed to 2k [[bytes]].
* Size of headers of requests will be limited to 255 bytes. This is per header, not total.
* The size of responses to requests is not currently limited, but this is subject to review during testing.
* The content type of the returned data is always 'text/plain; charset=utf-8'
*: ''Allowing more content type options is a possibility for the future, but not guaranteed.''
* There is a cap of 64 in flight requests per script. This is based on the maximum number of pending events in LSL. After hitting the 64 request limit, the simulator cap server returns '503 Service Unavailable' to the inbound request.
* ''We may throttle the rate we accept hits at the CAP server level as well. This is possible, but has not yet been decided.''
* HTML cannot be used without an external parser, as all output is plain text only. If making such a parser, remember that you should probably restrict access to only Linden Lab HTML URLs as to not have your bandwith stolen.
* It is important to note that when appending a query string to a cap URL there MUST be a trailing slash between the cap guid and the query string token '?'. IE https://sim123.agni.lindenlab.com/cap/f73b4b94-012d-44f2-bd0c-16c328321221?arg=gra will return an HTTP 500, but https://sim123.agni.lindenlab.com/cap/f73b4b94-012d-44f2-bd0c-16c328321221/?arg=gra will succeed. (This doesn't seem to be true.)

== Links ==
* [[LSL_http_server/examples | Script Examples]]
* [[LSL_http_server/design | Design Document]]
* Design Jira:{{jira|SVC-1086}}

{{LSLC|HTTP}}
{{LSLC|Communications}}