llSetRegionPos FAILS TO WORK IN MEGA REGIONS!

[Kayaker Magic]

If you call llSetRegionPos with a co-ordinate that is larger than 256 in x or y, it just refuses to do anything and leaves the prim where it is.
I guess I'll have to go back to using warpPos again.

Here is a script to demonstrate the problem.
Put this in a prim. If the prim is located inside 0 to 256 on both axes it will march away. When it gets to the 256 border, it will stop.
Drag it back with the edit dialog, it will move until it hits the 256 border at the edge of the universe again.
If it starts outside that range, or if you drag it there, it will just sit where you put it and not move at all.

Code: Select all

default
{
    state_entry()
    {
        llSetTimerEvent(1);
    }
    timer()
    {
        llSetRegionPos(llGetPos()+<1,1,0>);
    }
}

[Deuce Halsey]

I confirmed your results in my 4-region megaregion world. The script works fine in the Southwest (Home) region. When it gets to the boundary with another region it stops and sits.
I also tried rezzing the object in the other 3 regions of my world - it just sat there.

[Dundridge Dreadlow]

We'll look into this after tomorrow's update.

[Brayla Sana]

I saw this and I wanted to mention that Firestorm's cut and paste feature also fails in the same way. It works in the sw home region only.

[Constance Peregrine]

We've fixed many scripting functions to work in Advanced Megaregions, including llSetRegionPos(). See http://www.kitely.com/virtual-world-new ... g-physics/.