Long range teleport? confused

Hi, I have a very unique problem. I'm trying to find a teleport that will get customers up to a display area platform above my property at 400 meters. I am not a scriptor, I know enough to be quite dangerous (as I found out). I have found a lot of good teleport scripts and have been able to modify them to work. I have spent hours reading though these forums on teleport scripts (and my thanks to all of you for posting). Now I have the understanding that an avatar must 'sit' on something to be teleported to the destination. That might explain my problem. The teleport scripts I have used seem to work, they get me (and the TP pad) to the platform, but, the pad doesn't make it back. I think I found out why. On the return trip, the 'pad' has to cross over my neighbors parcel, a 512 parcel with 117 prims. He has used all of the 117 prims and I am guessing that the 'pad' being a prim, isn't being allowed to cross his parcel? Does that make sense? HELP! If there is any way around this, I'd sure like to find out. My estate has a long narrow shape, so I don't have the room to move things around, such as my primary display area on the surface so can put my platform over it. If I could, I doubt I'd be having this problem. Suggestions would be welcome. OH, and the neighbor hasn't been in since X-mas, he has a free account and got his land back in the 'First Land' days. I have been trying to buy him out for a year now, but he rarely comes in.

The 'teleport' method you are describing is actually a hack: You are not teleporting, instead you are sitting, this kind of 'teleport' has a 300meters range limit from object location to sit target, so maybe that's your problem with the teleport you have.

One solution is using a script that uses warpPos: a custom function that avoids this problem.

The other solution is using the only real teleport method that you can use in scripts: llMapDestination.

If the parcel isn't no-script, no-entry, there is something simple to do:

llSetPrimitiveParams([PRIM_TEMP_ON_REZ, TRUE]);

Before the call to warpPos() and the opposite:

llSetPrimitiveParams([PRIM_TEMP_ON_REZ, FALSE]);

Just after.

This will make the warper *temporary* so its prims do not add to the non-temporary ones of the full parcel and it will be able to go across. Besides, this is always a good policy not to "steal" prims to one's neighbor.

Attention! The warper must not stay temporary too long. After a minute, it will disappear... except if an avatar is sitting on it. (In this case, the delays starts after the avatar stands up.) Anyway, to warp over 400m, you won't have any problem.

Neighboring parcel object entry woes will affect warppos, but will not affect sit teleports in any way. Sit teleports work up to 520m, which your destination is well within.

Sit teleports use a combination of llSitTarget() and llSetRot() to work, and the prim itself never moves, just the avatar.

Oh! Did the range change recently? Used to be 300m in any dimension (still shown on lslwiki).

It's interesting that the warpPos prim is getting to the destination but not back. If that were the only problem, then it would be easy enough to change the script to rez a new copy of the teleporter and leave it behind when it departs... but if the return trip isn't successful, the outbound path is probably pretty perilous, too. Figuring out intermediate "waypoints" to route the warpPos may work, but extra effort. So if the llSitTarget trick has the range, that's reliable and quick.

There's a bug in parcel "Object Entry" restrictions that doesn't seem to affect non-physical prims being sat on by an avatar. Hence, it carries the avatar through the restricted parcel, but fails in coming back because the restriction kicks in.

Note that llSitTarget has a 300m restriction *per axis*. IE, it isn't a 300m radius from the prim, it is a clamp on each coordinate axis value. IE, the code goes something like:

llSitTarget(vector vOffset, rotation rRot) {
if (vOffset.x > 300.0)
vOffset.x = 300.0;
...etc for y and z and negatives.
}

As such, you can actually put someone at <300.0,300.0,300.0> relative to the position and (BIG HINT) rotation of the prim. Max distance is thus Sqrt(3.0*300.0*300.0) = ~520.

I leave figuring out the rotation math as an exercise to the reader (no, really, it is a fun challenge! ).

Supposedly it is 300m in EACH of the prim's LOCAL coordinate directions, which means that the total distance can be 300m*sqrt(3) which is very close to 520m. And since you can rotate the prim such that its local <1,1,1> axis (or other diagonal) is in the direction you want, that is the theoretical distance limit in any global direction. I've never really stress tested it or seen the need to myself, but there's the idea.

Oh. That would work.

(Somehow I'd always thought of that limit in grid coordinates, but that's daft, because the target is specified in prim coordinates.)

Thanks for the hint!

LOL..ok, thanks guys. I'm gonna have to research this, like I said...I am not a script writer. Sooo..this is kinda going over my head. To date, the problem still exists. I tried out a 'freebie' teleport system that I got from an NCI center. It did work (kinda), but I can't read the script, and I don't want a 'Trekie' teleport system. It even had issues, going both ways, but it did make the return trip. If any of you can refer me to a free script that I can incorporate into an object that will get around this issue, please let me know. I am presently trying to make a 'long range teleport' script work, but still have the same problem. Maybe this will be a challenge for you guys, eh? Appreciate the help. Thanks!

There is no challenge in giving you a free script and not the point of the forum. If you need to go past the 300,300,300 = 520 rule then just use warpPos. If you are having problems with it getting stuck on the return trip, then make it so that when you touch an object, a fresh "bubble" will rez that will TP you to the destination and then die when it arrives.

Post what you have for a script and we will walk you through what needs to be changed. In the process you will be learning and we will be fullfilling the premise of the Scripting Tips forum.

It's definitely not a challenge for us.

It's not really much of a challenge for anyone. Forum search for "long range teleport", or go to SLX and search the same, or spend a little time searching the various Wikis.

There are plenty of places where you can find solutions. The point of this forum is to learn, not to ask and receive completed product handouts.