11-02-2005 11:53
dunno what caused it, so let me retrace what I did when I encountered the bug and anomolies I noticed


1) logged on
2) teleported home
3) created a prim to test out a rotation on command script
4) noticed that the prim was behaving oddly with the script, realized the prim was rotated 90 on the Y axis
5) created a new prim (this was rotated 90 on the Y axis by default; WTF), rotated it back to 0, put in the script I was testing
6) noticed that the script had the X and Z rotations mixed up.
7) inspected script, did not see any misplaced values, so I swapped the commands for my change X to work on the Z axis and change Z to work on the X axis
8) script worked
9) created new prim (was rotated by 90 on the Y be default so I reset it to 0 rotations) with the following very basic rotation script:

CODE
default
{
state_entry()
{
llTargetOmega(<0,0,1>,PI,1.0);
}

}


the prim rotates on the X axis instead of the Z axis, even though the prim is has <0,0,0> rotations.

10) logged off, logged back on again, created new prim. still has the 90 Y axis rotation by default, but the above script works just fine now, but all the prims I rez are still having a 90 rotation on the Y axis when they are created. did a hard boot of my system, same problem. this has made it a pain to remember to rotate all the prims I create back to 0 when I start my scripting.


I changed nothing with my configuration or my system prior to this error occuring.