Compact Local Vector Function

Necessity is the mother of invention, I suppose. Ever since I wrote this, I've been using it all the time.

Essentially, this takes any vector you feed it and spits it out relative to your object's rotation. If this has already been done, or better yet, already is an ll function, I wouldn't be the least bit surprised. If it isn't, well... USE IT! And get the Lindens to endorse it.

Just to clarify some speculation, this is not just a rewrite of llRot2Fwd - heck, it makes use of it. llRot2Fwd does nothing more than return a unit vector relative to the X-axis of a given rotation.

Also, several functions which use of "integer local" do not always mean local relative to the object with the script. This fixes that problem.

Furthermore, this can be tweaked readily to accept any rotation frame you wish to feed it, and the current version already does vector math for you. Also note that this script is optomized to prevent Gimbal Lock.

vector ReturnLocalCoord(vector local)
{
    rotation rot = llGetRot(); //Change me to any reference point you wish
    vector fwd = llRot2Fwd(llGetRot());
    vector vect = fwd * local.x;
    
    fwd = llRot2Fwd(<0.00000, 0.00000, 0.70711, 0.70711> * rot);
    vect += fwd * local.y;
    
    fwd = llRot2Fwd(<0.00000, 0.70711, 0.00000, 0.70711> * rot);
    vect += fwd * local.z;

    return vect;
}

So if I were to write:

ReturnLocalCoord(<1,2,3>

... and my object is rotated 90 degrees along the Y Axis, this would evaluate:
<3,2,-1>

Confused? Try it for yourself! You'll see what I'm talking about.

Best used combined with llSetOmega for propellers, llMoveToTarget for vehicles, etc, etc...

By means of edit: Actually, Rickard's solution works if you do this:

rot = llGetRot();
rot.s *= -1;
vector local = <1,0,0> / rot;

vector UnrotateVector(vector local)
{
     return (local / llGetRot());
}

I could be wrong, but I believe this does the same thing.

So it does, and I officially look like a dolt.

The last time I tried something like that it threw a type mismatch error. Guessing I just screwed it up last time, but I was told better. Either way, all I did was write my own X/Y/Z decomposition code.