batch-processing multiple prims

Hey. I'm working on a primsuit made of a bunch of fairly identical prims linked to a handful of invisiprims. I'd like to do the same change to all of the visible prims, as I look for juuuust the right look for it.

I was able to work out a script using llGetPrimitiveParams and llSetPrimitiveParams to do the change I want, but it's only going to work on one prim at a time. I don't want to have to rez out the attachment, modify the invisiprim that contains everything so I can access the child prims, and drop the script on every single one of them. (I certainly don't want to modify 60-70 prims by hand, especially if automation can let me quickly try out several options.)

But ll(G|S)etPrimitiveParams only works on the prim the script lives in. Is there an easy way to dump one script onto the parent prim, and have it dump itself onto all the child prims, then execute? (Auto-deleting itself like Jeff Gomez' prim mirror scripts would be a nice bonus.) I could get a script to clone itself, but then it stops dead. And dropping an llSetRemoteScriptAccessPin script on every prim will be kinda maddening...

Do that, then Tools -> Reset Scripts in Selection. Or maybe Set Scripts to Running. Some combination of the above.

Ah, thanks! I'd even halfway noticed those options when browsing through the menus the other day, but they didn't stick. Now I can tweak my Rez-inspired avatar's prims to happiness.

There is a couple 1 script options depending exactly on what your trying to do. As I did not see a specific goal, like change color or texture on all, I will list a few that are plausible. Feel free to IM me in game if these don't match up to what your trying to accomplish in the end.


Change color:

EX: llSetLinkColor(LINK_SET, <1,1,1>, ALL_SIDES);
This will set every prim within the link set to the color white without needing a script in every prim.

Change Opacity/Alpha:

EX: llSetLinkAlpha(LINK_SET, 0.5, ALL_SIDES);
This would set every prim within the link set to 50% opacity.

Unfortunatly there is not an llSetLinkTexture command, but below I have included the link to the manual work-around Wiki page provided by Jeffrey Gomez.
http://secondlife.com/badgeo/wakka.php?wakka=llSetLinkTexture

Hope this helps you out a little.

I'm programmatically altering the <i>geometry</i>, not the color/texture/alpha/etc, and also trying to avoid putting a listener script in ~80 prims by hand.

Well. This is strange. Tools->reset scripts in selection/set scripts to running in selection did nothing, regardless of which order I tried them in.

Tools->recompile scripts in selection fired them off, but this is incredibly time-consuming to wait for, and probably prone to being interrupted by lag. Most strange. Of course it's quite possible there's something broken in my self-replicating script, too. Time to collapse it down to a test case of just that.

There was a time when some of those commands would only work on a few out of the many prims one had selected, I'm not sure if that got fixed.

If you're just testing stuff out, finding a quiet sim and firing up your 80 listeners isn't going to do anything terrible. Alternatively... link messages?

If I have to recompile a lot of scripts I shift click all the objects with scripts in I want to compile then go get some coffee

I've been doing some vaguely similar stuff; it is a pain to manually distribute an llSetRemoteScriptAccessPin() script to all child prims, but only needed once. After that, just update the scripts via llRemoteLoadScriptPin (don't forget to set them to running). The updating takes a long while, though, especially with ~200 prims, so in the end I had the script in the child prim parse link messages for the values for the llSetPrimitiveParameter call, and the parent prim reading the values from a notecard and link messaging the individual prims in that linkset, so that the child prim script did not have to be updated everytime I decided on another color scheme If you're interested in seeing the code, I can drop the scripts onto your inventory later today.

This thread may help ... /54/c4/73704/1.html

storing the listen script in each prim and assigning it a "group number" may help..then you just have to send one linked message and include the "group number" for the child prims to listen for..Also I have a simple subgroup script in the library that will remember and relink a set of prims(based on keys now so no re-rezzing)/15/73/71754/1.html .. I am working on an more efficient/faster version once i get time to write the code but this is a good base