warpPos is a still broken?

Is the warpPos fuction still inactive?
If so, is there away around it?

Some info is welcome thanks

possibly http://www.lslwiki.net/lslwiki/wakka.php?wakka=LibrarySenWarp

So its back again folks!. My tp systems working as it should again

Think it'll stay this time?, or another rollback?

WarpPos still isn't fixed. It runs like llSetPos, it stops at 10m . When will it be fixed??

I thought this was a deliberate fix in a recent update? It's not broken....... it's been disabled. I assume permanently.

That was acknowledged as a bad move and was supposedly fixed by a server-only update some time after:

http://blog.secondlife.com/2007/03/22/rolling-restart-on-main-grid-2/

I don't recall exactly what happened after that - is that the update that required a grid-wide rollback to undo it after the fact? I don't have a use for WarpPos personally, so I can't say whether it works right now or not, but I know the intention was for it to work again.

Warp pos works for me on the main grid.

Try this:

default
{
    state_entry()
    {
    }

    touch_start(integer total_number)
    {
        llSetPrimitiveParams([PRIM_POSITION, llGetPos() + <15, 0, 0>]);
    }
}

It should move 15m in X axis but it only moves 10

Darok - that never worked, the warp pos technique (hack?) works by chaining together multiple position rules in a single llSetPrimitiveParms call, not by setting a single rule to have a motion > 10m.

my warpos works perfectly fine.

I could give you a copy if you think yours is broken (but it shouldn't be, not anymore).

That's because that is not how warpPos works.

WarpPos breaks something like your 15m movement down into chunks that are no bigger than the 10m limit and applies them all at once.

So instead try:

vector pos;
default
{
	state_entry()
	{
		pos = llGetPos();
	}
	touch_start(integer total)
	{
		llSetPrimitiveParams([PRIM_POSITION,pos+<10,0,0>,PRIM_POSITION,pos+<15,0,0>]);
		llResetScript();
	}
}

Something like that would be more akin to warpPos' functionality.

Thx and sorry, it was a misunderstood. I found information that in a version it didn't work and then i wrongly tested the function. Yesterday i tested the correct call and it works.