No more warp?

Rolling across the grid as we speak (I was just kicked out of Dogfight Atoll a little bit ago).


I'm afraid to ask...

Bunnyporter's my Warp teleporter.

Just tested it in m' burrow. On th main grid.

Got all kindsa happy customers now. Ah... hope.

Reckon they could limit it to <-10,-10,0>..<266,266,768> then.

The rolling update is supposedly finished, but my warpPos-scripted objects are still broken!

Maybe it has something to do with there now being over 12,000 active scripts in my sim (Work-arounds for the broken llSetPrimitiveParameters()? Even llSetPos() seems to be working even more slowly than usual.), but then, you'd think my workshop teleporter wouldn't be dropping me off 10m above its origin.

Maybe I'd better call support. Do they ever miss sims when they do these rolling updates?

Warppos is working again in The Future

*clings onto warppos as it drifts away* Take me with you!!!!!!!!!!!!

At the end of a stressful day, WARPPOS TAKE ME AWAAAAYYYyyyyyy.

So I'm curious why, after they reinstated its functionality...they took it away again??

I reverted my lifts back to the original code and tested - worked perfectly. Now this morning they're broken again.

Yep, I just found them broken again - this is very odd.

The recent patch broke many things, Warppos included. They put in a patch to fix that and broke many othere tings. They have now reverted back to the prior broken patch. LL really does not know what they are doing and their QC is absolute garbage.

WarpPos(vector destpos)
{   
    //R&D by Keknehv Psaltery, 05/25/2006
    //with a little pokeing by Strife, and a bit more
    //some more munging by Talarus Luan
    //Final cleanup by Keknehv Psaltery
    //Implementation of Failsafe by Winter Ventura 03/17/2007
    
    // Compute the number of jumps necessary
    integer jumps = (integer)(llVecDist(destpos, llGetPos()) / 10.0) + 1;
    
    // Try and avoid stack/heap collisions
    if (jumps > 100 )
        jumps = 100;    //  1km should be plenty
    list rules = [ PRIM_POSITION, destpos ];  //The start for the rules list
    integer count = 1;
    while ( ( count = count << 1 ) < jumps)
        rules = (rules=[]) + rules + rules;   //should tighten memory use.
    llSetPrimitiveParams( rules + llList2List( rules, (count - jumps) << 1, count) );
    
    // Fail Safe
    if ( llVecDist(llGetPos(), destpos) > 0.001 ) // Are we there yet? No?
    {
        while ( llVecDist(llGetPos(), destpos) > 0.001 ) // Okay let's do this the SLOW way
        {
            llSetPos(destpos);
        }
    }
}

This is a really rudimentary "failsafe" fallback from WarpPos to the older "slow train" method. It has ONE flaw that I've discovered.. so perhaps someone can help refine this further.

if destpos is underground, the beam get's stuck on the ground level, in an infinite loop. ANyone help me break that loop? Let's make the best WarpPos ever.

as in underground underground or just under a faked ground?
for the later making the item phantom should work?

For the former I guess you could keep a check to see if you are getting any closer and if not then abort safely.

Well, this is my rudimentary fix to warpPos I'm using atm. Basically I just removed PRIM_POSITION from the lists and did a loop to set the pos destinations.

warp(vector target) 
{		
	if (target.z > 768) {
		target.z = 768;
	}
	if (target == llGetPos())
	{
		llWhisper(0,"We are already on that floor");
	}
	
	integer jumps = (integer)(llVecMag(target-llGetPos())/10)+1;
	if (jumps > 100) {
		jumps = 100;
	}
	integer e = (integer)( llLog(jumps) / 0.6931471805 );
	list rules = [ target ];
	integer i;
	for ( i = 0 ; i < e ; ++i ) {
		rules += rules;
	}
	integer r = jumps - (integer)llPow( 2, e );
	if (r > 0) {
		rules += llList2List( rules, 0, r * 2 + 1 );
	}
	gothere(rules,jumps);
	//llSetPrimitiveParams(rules);
}	
gothere(list points, integer times)
{
	integer i;
	while (i < times)
	{
		llSetPos(llList2Vector(points,i));
		i++;
	}
}

Good thing is it's easy to revert since I only removed one thing and commented out the params call.

My goal actually, was to make a WaprPos subroutine that would try WarpPos first, and then could TELL if WarpPos wasn't working, and then "fall back" to the original method.

Newgate.. I mean "the real ground". Phantom or not, we're talking non-phys movement here, so moving through prims is NOT an issue.

The problem comes in if the ground is at 29m Z... and your target destpos is below that. (since llSetPos can't be used to move a prim under the "real" ground.

I know there's a way to detect the ground height.. Basically I need to fail out of the while loop if a setpos move would move the prim underground. (but not "fail" before getting TO the ground.)

Basically if I use the mod I posted.. the beam shoots to the ground.. and sits there flashing without unsitting the rider. WarpPos takes you to the same place (when working) but once it fails to "get to destpos" it completes and pops, depositing the rider.

I can show you the issue inworld if you're interested. Basically I need the beam to go as close as the system will allow it to get to destpos, then exit the while loop when it reaches an irreconcilable point.

Hmmm.... I noticed ALL KINDS OF THINGS broken during testing after the rolling update, then this morning my teleporters don't work again...

I assume they reverted the rolling update because it broke even MORE stuff.

you notice how they never roll back the wednesday updates? THAT update broke stuff.. so they apply a fix.. the fix breaks stuff, so they unfix. I wish they'd unupdate. (downdate?)

If you are using a workaround, try to avoid the distance-checking loop type. IE,

    while (llVecDist(llGetPos(),destpos) > 0.01)
        llSetPos(destpos);

Try to use one which calculates a number of setpos statements (plus one if you wanna be sure), loops only that many times, then exits.

That prevents prims getting hung forever in that loop in the case of trying to move below ground, or into a blocked parcel. IE:

//1.13.3 (2) fix by Redux
//Optimized by SiRiS & Talarus
warpPos(vector d) //R&D by Keknehv Psaltery, ~05/25/2006 
{     
    if (d.z > 768) {d.z = 768;}     
    integer s = (integer)(llVecMag(d-llGetPos())/10)+1; //The number of jumps necessary     
    do{
        llSetPrimitiveParams([PRIM_POSITION, d]);
    } while (--s); 
}

Since you already know the number of loops for the parameter list, that's the way to go.

I'm looking into designing a little Sonic-themed area, and was actually working on something similar to this. XD The only problem is that I can't seem to find a way to very specifically control the direction a person if going, which makes their velocity when they step on the object change their destination - By wide margins, if it's a long distance.

I have updated my WarpPos code on the forums, the lsl wiki, and the lsl portal to include the failsafe:

    while ( llVecDist( llGetPos(), destpos ) > .001 )    //Failsafe
        llSetPos(destpos);

Not sure how that is failsafe. You could still be stuck in a loop if you don't get to the destination because of some obstruction. The code at post 67 looks more failsafe to me!

Fine, fine...

if ( llVecDist( llGetPos(), destpos ) > .001 )
    while ( --jumps )
        llSetPos( destpos );

I just wana say thanks to all who are working on alternative methods and listing them here. I will try out these scripts next time I'm in world and set up a new teleport system to use as a backup for times like this. I use the Terra Mark III teleporter but i modified it to use WarpPos. Going back to default is gona suck, so I'm willing to see out the alternative methods.

Probably getting compulsive about this, but would this not be better?

integer jumps = (integer)(llVecMag(destPos-llGetPos())/10)+2; //The number of jumps that might be necessary      
while ( --jumps ) 
  if ( llVecDist( llGetPos(), destpos ) > .001 ) 
        llSetPos( destpos );
  else
    jumps = 1;

I would imagine this could still have problems with sim crossings, or would you use global coordinates?

The code snippet that I gave was meant to be appended to the end of the original WarpPos function, i.e.:

warpPos( vector destpos) 
{   //R&D by Keknehv Psaltery, 05/25/2006 
    //with a little pokeing by Strife, and a bit more 
    //some more munging by Talarus Luan 
    //Final cleanup by Keknehv Psaltery 
    // Compute the number of jumps necessary 
    integer jumps = (integer)(llVecDist(destpos, llGetPos()) / 10.0) + 1; 
    // Try and avoid stack/heap collisions 
    if (jumps > 100 ) 
        jumps = 100;    //  1km should be plenty 
    list rules = [ PRIM_POSITION, destpos ];  //The start for the rules list 
    integer count = 1; 
    while ( ( count = count << 1 ) < jumps) 
        rules = (rules=[]) + rules + rules;   //should tighten memory use. 
    llSetPrimitiveParams( rules + llList2List( rules, (count - jumps) << 1, count) ); 
    while ( llVecDist( llGetPos(), destpos ) > .001 )    //Failsafe 
        llSetPos(destpos); 
    if ( llVecDist( llGetPos(), destpos ) > .001 ) //Failsafe 
        while ( --jumps ) 
            llSetPos( destpos ); 
}

The failsafe should be enough for someone to get by if the function breaks until they can update their code to use a faster method.