Temp on Res and Lag

Ok I have heard many things about Temp on Res primatives thus far. I dont know if this belongs in Scripting or in Building either way the two relate.

Ok From my understanding a Temporary on Rez box is not a "True" Prim as it doesnt continually lag the server and the script associated with it only lags the server for the ammount of time that it "Creates" the Rezed Object.

So any scripters out there that know the True answer to this please speak up. As I have been using a Temp on Rez Script for my vendors for almost 8 months now.

Currently I was also told that Temp on Rez does not count against Land Prim Allottments. Unfortunately several store owners make people count the Rezed Prim as part of the vendor even though the box only stays in world from 55-90 seconds.

So Anyone please enlighten me

#1 Does a Temp on Rez Box LAG a sim
#2 Does a Temp on Rez Box Count against Prim limits of a Sim
#3 Does a Temp on Rez Box create lag in the same respect a switching Textures Prim does?

If anyone can help me by answering these questions Id greatly Appreciate it because the information I have says contrary to the asked questions as:

#1 I was assured by LL That they do not lag a Sim
#2 They do not count against Prim Limits as per LL.
#3 They are not as hard on the system as a "Hard" prim that switches textures Per LL.


So please anyone with any contradicting information please let me know as this is a battle Im tired of fighting alone.

Sincerely, Shadow

A temp on rez prim lags the sim less than a normal prim does, but only because it places a lower priority on processing that prim. You can best see this by creating a physical prim and moving it slowly. The prim will 'blink' in and out of existence as the sim rapidly decides to stop sending information out to other people about it at random.

If it has a script in it, that script probably uses up less processor time, but probably not by much.

A temp on rez prim does NOT use up a bit in someone's prim allotment, just like an attachment on your avatar doesn't use up prims on the land you're standing on.

The ultimate benefit to TempOnRez is just that. It's a temporary prim. Even if you've got an llDie in there, if it accidentally doesn't fire, it'll still disappear. Lag really isn't that much of an issue.

Any land owner making you count rezzed temponrez objects means that they're using a script to count your prims, and sensors can't differentiate between temponrez and non-temponrez.

Rezzing stuff repeatedly can cause massive amounts of lag, as it obviously involves a full object update being sent to the client. Do NOT try and be clever by using temp on rez prims to compensate for lack of land.

Recently I've been experimenting with a set of seventy objects that all rez a temponrez object once every ten seconds. Which means the entire set is rezzing one object every 0.7 seconds or so.

The only lag that occurs because of this is because all the objects are physical (it's actually a damn sweet looking effect for the half-minute or so before the server practically locks up).

This is probably one of those, "Use with discression" things, like with so much else in SL.

If one or two people do this, just to have a high-detail statue or something, no real harm. I've seen this done quite frequently, with minimal impact on a sim. I've done it myself, in fact, to test the impact (minimal). However, like physical objects, timers, sensors, listeners, etc, the more people do this, the worse it gets.

used for your purposes no it doesn't hurt anything shadow. you're rezzing a box every minute or so, and it's a very simple non-phys box with one non active script.

something i think is important to know that even the wiki doesn't say.... the temp on rez thing doesn't work if you rez the object yourself and it doesn't work if you check the box on an existing object and wait around for it to disapear. it only seems to work if you use llRezObject.

i dunno if they still don't count against the land's allowance but they won't disapear unless you use llRezObject.

Incorrect.



Dunno if correct, but possibly. However, seeing the incorrect statement above, I'd check before trusting this one.



TempOnRez will not start/kickin unless you are NOT editing the object. If I rez a TempOnRez object, it disappears within 90 seconds. If I rez a TempOnRez object and edit it, it will disappear within 90 seconds of my editing it. If I continue to hold my edit-pointer on the object, it will never disappear.

As far as I can tell, the temp-on-rez timer only starts ticking if the prim is rezzed. If you turn on temp-on-rez after rezzing it, it's just a normal prim with the temp-on-rez box checked.

thanks for the input Moleculor. guess i should have said "in my experience" on there.

1. i made a prim and checked the temp on rez box. i took it, rezzed it again and it sat there for about 10 minutes before i got tired of waiting for it to disapear. i wasn't editting it.

2. i made a prim and checked the temp on rez box but i didn't take it and rez it again. just let it sit there. i did some other stuff and it was still there about a half hour later. also wasn't editting it.

3. i made a prim and checked the temp on rez box. i took it, put it in another prim and used llRezObject to rez it again. about a minute or so later *poof* no more rezzed prim.

at least that's what happened to me. i like to test stuff out before i go around saying this is how it is. course i can't guarantee this is how it is for you.

edit: one other thing that's interesting. i rezzed a regular old prim with llRezObject and in its on_rez event i made it temp on rez. it sat there and sat there and never disapeared. obviously it's the same situation as #2 up there. just like checking the box on a prim that's already sitting in the world. once it gets to the on_rez event it's already rezzed. too late for temp on rez.

I just spent the last four hours rezzing little, tiny TempOnRez physical phantom objects in the sandbox from my inventory. They all disappeared without fail.

Are you SURE you don't have your edit mode on?

Could he have been on no-script land? I don't know if Lindens ever fixed that, but no-script land used to prevent temponrez objects from poofing.

Basicaly from the responces I have recieved thus far I am definately on the same sheet of music as everyone else.

I phrased the questions in a manor that would elicit contradictory information to be unvield and thus far the information everyone is providing is consistant with what I have been told in the past by LL.

So, With this knowledge I will continue to use my Vendors as they are. Unfortunately its still a bit mind boggling to explain to someone that has a limited knowledge about SL as to "What?" a Temp on Rez Prim is.

I have been using this for almost a Year now and have never had any Issues in the past. Unfortunately its mostly been a problem with ghosting that has occasionaly been a problem in the past.

Now as for my experience, if you rez a temp on rez prim and do not rez it while in edit mod it will die just like its suppose to. However, if you rez it while in edit mode then it won't die until you go out of edit and the temp on rez timer then kicks in and will die in 55-90 seconds depending.


However the only question that wasn't answered of my three was which is harder on a sim a Rezed prim or a prim that rotates textures?

Fixed it very very long ago. It may have cropped up since then, but it was definitely fixed at one point.



Rezzing a prim is harder on a sim than changing textures, but only in the sense that one drop of water is more than half a drop of water in a bucket full of water.

I have been trying to figure out if my new Christmas tree is a lagger (half a bucket) or just part of the background noise (one drop in the bucket).

The tree creates ornaments on the surface of a cone -- using llRezObject of Temporary on Rez prims. At any time, I have about 80 ornament prims on the tree, and create them at the rate of 8 ornaments every 4 seconds.

None of the tests I have done show any lag -- and I suspect folks will put away the trees after the season. And unlikely anyone will deploy a forrest of them.

Does this fall in the category of (possibly) creating massive lag, by trying to use temps to create more prims than you ought? Or perhaps it is just two drops in the bucket instead of the typical 1/2.

#1 - Not any more than a permanant "Box"
#2 - No
#3 - No

The only incremental cost of a "Temp on Rez" prim over a permanant prim is the cost for the sim to kill it after its time has expired.

- Ace

WRT #3 I think it should be said that while a TOR prim will not cause lag by itself, if you have a box rezzing TOR prims on a timer, it will cause exactly the same kind of lag as a texture changer: full object updates (the red puffs of smoke you see if you have "show updates" enabled)

Best way to test it is to find a "slow" sim (something running at 500 or less SimFPS) and rez a tree. See what percentage drop you see in SimFPS. If it's negligible, then you're fine. If it drops more than 5-10%, people probably won't appreciate the tree too much.

That said, people probably WILL end up rezzing forests, just for fun, so I'd suggest sticking some code into the core of the tree to set up a single listen and/or sensor (probably listen) that would allow trees to "hear" each other when planted, and disable themselves if another one owned by the same person is nearby.

Wolfie, believe it or not, lag mostly exists in SL because everything is a drop in a bucket, but there's far too many drops for too small a bucket