OpenSim Mantis Tracker
"We are aiming to provide copy/paste compatibility for scripts from SL. ... Often the user's ability to change a script is not sufficient to remove it, so the result is "It doesn't work" and more support requests."
In 0.6.7-RC1, llSetPos() fails this test completely with regard to child prims because OpenSim is much more restrictive than SL.
SL does not restrict child prims to moving in 10m increments, nor does it limit the total distance that a child prim can move to a maximum of 10m from the root. OpenSim 0.6.7-RC1 does both of these.
Test Cases
Test 1: Moving a child 20 meters from the root in 4 meter increments.
1) Create two 10m x 10m x 0.5m prims.
2) Put the Move20XTest script in one prim (script is attached).
3) Link the prims so that the script is in the child prim.
4) Approximately center the prims with each other.
5) Touch the child prim.
Test 1 - Results
In OpenSim 0.6.7, the child will move 8m.
In SL, the child will move 20m.
Test 2: Moving Child Prims to Form a 20m x 30m Board
1) Create a prim and put the Child20x30Test script in it (script is attached).
2) Make 5 copies of the prim. (shift-drag, control-Z)
3) Link the six prims together.
4) Touch the linkset.
Test 2 - Results
In OpenSim 0.6.7, only two of the prims will move.
In SL, the five child prims will move so that the linkset forms a 20m x 30m grid of prims.
Discussion
I don't believe that it is necessary to completely mimic SL's restrictions on child movement. It is a complex system that is partially based on the SL's Linkablity Rules (http://wiki.secondlife.com/wiki/Linkability_Rules). [^] For example, you can move a large child prim a farther distance from the root than you can a small child prim.
However, I do believe that it is vital that the default OpenSim rules are equal to or *less* restrictive than SL's rules.
Please, please, please make llSetPos() less restrictive for child prims.
Child20x30Test.lsl [^] (757 bytes) 2009-10-07 22:33 Child20XTest.lsl [^] (305 bytes) 2009-10-07 22:34 
