SetPrimitiveParams - Some Links Prevent ChangingSize

I have a contradictory one I can't figure out.
I have a linkset that's a control surface for a group of audio modules.
Uses linkmessage to communicate with them - works fine.
There's a prim that's a meter module which receives message from buttons and updates volume then does another linkmessage to the individual audio prims.
The meter will change color to indicate mute/unmute state - that works fine.
The ONLY THING IS
It only changes size to indicate level when its not linked to the audio prims.
They only receive via linkmessage and have no messagelinked functions in them, and they are responding fine.

So - it works as part of a linkset as either parent or child but won't work if I link in these other scripted objects (that only receive) to the linkset? Meanwhile, the other SetPrimitiveParams call to change the meter color works fiine in both circumstances??

Is there something I should know???

Even though you're using llSetPrimParams to set the scale, you should take a careful read of llSetScale (http://lslwiki.net/lslwiki/wakka.php?wakka=llSetScale). Specifically this sentence:

Sounds more like he's describing the bug with linking smaller prims though. I've had a group of spheres in a grid, 2 lines of 3, with 2.5m spacing between the 2 lines and 2m spacing between the spheres in each line. (so kinda like ::: ) The spheres are 0.5m in size

This is obviously well within the link distance limits, however, while I can link them originally without any problems, I always end up having issues if I unlink them...they will not, under no circumstances, relink together again and I will start getting the message that they're too far apart. I've seen this happen repeatedly with the only fix being to replace the spheres with brand new ones.

More related to sizing in a linkset, however, I've often tried to edit link parts on something and had it quit letting me move/size/rotate after the first 2 prims. The 3rd one I try to do this with will continually snap back into its original position, so I have to unlink that prim.

This is a fault I reported through the system a while ago.
Teeple Linden did eventually answer and had the following to say



The ticket number was #675335.

Ah thanks Newgate...at least I know they're aware of it.

To be more precise, the linkset distancing error seems to be directly related to the size of the prims in question. IE: The smaller they are, the closer they have to be together. It's almost as if it's compensating for the linkset distance required if you were to scale the object to its max size (until one hits 10m on an axis).

To correct my above statement, the spheres were actually 0.05m at those distances...the fix to make it readily relinkable was to expand them to 0.5. I attempted to do this, and then resize them to 0.05m while linked, but then the other bug I mentioned came into play as it let me change only the first 2.

I'll post this all onto Teeple Linden when i next get in world, which may not be for a few days.

I'm aware of that distance limit on linking dependency based on size.
I suppose it seemed like a good idea at the time.

So - just to eliminate it - this occurs with objects touching and I also have found no solution but to delete the object and rez a new one.

I really tried to avoid linking the objects because the system I'm building needs to be dynamic in terms of adding and removing objects with sound files in their inventory. Initially I used chat to communicate between the group controls and the individual sound objects - audicles - but chat seems to have such low priority it was more like a "source of uncertainty". Had no idea which objects would actually start playing or when - I swear some of those chat functions take a long time before they get through. So the linkmessage approach works a lot better for communication but then you get all the hassles of linking. If you're building something static you can wrestle it out and get to a point where you say o.k. don't touch anything it works, if not

I think I've found a way to unlink a single prim from the set - I do know that if you select a link set, then select 'edit linked parts' and select a single prim from the set and do an unlink ,you end up unlinking the whole set even though you only have one selected. On the other hand if you select the edit tool, then select 'edit linked parts' then select the single prim you want to unlink you've got a chance it will just unlink the one. ARgh - to try this I just did unlink one prim of a linkset and it wouldn't link in again, so I unlinked the whole set and now I can't get all that linked again. O>K> it took a while and its linked again?????


I'm wondering if this behavior is some kind of permission issue. It's hard to deal with all the variables - which is the root prim now, what's the link order, what kind of scripts are running, etc.. I've noticed different behavior depending on whether the object has a script going - sometimes turning off the script has made linking possible. But not always.

Q What's the difference between theory and practice?
A. In theory they are the same.