User talk:TigroSpottystripes Katsu

PosJump

I would assume since the delay with the older llSetPrimParams functions comes after the call* and PosJump uses only one call, that the use of the old functions (as opposed to the new) would be no slower in operation then the new.

• Script delays happen after the function call, to avoid them being used repeatedly in too rapid succession. The result of the call is as instant as with any function without a delay, the script is forced to rest afterwards though.

Also, When an avatar sits on a single prim, a link_set is born with the prim acting as the root. A single prim teleporter is thus never not the root during operation (unless the passenger jumps off or crashes etc. Although that is highly unlikely during the instant that PosJump is active). -- Fred Gandt ^{(talk|contribs)} 13:11, 16 May 2010 (UTC)

They've recognized forced sleeps only made things worse, that is why they created llSetLinkPrimitiveParamsFast . Teleporting avatars across a sim is not the only possible use for quickly moving an object over vast distances. --TigroSpottystripes Katsu 14:49, 16 May 2010 (UTC)

No it's not. Very true. Good point. Well made. You'll be changing WarpPos too then? -- Fred Gandt ^{(talk|contribs)} 16:11, 16 May 2010 (UTC)

I haven't tested if it works with WarpPos code yet, i imagine it would, but i'll refrain from changing the examples there untill i verify it really works. --TigroSpottystripes Katsu 15:53, 19 May 2010 (UTC)