Scale Constraints Not Working Properly?

[sz200]

I have 2 joints, hip_A and knee_A. Both are scale constrained in X to their exact copy hip_B and knee_B.

Now if I scale hip_B in X, both hip_A and knee_A obtain scale values. Why is the knee inheriting scale from it's parent, the hip. It should not be... This is a pretty simple setup, and I'm not understanding whats going on.

I have toyed with the Segment Scale Compensate option under joints. Apparently turning this on, forces the joint not to inherit it's parents values. This works fine. The minute you introduce a Scale Constraint though, it totally ignores this and inherits its parents values.

Is this a bug or intended feature with Scale Constraints?

[gmask]

I just did a quick test of this and the knee did not inherit scale from it's parent so there is either a problem with your rig or a bug... for sanity check just make a new scene file and make a simplified skeleton and constrain it and see that it works the way you're expecting it to.

[sz200]

That is exactly how I went about testing this... with a simplified file. You can find it here to show you:

Scale Constraint File

If you click on hipA you can see that I have scaled it in X. Click on hipB and it has that same scale, as it is scale constrained to hipA.

Now go down the hierarchy to kneeB and it also has inherited the scale. Feel free to play with scaling hipA up and down to see how kneeB inherits the scale.

[joojaa]

Dont send mb (as in maya binary) files, ALLWAYS send out ma (as in maya ascii) files, this serves 3 equally important functions:

Trojan danger! a maya binary file is the perfect Trojan attack on the non wary, because it allows me to inject pretty much any code with the users privileges. Having a Ascii file in this case is like submitting yourself freely to a body inspection. so if your smart you never open third party mb files ever. How would you like a rootkit on your machine

Version support, a person with lower version of maya than you can open a ma file giving you a bigger potential audience

One can read it in plain text, often reading the ascii file can pinpoint the problem in a few seconds. So one could help you even on a machine with no maya

Aside for the fact that you should always save in Ascii format unless:

Its a big mesh only reference!

The file gets bigger than 30-60 megs

Partly for the reasons above but should something go wrong, its far more easy to salvage a MA file than a mb one. Especially if you use plugins!

[sz200]

Yes I normally do, and totally forgot.

It has been reposted with an .ma if anyone is interested in looking. Sorry folks.