(as I was afraid) it doesn't work... Any clue/es? THANKS! 
hanging_layer? Clues? Seemed easy but...
Moderators: Víctor Paredes, Belgarath, slowtiger
hanging_layer? Clues? Seemed easy but...
Hmmm... HI! I need (for complicated/gravity reasons) to have a layer that never NEVER rotate for any bone influence or parent group rotation, I have thought in something like "hanging_bone.lua" embedded script provided by LM but acting over the entire scripted layer and not over a bone, could that be possible? Seemed easy and I tried happily to modify it and change the "bone.fAngle" instruction to "layer.fRotationZ" but (as I was afraid) it doesn't work... Any clue/es? THANKS!
(as I was afraid) it doesn't work... Any clue/es? THANKS! Well, THANKS to Ramón López (...) I've found an intrincated and temporally solution for this (based in several layers hierarchies), but well... I'm still thinking that the Embedded solution it'd be a good thing, so if anybody could easily help me I'd still be grateful , if not... doesn't matter 
*CIAO!*
, if not... doesn't matter *CIAO!*
I was doing some work on this last night. First, conceptually, it's more than an "immune to group movements" kinda problem. It would seem you want to keep the layer translations, scaling, whatever. Maybe even the X and Y rotation. An "immune to layer movements" setting might be handy for some things, but that would sem to mean the layer just don't move. Immunity to particular transformations specifically, like "immune to translation" or rotation or scaling would do the job, but a blanket setting is the same as putting the layer outside the group.
Besides that, I'm trying to figure something out. The ins-and-outs of the matrix transformations makes my head hurt, but I'm tryin'! I'll let you know if I have any luck. I'm basically trying to take the parent layers transformation (well just the rotation, which is the thing I'm having trouble isolating) and subtract that from the target layers ) frame rotation. Should do the trick if I can figure it out, but it would probably create keyframes every frame. The layer rotations only have an animated value, and not a separate value for the 0 frame, so I don't think it could be made to work on the fly like the bone copy bit. But I'm working on it.
Besides that, I'm trying to figure something out. The ins-and-outs of the matrix transformations makes my head hurt, but I'm tryin'! I'll let you know if I have any luck. I'm basically trying to take the parent layers transformation (well just the rotation, which is the thing I'm having trouble isolating) and subtract that from the target layers ) frame rotation. Should do the trick if I can figure it out, but it would probably create keyframes every frame. The layer rotations only have an animated value, and not a separate value for the 0 frame, so I don't think it could be made to work on the fly like the bone copy bit. But I'm working on it.
Not quite, there are times when you need to have objects inside of groups but dont want them to move with the rest of the group at all, some masking for instance.7feet wrote:An "immune to layer movements" setting might be handy for some things, but that would sem to mean the layer just don't move. Immunity to particular transformations specifically, like "immune to translation" or rotation or scaling would do the job, but a blanket setting is the same as putting the layer outside the group.
That could be very useful for resolve lots of peculiar (or not so peculiar) situations, mix techniques and increase possibilities! THANKS (one more time) 7feet! ryellman - After I posted that, Im started to think about masking. wasn't quite sure wher it would be applicable, but it's a fluid medium.
Part of the question with using (and writing) emebedded scripts is that, at this point, you can only use one per layer. If you have the wherewithal, you can do the cut 'n' paste and stack 'em up in one bit, but that's a little too much like work. Perhaps necessary sometimes.
Part of the question with using (and writing) emebedded scripts is that, at this point, you can only use one per layer. If you have the wherewithal, you can do the cut 'n' paste and stack 'em up in one bit, but that's a little too much like work. Perhaps necessary sometimes.