Difference between revisions of "PRIM TEMP ON REZ"

From Second Life Wiki
Jump to navigation Jump to search
(stuff the limit in here too, I guess)
Line 6: Line 6:


{{LSL_Function/boolean|boolean}}
{{LSL_Function/boolean|boolean}}
{{Issues/SVC-2380}}


}}{{LSL Constant
}}{{LSL Constant

Revision as of 19:52, 3 February 2010

Description

Constant: integer PRIM_TEMP_ON_REZ = 4;

The integer constant PRIM_TEMP_ON_REZ has the value 4

Used to get or set the object's temporary status. It lives until the next garbage collection cycle (about 1 minute). Does not count against normal prim limits. There are limits to the number of temporary objects that can exist in a region and the garbage collector may run sooner than expected.

The maximum temporary prims allowed are based on the regular prim limit, as (regular_prim_limit - current_regular_prims) + minimum(0.5 * regular_prim_limit + 400, 1000) (see forum posting).

llSetPrimitiveParams

[ PRIM_TEMP_ON_REZ, integer boolean ]
• integer boolean TRUE enables, FALSE disables

When used with llSetPrimitiveParams & llSetLinkPrimitiveParams

  • NOTE: This sets the entire object (linkset) when used in either function.

llGetPrimitiveParams

llGetPrimitiveParams([ PRIM_TEMP_ON_REZ ]);

Returns the list [ integer boolean ]

• integer boolean TRUE enables, FALSE disables

Caveats


Related Articles

Deep Notes

History

Before SL 1.9 objects would only be recognized by the garbage collector as temporary if they were rezzed with the temporary status already set. Setting the attribute only effected the object the next time it was rezzed. With 1.9 this was changed so that changing this status flag effected the object immediately. The constant name however was not changed to reflect this functionality change.

All Issues

~ Search JIRA for related Issues
   Temp-On-Rez Prim Limits Behave Erratically

Signature

integer PRIM_TEMP_ON_REZ = 4;