Temp on Rez changes

viz: /139/14/123033/1.html

I'd like to second the request that temp on rez not take effect until an object is rezzed, that is while I'm building it, it shouldn't get culled. This is really annoying BTW.

On temp on rez prim limits, that seems like an internal technical question, more is better for scripters, but I don't want to cause lag either. Personally, I only use a handful in my stuff, but they are very nice to have.

How about simply adding an 'on_rez' function(right term?) with llSetPrimativeParams([temp_on_rez, True]) to make it only check the box after the object gets rezzed? I do that with my balistics. You could then also have it delete the script after changing the properties I think. Also, to edit it, simply rez the object in a no-scripts area .

- Jolan

For one thing llSetPrimativeParams delays the script and for what I'm doing I can't afford the delay.

I'd prefer to work at my workshop thanks.

If you made the on_rez script its own script, wouldnt that stop the delay?..

Well then everytime you take it to inventory, take a copy that is not temporary first, then check it and quickly take the temp one. My best guess to date .

- Mike

Aren't temp on rez prims only temp if the flag has been set before it's rezzed? I think setting the temp on rez flag after rezzing the prim wouldn't make it temp until it's rerezzed.

nope, it takes effect immeditatly, so 60 seconds later it poofs

default
{
state_entry()
{
}

on_rez(integer rez)
{
if (rez != 0)
{
llSetPrimitiveParams([PRIM_TEMP_ON_REZ, TRUE]);
}
}

}