Second Life Wiki - User contributions [en]

Talk:Creating HUDs

2014-01-27T05:13:00Z

Revochen Mayne: /* False wording? */ new section

Bonjour à tous et toutes les SecondLifers,

Je suis nouvelle et essaie de découvrir toutes les possibilités de SL....
Je ne comprends pas bien comment fonctionne les HUD... ?
Je ne trouve pas vraiment de guide ou tutoriels en Français.

J'ai voulu commencer par un HUD faisant le lien entre monde web et SL le kit Slquery : SLQinfobox, slqinfohud....
j'ai juste quelques infos en anglais du site slquery.
après avoir récupéré la box et notecards faut-il s'enregistrer ?
faut-il faire /rez.lz.kit ?
y a t'il autre chose à faire que de "porter" sur un endroit de l'écran..

Pour le HUD outsmart je n'ai rien trouvé dans ma "library" ?

j'ai l'impression qu'on ne voit pas toujours un HUD reçu et porté sur une partie de l'écran..

Si je constuis par exemple une salle de réunion et possède un HUD "écran blanc" puis je permettre à quelqu'un qui arrive chez moi de l'utiliser...
faut-il qu'il appartienne à un groupe avec qui j'aurai partagé ce HUD ? doit-il impérativement en posséder un aussi ?

Désolée cela fait plusieurs questions....

Merci beaucoup pour toute information

Agréable surf sur SL

== So, what attaches to a HUD? ==

How are they created?
What attaches to them?
How are they interfaced to scripts?
This really does look promising as a powerful tool, i.e. from the point of view that i haven't ever seen it work. [[User:Unsyned Short|Unsyned Short]] 12:23, 11 December 2007 (PST)

== Particles ==

I think they made particles work in HUDs since 1.23RC [[User:Nexii Malthus|Nexii Malthus]] 04:17, 24 May 2009 (UTC)

== False wording? ==

Seems there is a false wording at at the "Differences in behavior" section where it sais:

"Despite the limitations, some HUD objects use it to great effect."

Guess it either has to say
"...some HUD objects use it to create great effects." or
"...some HUD objects use it to create effects."

But that makes me wonder about what type of effects it might be and adding a few examples might be a good idea?

LlSetText

2013-07-15T14:38:20Z

Revochen Mayne:

{{LSL_Function
|inject-2={{:PRIM_TEXT|set}}{{Issues/SVC-4539}}
|func_id=152
|func_sleep=0.0
|func_energy=10.0
|func=llSetText
|sort=SetText
|p1_type=string|p1_name=text
|p2_type=vector|p2_name=color
|p3_type=float|p3_name=alpha
|func_desc=Displays {{LSLP|text}} that hovers over the prim with specific {{LSLP|color}} and translucency (specified with {{LSLP|alpha}}).
|return_text
|spec=
|caveats=
*If more than one llSetText is called (By reset,interaction or script state) within a prim the latest call will take priority over the previous.
*{{LSLP|text}} is [[limit]]ed to 254 [[bytes]], if the string is longer it will be truncated to 254 bytes, even if that means the truncation will chop a character in half.
*An unbroken line of text of a great length may be broken automatically into two lines (one above the other).
*Floating text can be seen through walls and other object. Be considerate of neighbors in malls and apartment buildings.
**Visibility distance increases with prim size.
*Removing the script or deactivating it will not remove the prim's floating text.
**Floating text is a prim property and not dependent on a script for its continued existence.
*To remove floating text, use the following:
<lsl>
// ZERO_VECTOR has the vector value <0.0, 0.0, 0.0>
// when used as a color it's black

llSetText("", ZERO_VECTOR, 0.0);
</lsl>
*Shift-copying does not keep the floating text prim property. If the llSetText() script is not triggered when a copy made, the copy will not have the floating text.
*Vertical whitespace is removed from the end of the text string, so if you want vertical whitespace put any character (like a space) on the last line.
*Multiple linebreaks with empty lines are converted to a single linebreak, so add a whitespace character on every line you want to skip:
<lsl>
// Bad:
llSetText("Monkeys\n\n\n\n\n", <1.0, 1.0, 1.0>, 1.0);

// Good:
llSetText("Monkeys\n \n \n \n \n ", <1.0, 1.0, 1.0>, 1.0);
</lsl>
*Measurements showed a high impact of process time when doing numerous iterations in a while loop. For approx. 65K iterations the process times are ca. 5s without float text, 24s with llSetText and 96s when using llSetLinkPrimitiveParamsFast/PRIM_TEXT. Thats why its not adviced to make excessive use of a float text within such iterations.
|examples=
Example of how llSetText could be included in default code to show prim's name in green text:
<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");

// prim's name (not necessarily object's) in green and opaque
llSetText(llGetObjectName(), <0.0, 1.0, 0.0>, 1.0 );
}

touch_start(integer total_number)
{
llSay(0, "Touched.");
}
}
</lsl>
By default the floating text will appear on a single line. However, the floating text can be spread over multiple lines by using a line break "\n" (read [[SplitLine]] in section 'See Also').
===Color & Alpha===
{{{!}} class="sortable" {{Prettytable|style=float:right; margin-top:0;}}
{{!}}- {{Hl2}}
! Color
! Code
{{!}}- style="background:white"
{{!}}White
{{!}}<1.0, 1.0, 1.0>
{{!}}- style="background:grey"
{{!}}Grey
{{!}}<0.5, 0.5, 0.5>
{{!}}- style="background:black; color:white;"
{{!}}{{!}}Black
{{!}}<0.0, 0.0, 0.0>
{{!}}- style="background:red; color:white;"
{{!}}Red
{{!}}<1.0, 0.0, 0.0>
{{!}}- style="background:green; color:white;"
{{!}}Green
{{!}}<0.0, 1.0, 0.0>
{{!}}- style="background:blue; color:white;"
{{!}}Blue
{{!}}<0.0, 0.0, 1.0>
{{!}}}
The x, y & z components of the vector are used to represent red, green, and blue respectively. The range is different than traditional RGB, instead of being 0 -> 255, LSL uses 0 -> 1. <1.0, 1.0, 1.0>, means "white" and <0.0, 0.0, 0.0> means "black":
<lsl>
// <1.0, 1.0, 1.0> as color is white

llSetText("I am white", <1.0, 1.0, 1.0>, 1.0);
</lsl>
<lsl>
// ZERO_VECTOR is <0.0, 0.0, 0.0> and as color black

llSetText("I am black", ZERO_VECTOR, 1.0);
</lsl>
The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible):
<lsl>
llSetText("green text with alpha 0.5", <0.0, 1.0, 0.0>, 0.5);

llSetText("white text with alpha 1.0\nfully opaque", <1.0, 1.0, 1.0>, 1.0);
llSetText("white text with alpha 1.0\nfully opaque", <1.0, 1.0, 1.0>, 1.0);

llSetText("invisible black text with alpha 0.0\nfully transparent", ZERO_VECTOR, 0.0);
llSetText("invisible black text with alpha 0.0\nfully transparent", <0.0, 0.0, 0.0>, 0.0);
</lsl>
===Multiple lines===
<lsl>
// two lines of green text

llSetText("I am \n on two lines!", <0.0, 1.0, 0.0>, 1.0);
</lsl>
|helpers=
Drag this script out of inventory onto an object to erase its set text:
<lsl>
// http://wiki.secondlife.com/wiki/llSetText

default
{
state_entry()
{
// black and transparent
llSetText("", ZERO_VECTOR, 0.0);

llRemoveInventory(llGetScriptName());
}
}
</lsl>
Code to easily specify appearance of hovertext:
<lsl>
vector blue = <0.0, 0.0, 1.0>;
vector orange = <1.0, 0.5, 0.0>;
vector cyan = <0.0, 1.0, 1.0>;
vector pink = <1.0, 0.5, 0.76>;
vector green = <0.0, 1.0, 0.0>;
vector red = <1.0, 0.0, 0.0>;
vector white = <1.0, 1.0, 1.0>;
vector yellow = <1.0, 1.0, 0.1>;
vector purple = <1.0, 0.0, 1.0>;
vector black = <0.0, 0.0, 0.0>;

string hoverText = "TEXT GOES HERE";
vector hoverColor = white;// set predefined color or any RGB color vector in float form
float hoverAlpha = 1.0; // Sets the text's transparency, 1.0 being opaque, while 0.0 would be transparent

default
{
state_entry()
{
llSetText(hoverText, hoverColor, hoverAlpha);
}
}
</lsl>
To make hovertext under linked prims you can use this simple function:
<lsl>
mySetLinkText(integer linknum, string text, vector color, float alpha) {
llSetLinkPrimitiveParamsFast(linknum, [PRIM_TEXT, text, color, alpha]);
}

// For example:

default
{
touch_start(integer total_number)
{
mySetLinkText(LINK_SET, "TEST", <0,1,0>, 0.5);
}
}
</lsl>
|also
|also_functions
|also_constants=
{{LSL DefineRow||[[PRIM_TEXT]]}}
|also_articles=
{{LSL DefineRow||[[:Category:LSL Examples|Examples]]: [[SplitLine]]|Insert 'new line' escape codes at certain positions of a string}}
{{LSL DefineRow||Useful snippet: [[llGetObjectPermMask]]|Label an object with text and newlines to give away or sell}}
|notes=To actually display text on a prim, see [[XyzzyText]], or consider using parcel prim [[:Category:LSL_Media|Media]] options (useful only if you have control over the land's media settings.)
----
The function displays {{LSLP|text}} that hover over the prim's center, the prim position. The height over the center is proportional to the prim's Z-dimension exclusively
* It doesn't matter how the prim is rotated, so if Z is smaller than X and Y the {{LSLP|text}} may be seen {{LSLP|on}} the prim
|cat1=Effects
|cat2=Prim
|cat3=Stop
|cat4=Floating Text
}}

LlSetText

2013-07-15T14:37:16Z

Revochen Mayne:

{{LSL_Function
|inject-2={{:PRIM_TEXT|set}}{{Issues/SVC-4539}}
|func_id=152
|func_sleep=0.0
|func_energy=10.0
|func=llSetText
|sort=SetText
|p1_type=string|p1_name=text
|p2_type=vector|p2_name=color
|p3_type=float|p3_name=alpha
|func_desc=Displays {{LSLP|text}} that hovers over the prim with specific {{LSLP|color}} and translucency (specified with {{LSLP|alpha}}).
|return_text
|spec=
|caveats=
*If more than one llSetText is called (By reset,interaction or script state) within a prim the latest call will take priority over the previous.
*{{LSLP|text}} is [[limit]]ed to 254 [[bytes]], if the string is longer it will be truncated to 254 bytes, even if that means the truncation will chop a character in half.
*An unbroken line of text of a great length may be broken automatically into two lines (one above the other).
*Floating text can be seen through walls and other object. Be considerate of neighbors in malls and apartment buildings.
**Visibility distance increases with prim size.
*Removing the script or deactivating it will not remove the prim's floating text.
**Floating text is a prim property and not dependent on a script for its continued existence.
*To remove floating text, use the following:
<lsl>
// ZERO_VECTOR has the vector value <0.0, 0.0, 0.0>
// when used as a color it's black

llSetText("", ZERO_VECTOR, 0.0);
</lsl>
*Shift-copying does not keep the floating text prim property. If the llSetText() script is not triggered when a copy made, the copy will not have the floating text.
*Vertical whitespace is removed from the end of the text string, so if you want vertical whitespace put any character (like a space) on the last line.
*Multiple linebreaks with empty lines are converted to a single linebreak, so add a whitespace character on every line you want to skip:
<lsl>
// Bad:
llSetText("Monkeys\n\n\n\n\n", <1.0, 1.0, 1.0>, 1.0);

// Good:
llSetText("Monkeys\n \n \n \n \n ", <1.0, 1.0, 1.0>, 1.0);
</lsl>
*Measurements showed a high impact of process time when doing numerous iterations in a while loop. For approx. 65K iterations the process times are ca. 5s without float text, 24s with llSetText and 96s when using llSetLinkPrimitiveParamsFast/PRIM_TEXT. Thats why its not adviced to make extensive use of a float text within such iterations.
|examples=
Example of how llSetText could be included in default code to show prim's name in green text:
<lsl>
default
{
state_entry()
{
llSay(0, "Hello, Avatar!");

// prim's name (not necessarily object's) in green and opaque
llSetText(llGetObjectName(), <0.0, 1.0, 0.0>, 1.0 );
}

touch_start(integer total_number)
{
llSay(0, "Touched.");
}
}
</lsl>
By default the floating text will appear on a single line. However, the floating text can be spread over multiple lines by using a line break "\n" (read [[SplitLine]] in section 'See Also').
===Color & Alpha===
{{{!}} class="sortable" {{Prettytable|style=float:right; margin-top:0;}}
{{!}}- {{Hl2}}
! Color
! Code
{{!}}- style="background:white"
{{!}}White
{{!}}<1.0, 1.0, 1.0>
{{!}}- style="background:grey"
{{!}}Grey
{{!}}<0.5, 0.5, 0.5>
{{!}}- style="background:black; color:white;"
{{!}}{{!}}Black
{{!}}<0.0, 0.0, 0.0>
{{!}}- style="background:red; color:white;"
{{!}}Red
{{!}}<1.0, 0.0, 0.0>
{{!}}- style="background:green; color:white;"
{{!}}Green
{{!}}<0.0, 1.0, 0.0>
{{!}}- style="background:blue; color:white;"
{{!}}Blue
{{!}}<0.0, 0.0, 1.0>
{{!}}}
The x, y & z components of the vector are used to represent red, green, and blue respectively. The range is different than traditional RGB, instead of being 0 -> 255, LSL uses 0 -> 1. <1.0, 1.0, 1.0>, means "white" and <0.0, 0.0, 0.0> means "black":
<lsl>
// <1.0, 1.0, 1.0> as color is white

llSetText("I am white", <1.0, 1.0, 1.0>, 1.0);
</lsl>
<lsl>
// ZERO_VECTOR is <0.0, 0.0, 0.0> and as color black

llSetText("I am black", ZERO_VECTOR, 1.0);
</lsl>
The 1.0 is the alpha setting. 1.0 means fully opaque, and 0.0 would be completely transparent (invisible):
<lsl>
llSetText("green text with alpha 0.5", <0.0, 1.0, 0.0>, 0.5);

llSetText("white text with alpha 1.0\nfully opaque", <1.0, 1.0, 1.0>, 1.0);
llSetText("white text with alpha 1.0\nfully opaque", <1.0, 1.0, 1.0>, 1.0);

llSetText("invisible black text with alpha 0.0\nfully transparent", ZERO_VECTOR, 0.0);
llSetText("invisible black text with alpha 0.0\nfully transparent", <0.0, 0.0, 0.0>, 0.0);
</lsl>
===Multiple lines===
<lsl>
// two lines of green text

llSetText("I am \n on two lines!", <0.0, 1.0, 0.0>, 1.0);
</lsl>
|helpers=
Drag this script out of inventory onto an object to erase its set text:
<lsl>
// http://wiki.secondlife.com/wiki/llSetText

default
{
state_entry()
{
// black and transparent
llSetText("", ZERO_VECTOR, 0.0);

llRemoveInventory(llGetScriptName());
}
}
</lsl>
Code to easily specify appearance of hovertext:
<lsl>
vector blue = <0.0, 0.0, 1.0>;
vector orange = <1.0, 0.5, 0.0>;
vector cyan = <0.0, 1.0, 1.0>;
vector pink = <1.0, 0.5, 0.76>;
vector green = <0.0, 1.0, 0.0>;
vector red = <1.0, 0.0, 0.0>;
vector white = <1.0, 1.0, 1.0>;
vector yellow = <1.0, 1.0, 0.1>;
vector purple = <1.0, 0.0, 1.0>;
vector black = <0.0, 0.0, 0.0>;

string hoverText = "TEXT GOES HERE";
vector hoverColor = white;// set predefined color or any RGB color vector in float form
float hoverAlpha = 1.0; // Sets the text's transparency, 1.0 being opaque, while 0.0 would be transparent

default
{
state_entry()
{
llSetText(hoverText, hoverColor, hoverAlpha);
}
}
</lsl>
To make hovertext under linked prims you can use this simple function:
<lsl>
mySetLinkText(integer linknum, string text, vector color, float alpha) {
llSetLinkPrimitiveParamsFast(linknum, [PRIM_TEXT, text, color, alpha]);
}

// For example:

default
{
touch_start(integer total_number)
{
mySetLinkText(LINK_SET, "TEST", <0,1,0>, 0.5);
}
}
</lsl>
|also
|also_functions
|also_constants=
{{LSL DefineRow||[[PRIM_TEXT]]}}
|also_articles=
{{LSL DefineRow||[[:Category:LSL Examples|Examples]]: [[SplitLine]]|Insert 'new line' escape codes at certain positions of a string}}
{{LSL DefineRow||Useful snippet: [[llGetObjectPermMask]]|Label an object with text and newlines to give away or sell}}
|notes=To actually display text on a prim, see [[XyzzyText]], or consider using parcel prim [[:Category:LSL_Media|Media]] options (useful only if you have control over the land's media settings.)
----
The function displays {{LSLP|text}} that hover over the prim's center, the prim position. The height over the center is proportional to the prim's Z-dimension exclusively
* It doesn't matter how the prim is rotated, so if Z is smaller than X and Y the {{LSLP|text}} may be seen {{LSLP|on}} the prim
|cat1=Effects
|cat2=Prim
|cat3=Stop
|cat4=Floating Text
}}

LlSetLinkPrimitiveParamsFast

2013-07-15T10:56:02Z

Revochen Mayne:

{{LSL Function
|inject-2={{LSL Function/link|link}}{{LSL PrimitiveParam Categorize|Link}}
|func_id=353|func_sleep=0.0|func_energy=10.0
|func=llSetLinkPrimitiveParamsFast|sort=SetLinkPrimitiveParamsFast
|p1_type=integer|p1_name=link
|p2_type=list|p2_name=rules
|func_desc=Set primitive parameters for {{LSLP|link}} based on {{LSLP|rules}} with no built-in script sleep. This function is identical to [[llSetLinkPrimitiveParams]] except without the delay.
|spec
|caveats=
*Applying an operation to [[LINK_SET]] will apply it first to the root prim, then to each child prim.
* [[PRIM_LINK_TARGET]] is a special paramter which can be inserted to perfom actions on multiple prims on the linkset with one call.
*The sim will clamp attributes before storing them.
*The client will clamp attributes before rendering.
* [[PRIM_ROTATION]] is bugged in child prims, see [[llSetLinkPrimitiveParams#Useful_Snipptes|Useful Snippets]] for a workaround, or the linked SVC-93 issue below.
* '''Some prim properties are reset''' by this function
** A flexible prim will become not flexible
** A sliced prim will become unsliced
: In order to preserve properties they must be saved and explicitly set in the function call
{{LSL Tip|When wanting to change the alpha value of a face, please consider using [[llSetLinkAlpha]](integer link, float alpha, integer face); instead of [[llSetLinkPrimitiveParamsFast]](integer link, [ [[PRIM_COLOR]], integer face, vector color, float alpha ]);, that way you don't have to mess with the color settings. Also don't expect [[llSetLinkPrimitiveParamsFast]] being faster than [[llSetText]] when setting a float text property within a loop like at "% loading" status bars. Measurements showed llSetText being 3-4 times faster. That also might applies for similar functions.}}
|constants={{LSL Constants/PrimitiveParams|set|remote=true}}
|examples =
A simple script to light up a prim in a [[linkset]] when touched, and unlight the others using llSetLinkPrimitiveParams, when script is installed in the root prim of the linkset.
<lsl>
default
{
touch_start(integer num_detected)
{
// Turn off all prims

llSetLinkPrimitiveParamsFast(LINK_SET,
[PRIM_FULLBRIGHT, ALL_SIDES, FALSE]);

// Turn on the one that was touched

llSetLinkPrimitiveParamsFast(llDetectedLinkNumber(0),
[PRIM_FULLBRIGHT, ALL_SIDES, TRUE]);
}
}
</lsl>
A simple script which moves all child prims .25m higher than the root prim when touched.
<lsl>
default
{
touch_start(integer total_number)
{
vector obj_pos = llGetPos();
rotation obj_rot = llGetRot();
integer i=1;
while (i <= llGetNumberOfPrims())
{
vector prim_pos = llList2Vector(llGetLinkPrimitiveParams(i,[PRIM_POSITION]),0);
if (i > 1) // If not the root prim
{
prim_pos = (prim_pos - obj_pos) / obj_rot; // Convert from region coordinates to local coordinates
prim_pos.z += 0.25; // increase the Z position by .25m
llSetLinkPrimitiveParamsFast(i,[PRIM_POSITION,prim_pos]);
}
++i;
}
}
}
</lsl>
{{LSL Tip|You can use one function call instead of two when making use of [[PRIM_LINK_TARGET]].}}
{{{!}} class="sortable" width="100%" {{Prettytable}}
{{!}}- {{Hl2}}
! '''Preferred method using [[PRIM_LINK_TARGET]]'''
! '''Second method does the same effect-wise.'''
{{!}}-
{{!!}}<lsl>
default
{
touch_start(integer num_detected)
{
// color the root prim red and the first linked-prim green

llSetLinkPrimitiveParamsFast(LINK_ROOT,
[PRIM_COLOR, ALL_SIDES, <1.0, 0.0, 0.0>, 1.0,
PRIM_LINK_TARGET, 2,
PRIM_COLOR, ALL_SIDES, <0.0, 1.0, 0.0>, 1.0]);
}
}
</lsl>
{{!!}}
<lsl>
default
{
touch_start(integer num_detected)
{
// color the root prim red and the first linked-prim green

llSetLinkPrimitiveParamsFast(LINK_ROOT,
[PRIM_COLOR, ALL_SIDES, <1.0, 0.0, 0.0>, 1.0]);
llSetLinkPrimitiveParamsFast(2,
[PRIM_COLOR, ALL_SIDES, <0.0, 1.0, 0.0>, 1.0]);
}
}
</lsl>
{{!}}}
[[File:Readability_of_setlinkprimitiveparamsfast.gif|thumb|700px|center|'''For better readability order the params of llSetLinkPrimitiveParamsFast function calls by PRIM_LINK_TARGET.''']]
|helpers=
<lsl>
//-- PRIM_ROTATION workaround for child prims (works in unattached objects only)
llSetLinkPrimitiveParamsFast( linknumber, [PRIM_ROT_LOCAL, rot * llGetRootRotation()] )

//-- PRIM_ROTATION workaround for child prims (works in linked objects only)
llSetLinkPrimitiveParamsFast( linknumber,
[PRIM_ROT_LOCAL, rot * llList2Rot( llGetLinkPrimitiveParams( LINK_ROOT, [PRIM_ROT_LOCAL] ), 0 )] )

//-- PRIM_ROTATION workaround for child prims (works in all scenarios)
llSetLinkPrimitiveParamsFast( linknumber,
[PRIM_ROT_LOCAL, rot * llList2Rot( llGetLinkPrimitiveParams( !!llGetLinkNumber(), [PRIM_ROT_LOCAL] ), 0 )] )
</lsl>
|also_functions=
{{LSL DefineRow||[[llSetLinkPrimitiveParams]]|Set many primitive parameters}}
{{LSL DefineRow||[[llGetLinkPrimitiveParams]]|Get many primitive parameters}}
{{LSL DefineRow||[[llSetPrimitiveParams]]|Set many primitive parameters}}
{{LSL DefineRow||[[llGetPrimitiveParams]]|Get many primitive parameters}}
{{LSL DefineRow||[[llSetLinkAlpha]]|}}
{{LSL DefineRow||[[llSetLinkColor]]|}}
{{LSL DefineRow||[[llSetLinkTexture]]|}}
{{LSL DefineRow||[[llSetLinkTextureAnim]]|}}
|also_tests
|also_events
|also_articles
|notes=
===[[PRIM_POSITION]]===
{{#var:PRIM_POSITION/SLPP&A}}
|cat1=Prim
|cat2=Movement
|cat3=Status
|cat4=Texture
|cat5=Object
|cat6=Sit/Teleport
|cat7=Link/Set
|cat8
}}

LlSetLinkPrimitiveParamsFast

2013-07-15T10:44:36Z

Revochen Mayne: added delay note

{{LSL Function
|inject-2={{LSL Function/link|link}}{{LSL PrimitiveParam Categorize|Link}}
|func_id=353|func_sleep=0.0|func_energy=10.0
|func=llSetLinkPrimitiveParamsFast|sort=SetLinkPrimitiveParamsFast
|p1_type=integer|p1_name=link
|p2_type=list|p2_name=rules
|func_desc=Set primitive parameters for {{LSLP|link}} based on {{LSLP|rules}} with no built-in script sleep. This function is identical to [[llSetLinkPrimitiveParams]] except without the delay.
|spec
|caveats=
*Applying an operation to [[LINK_SET]] will apply it first to the root prim, then to each child prim.
* [[PRIM_LINK_TARGET]] is a special paramter which can be inserted to perfom actions on multiple prims on the linkset with one call.
*The sim will clamp attributes before storing them.
*The client will clamp attributes before rendering.
* [[PRIM_ROTATION]] is bugged in child prims, see [[llSetLinkPrimitiveParams#Useful_Snipptes|Useful Snippets]] for a workaround, or the linked SVC-93 issue below.
* '''Some prim properties are reset''' by this function
** A flexible prim will become not flexible
** A sliced prim will become unsliced
: In order to preserve properties they must be saved and explicitly set in the function call
{{LSL Tip|When wanting to change the alpha value of a face, please consider using [[llSetLinkAlpha]](integer link, float alpha, integer face); instead of [[llSetLinkPrimitiveParamsFast]](integer link, [ [[PRIM_COLOR]], integer face, vector color, float alpha ]);, that way you don't have to mess with the color settings. Also don't expect [[llSetLinkPrimitiveParamsFast]] being faster than [[llSetText]] when setting a float text property within a loop like at "% loading" status bars. That also might applies for similar functions.}}
|constants={{LSL Constants/PrimitiveParams|set|remote=true}}
|examples =
A simple script to light up a prim in a [[linkset]] when touched, and unlight the others using llSetLinkPrimitiveParams, when script is installed in the root prim of the linkset.
<lsl>
default
{
touch_start(integer num_detected)
{
// Turn off all prims

llSetLinkPrimitiveParamsFast(LINK_SET,
[PRIM_FULLBRIGHT, ALL_SIDES, FALSE]);

// Turn on the one that was touched

llSetLinkPrimitiveParamsFast(llDetectedLinkNumber(0),
[PRIM_FULLBRIGHT, ALL_SIDES, TRUE]);
}
}
</lsl>
A simple script which moves all child prims .25m higher than the root prim when touched.
<lsl>
default
{
touch_start(integer total_number)
{
vector obj_pos = llGetPos();
rotation obj_rot = llGetRot();
integer i=1;
while (i <= llGetNumberOfPrims())
{
vector prim_pos = llList2Vector(llGetLinkPrimitiveParams(i,[PRIM_POSITION]),0);
if (i > 1) // If not the root prim
{
prim_pos = (prim_pos - obj_pos) / obj_rot; // Convert from region coordinates to local coordinates
prim_pos.z += 0.25; // increase the Z position by .25m
llSetLinkPrimitiveParamsFast(i,[PRIM_POSITION,prim_pos]);
}
++i;
}
}
}
</lsl>
{{LSL Tip|You can use one function call instead of two when making use of [[PRIM_LINK_TARGET]].}}
{{{!}} class="sortable" width="100%" {{Prettytable}}
{{!}}- {{Hl2}}
! '''Preferred method using [[PRIM_LINK_TARGET]]'''
! '''Second method does the same effect-wise.'''
{{!}}-
{{!!}}<lsl>
default
{
touch_start(integer num_detected)
{
// color the root prim red and the first linked-prim green

llSetLinkPrimitiveParamsFast(LINK_ROOT,
[PRIM_COLOR, ALL_SIDES, <1.0, 0.0, 0.0>, 1.0,
PRIM_LINK_TARGET, 2,
PRIM_COLOR, ALL_SIDES, <0.0, 1.0, 0.0>, 1.0]);
}
}
</lsl>
{{!!}}
<lsl>
default
{
touch_start(integer num_detected)
{
// color the root prim red and the first linked-prim green

llSetLinkPrimitiveParamsFast(LINK_ROOT,
[PRIM_COLOR, ALL_SIDES, <1.0, 0.0, 0.0>, 1.0]);
llSetLinkPrimitiveParamsFast(2,
[PRIM_COLOR, ALL_SIDES, <0.0, 1.0, 0.0>, 1.0]);
}
}
</lsl>
{{!}}}
[[File:Readability_of_setlinkprimitiveparamsfast.gif|thumb|700px|center|'''For better readability order the params of llSetLinkPrimitiveParamsFast function calls by PRIM_LINK_TARGET.''']]
|helpers=
<lsl>
//-- PRIM_ROTATION workaround for child prims (works in unattached objects only)
llSetLinkPrimitiveParamsFast( linknumber, [PRIM_ROT_LOCAL, rot * llGetRootRotation()] )

//-- PRIM_ROTATION workaround for child prims (works in linked objects only)
llSetLinkPrimitiveParamsFast( linknumber,
[PRIM_ROT_LOCAL, rot * llList2Rot( llGetLinkPrimitiveParams( LINK_ROOT, [PRIM_ROT_LOCAL] ), 0 )] )

//-- PRIM_ROTATION workaround for child prims (works in all scenarios)
llSetLinkPrimitiveParamsFast( linknumber,
[PRIM_ROT_LOCAL, rot * llList2Rot( llGetLinkPrimitiveParams( !!llGetLinkNumber(), [PRIM_ROT_LOCAL] ), 0 )] )
</lsl>
|also_functions=
{{LSL DefineRow||[[llSetLinkPrimitiveParams]]|Set many primitive parameters}}
{{LSL DefineRow||[[llGetLinkPrimitiveParams]]|Get many primitive parameters}}
{{LSL DefineRow||[[llSetPrimitiveParams]]|Set many primitive parameters}}
{{LSL DefineRow||[[llGetPrimitiveParams]]|Get many primitive parameters}}
{{LSL DefineRow||[[llSetLinkAlpha]]|}}
{{LSL DefineRow||[[llSetLinkColor]]|}}
{{LSL DefineRow||[[llSetLinkTexture]]|}}
{{LSL DefineRow||[[llSetLinkTextureAnim]]|}}
|also_tests
|also_events
|also_articles
|notes=
===[[PRIM_POSITION]]===
{{#var:PRIM_POSITION/SLPP&A}}
|cat1=Prim
|cat2=Movement
|cat3=Status
|cat4=Texture
|cat5=Object
|cat6=Sit/Teleport
|cat7=Link/Set
|cat8
}}