Scaling flexi prims from a script

Hi all

I've just raised this as a bug, but wanted to know if anyone else has noticed it:

I have created, and have been selling, sets of scripted flexiprim curtains for some months. These curtains have a number of prim "panels" with flex properties, and are linked as a set to a "curtain rod" parent prim. Clicking the curtains causes them to "open" and "close", by moving the prims and rescaling them. This has been working perfectly well, but I noticed today that the scale function seems to be glitching on the flexiprims.

The prims move as before, but the scale effect is now reversed, almost as if the viewer is receiving the previous scale instruction rather than the latest one. Teleporting, relogging, or simply right clicking the object immediately fixes the scale to what it should be, suggesting a viewer problem, or data transmission to the viewer perhaps.

Whatever it is, it's irritating as hell. I don't even know if it affects everyone, or just me (and presumably a few others).

Any ideas?

There's something in the next SL client version patch notes that seems to be related

* Fixed objects disappearing if they were made flexible via script

possibly something about flexi prims and scripts got broken with 1.13, hopefully that one will fix it? o.O

I saw that in the release notes today. I've been working on a new product, and so have been playing with scripted flexi attachments a lot in the last few days. I haven't noticed anything like this. So I was a bit concerned with the release note, wondering what they were going to break by trying to fix a non-existent bug But it did mention something about making non-attached and attached objects work the same... so maybe the attachments work OK, and in-world rezzed objects don't?

Further to the details initially reported, I can now confirm the following:

1. This bug still exists on the test grid and in the beta viewer

2. The incorrectly scaled prims are visible to all players, and they are fixed for ALL players when any ONE of them right clicks the object!

3. The problem occurs regardless of whether the script uses llSetScale or llSetPrimitiveParams

4. The scale parameters that show in the viewer for the prim are the ones used directly prior to the ones most recently set - e.g. set scale to vector A, then vector B, then vector C - the viewer shows it scaled to vector B, then right click it or relog and it updates to vector C

I am implementing a temporary fix based on point 4 above, setting the scale twice in the script, first to a value fractionally different to the one I need and then again to the correct value immediately after. This gives me a workaround, but clearly it causes script delays and is a major pain in the ass.

Do you see the same behavior if the object is an attachment?

Yeah, it does the same thing as an attachment too.