possible LSL bug

I think I may have found a bug in llSetScale, someone try this:

Try resizing it when it's in the default state, then touching it. The setscale silently fails.

float gHeight;

default
{
    touch_start(integer num)
    {
        vector scale;
        scale=llGetScale();
        gHeight=scale.z  - 0.01;
        llSetScale(scale - <0,0,gHeight>);
        state flat;
    }

}

state flat
{
    
    touch_start(integer num)
    {
        llSetScale(llGetScale()+<0,0,gHeight>);
        state default;
    }
}

Followup:

It never fails if you setscale to a minimum of 0.02. Looks like setscale to 0.01 is flaky.

Followup 2:

I think this is being caused by float inprecision, every now and then it must be getting 0.00999999... because of the subtraction I do.

Changing it to not calculate on the float works.

So, not an LSL bug. Case closed

Looking at the comments in the wiki it looks like llSetScale has always been kind of iffy. Try llSetPrimParameters instead.

Interesting. I've been noticing some flakiness on a 0.01 set scale recently too. My script isn't doing any math though. I'll see if it acts more reliably at 0.02.

Oh, well, this makes sense. I don't think 0.01 can be represented exactly internally, so when the sim is doing "if scale component > 0.01", you're losing because of float inaccuracies. Try targeting 0.011.

Just pointing out that setting scale WITHOUT a script is flaky at the moment....as are other parameters for that matter.