Teleporter Script Woes

I've had it happen to me sometimes when using a teleporter, I've ended up at the other end in a kind of space with a frozen view until I hit a key on the keyboard or something.

Well, even though I know there are tons of freebie teleporter scripts out there, I've trying to write my own. [1]

I have as my final wrap-up code:

changed(integer change)
{
llSleep(0.15);
llUnSit(llAvatarOnSitTarget());
}

And guess what, I'm ending up with that frozen point of view thing.

Anyone have any ideas what causes this?

If this has already been answered in this forum, my apologies. I did browse through all 18 pages first to see if it had been before posting.

_________________________________

[1] Writing my own because rather than having to type the destination vector params into a script, I'm having the script read the params from a notecard dropped into a prim holding the teleportation script.

It's an old bug. Being sent to limbo <0,0,0> on sits. Not a problem with your script.

Ah, thanks Destiny.

So there's nothing for it?

Pressing th escape key seems to get me out of that ok.

Hmmm..the intra-sim teleporter I've been modding aready reads from the description; changing it to preferentially read from a notecard when one is present should be easy enough. I'll have that up this or next weekened, its a fun short project.

/54/24/138989/1.html (scroll to the last couple forum entries entries)

yeah the reading from notecard thing was already covered by somebody here a short while ago, and it works like a charm! It's just trying to get it so that you don't to press a key such as escape to snap out of limbo at the end of it.

Destiny Niles wrote:


The <0,0,0> bug is not what is happening, as described by Chaz. Rather it's the annoying bug where your positioning seems to be in limbo for a short time after TP. It seems to be happening to me more often than it used too, with my in-sim teleporter. The only way out of the <0,0,0> bug is to either re-teleport or manually move out of the <0,0,0> location. What Chaz has described is just at temporary anomaly.

Chaz--
I simply wait out the delay and it corrects itself after a couple seconds.

I'm not sure if my AV is simply arriving below ground before moving up to the proper coordinates. I guess I could test this and use an Alt on a separate computer to see what the visual effect is when my main AV arrives.

I've noticed that this has only been happening to me with llSitTarget based teleporters on a semi-regular basis. I have yet to have this bug happen with a warppos based teleporter