When you do this: actor BODY:1 { channels { valueParm Muscular { keys { k 0 0.444 } } ~~~~~~~~~~ actor chest:1 { channels { targetGeom Muscular { keys { k 0 0.253632 } } ~~~~~~~~~~~~~~~~ actor rCollar:1 { channels { targetGeom Muscular { keys { k 0 0 } } ~~~~~~~~ actor rForeArm:1 { channels { targetGeom Muscular { keys { k 0 0.388339 } } It makes a mess: The value from Body = 0.444 gets passes to every slave morph. The value does not show on the dial - Poser knows it, does not show, will Spawn with it. (MM4 will not use it.) So, you have an actual value of abdomen = 0.444 chest = 0.697632 rCollar = 0.444 rForeArm = 0.832339 This is the same morph, not a bunch of singletons thrown together. The dials on the groups begin with pbm- This means = "my control is in Body, not here" This morph is made to be used with identical values on all components. You make it on the whole body. It is just saved out as sub-groups. There are duplicate verts at the seams between groups. The chest is stretched outside its neighbors, and in the case of Collar-chest - it is actually the same group for all intents. You say: 'It looks OK to me.' . Poser smooths - it tries to compensate. But you can get black spots, sharp angles, other weirdness. If you look carefully. If you were expecting to see valueParm numbers on the slave groups, it does not happen, either on the dials, or in a pose file made from these settings. By hacking the PZ2 and entering the value in Body valueParm, you have done enough, the pose will work. By also setting slaves at different inter-group values, you are breaking the seams. You can go to every slave and set an identical value, but why bother, when the master does this for you? You have a different issue with SoftenHip. I don't know if you have meesed with Buttock values, but this morph is a Partial body morph , I think, the Body valueParm only sets hip and hip sets the rest. Your actual value for this morph is ~1.1 - the Body value adds to hip and the sum is passed to the others. If you were a compulsive type, you may have pushed a valueParm to its +/- limits and reset the the min & max for each slave to these limits. In this case, the value will peg at the limit no matter what the ValueParm is, when higher, or if the sum of the two is higher. If you use it properly, just setting the limits at valueParm is enough, because the slave dials are not touched anyway. But, if you are determined to stunt, set the slaves' limits to avoid taking them too far.