Linkset within Linkset and Link Messaging

I'm working on a project right now for a scripted crib, and something is stumping me, namely with linking with possible issues in interlink messaging.

Ok - here's what I got.. I have two linksets.. one is the crib, and one is the crib side gate. The gate linkset consists of 3 prims, gate top, gate bottom and texture prim for the bars. The other linkset consists of all the other pieces of the crib.

The crib gate linkset is scripted to open and close on a listen command at the moment, but it's going to be messaged by the 'pose mattress' *laughs* which I've finally made work after all the pose rotational issues had been sorted out.

Anyway, I went to link the two linksets together and now only the prim with the script on the gate (with the texture railings) moves up and down, and not (was was linked with it) the top and bottom railings.

Unless I'm missing something stupid obvious, it appears I can't have two independant linksets 'linked' together as one object. Is this the case?

Considering people are going to be moving this crib around, I can see issues with the gate not being selected at the same time as the crib, thus the two being inadvertantly separated.

Also, if the two linksets are left independant, will messaging still work? I was under the impression that messaging only worked between prims of a complete linkset. Another wrong assumption?

Thanks!!

Teddy.

Just a stupid idea.. but if the above isn't possible, should I just throw the movement code into the top and bottom railings as well? It might look lame to have three individual prims moving out of sync, depending on lag, etc.

Yup, linking isnt hirarchial - once you link together two small link sets, they become one big link set. llSetPos/llSetRot will no longer move a group of prims around, only the child prim that called it (unless its in the parent, in that case it will move the set).


Here's a possible solution:
Make the gate and crib seperate link sets. However, have the crib tell the gate (via llSay) when it moves where it moves. The gate can then use this information to reposition itself. This way, the crib and gate will remain together, even while being seperate link sets.

Otherwise, youll have to deal with each prim of the gate moving out of sync with the rest.

Psst, I take commissions
==Chris

Egads.. yeah, that's kinda what I suspected..


I thought about that as an option.. kinda the way res-foo works.. unfortunately that seemed a little overkill for a product that I wouldn't be selling for very much. *laughs*

I finally got it all working, but I had to do some retexturing to get it down to one prim, so of course, it all works fine now.

The linking system needs some upgrades.

Thanks for the reply!

come join the party at Prop 607: Heirarchical Linking

Why don't you set up your crib using hinges? They are a lot simpler, and you just put physics on the crib and you're done.

A suggestion would be to use the integer part of the linked message as a kind of channel-number. Then in the link_message event, just check if its the correct channel and then act accordingly. Works fine in several things I made.

Till Stirling

On that Google TechTalk Philip mentioned that they were working on implementing hierarchical linking now. I know that means it'll probably be ages away, but I didn't know if it had been officially mentioned anywhere as actually being on the agenda.