Multi-bone rotation: motion vs graph

[WeirdoCello]

I've noticed that the graph-edditor and motion edditor handle multi-selections differently. In the graph edditor, if I want to rotate multiple bones along an axis, I ust select them all and rotate. So, if I want a character to hunch foward, I just select all the spine bones and rotate them foward, and it has the same effect as selecting them individually and rotating them one at a time.

In the motion edditor, however, multi-selections seem to be treated like locks. When I try the same thing, each of the spine bones moves as though it was locked to the last one I selected. Should I bother trying to change this, or is it just learn to work with it?

[celica soupra]

It's not specifically an editor thing, it's a rotation type thing. Right click on the middle of the rotation tool in the viewport and you can check either global or local rotation. In global the selected bones rotate relative to the world (your second example), in local they rotate relative to each other (your first example).

[Zappy]

Originally posted by 64GIGS.exe:

in local they rotate relative to each other (your first example).

But rotating multiple things in the Graph Editor causes the same rotation axis(es) of the bones to be rotated equally much, even if they're rotated completely differently, while using that "local" mode in the Motion Editor rotates them all in the same direction, which is not necessarily along the same axis, unless the selected bones are all facing the exact same way.

[raptornx01]

yeah, graph rotates and moves each bone independently. while the ME only uses the last one. that is why if you try to move a model in graph with everything selected the model explodes, because it is grabbing the same axis (for example Z) on every bone. and since that axis is always pointing in different directions for each bone they all fly off in different directions.

[WeirdoCello]

Originally posted by raptornx01:

yeah, graph rotates and moves each bone independently. while the ME only uses the last one. that is why if you try to move a model in graph with everything selected the model explodes, because it is grabbing the same axis (for example Z) on every bone. and since that axis is always pointing in different directions for each bone they all fly off in different directions.

unless you want an evenly-bent spine, in which case it's wonderfully practical.