Trouble with texture change script

[CadenzaInVivace]

I'm having trouble with my texture change script for objects with large amount of prims (50-100). It works but around 5-10% of prims are always left untextured, it's random prims. I'm guessing it's because of lag and the function is not executed properly a few times. I'm using llSetLinkPrimitiveParams and llSetLinkPrimitiveParamsFast, both have the same problem. This is my code: http://codepaste.net/vwsfti Can someone take a look and see what the problem is and offer some suggestions? Thanks.

[Qie Niangao]

Before driving yourself crazy, check to be sure others see the same parts of the object failing to update. I believe you may be seeing a bug in transmission of updates between sim and viewer, where different viewers will see different things. I seem to think there's a viewer setting that affects the problem, but off the top of my head I can't recall which viewer setting.

[CadenzaInVivace]

It's random prims not being retextured. I'm pretty sure it's a problem with the script not optimized as I have no problem using retexture huds by other creators for their stuff.

[Qie Niangao]

You're gonna make me look at that code, aren't you?

Just for completeness, I was thinking of BUG-1786, which was the topic of most of a Server user group back in September. Pretty sure the viewer setting I was thinking of was the viewer's Maximum Bandwidth, as suggested by Whirly in that meeting.

[Qie Niangao]

At first glance, and since you mentioned optimization, a couple of things: Firstly, it's not ideal to call llGetListLength(num0) each time you test for loop completion; it's slightly more efficient to call that function once and store the result in a variable, then test against that variable.

But a much bigger deal is to call llSetLinkPrimitiveParamsFast only once per linkset, with one long parameter list that steps through the linkset with PRIM_LINK_TARGET.

Unfortunately, however, none of this is guaranteed to make your problem go away.

[Dora Gustafson]

I haven't read the script but the size of 50 to 100 prims make me stop at 64, which is the number of events that can be stacked.
When that number is exceeded events are discharged, e.i. forgotten, not handled.

Read about it in LSL Events

This may be the reason to your troubles

:smileysurprised::smileyvery-happy:

[Miranda Umino]

You don t get enough authorization for some of your textures. ( some of them are , for instance , no transfer for you )

Even when you fill the UUID , you need some rights on the textures . 

Or some UUIDs are wrong

[ChinRey]

The linden Homes house control system does something like that. It's only been around for five years so it's still in beta but when it works, it seems to retexture the house in stages with pauses between them raher than in one big swwop. That might be the solution.