Armature "Switch Direction" removes parenting. #34123

New Issue

Tobias Oelgarte · 2013-02-05T22:41:15+01:00

Tobias Oelgarte commented

2013-02-05 22:41:15 +01:00

%%%--- Blender version with error, and version that worked ---
r54287

- Short description of error ---

Switch direction in bone edit mode destroys parent relationships.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

I appended an example file. If you switch the direction of the selected bone, then the parenting of the bone is lost (children and itself), but the bone does not change the direction. If you select switch direction, then it switches the direction. The parent relation should not be lost and it should switch the direction in the first time.

%%%

%%%--- Blender version with error, and version that worked --- r54287 - Short description of error --- Switch direction in bone edit mode destroys parent relationships. - Steps for others to reproduce the error (preferably based on attached .blend file) --- I appended an example file. If you switch the direction of the selected bone, then the parenting of the bone is lost (children and itself), but the bone does not change the direction. If you select switch direction, then it switches the direction. The parent relation should not be lost and it should switch the direction in the first time. %%%

Tobias Oelgarte commented

2013-02-05 22:41:15 +01:00

Changed status to: 'Open'

Joshua Leung commented

2013-02-06 02:26:57 +01:00

%%%Assigning to self.%%%

Joshua Leung commented

2013-02-06 02:54:32 +01:00

%%%54345: Fixed the problem with flipping not working the first time. It turns out it was flipping the bone twice, nullifying the effect.

As for the parent relationships being removed, IMO this is not a bug. It doesn't seem useful/logical that you'd want a setup like A--> <---B (where both are pointed at each other) or <--A B--> (where both a rooted at the same point) where rotating A would rotate the move the pivot of B (which is no longer situated at tip of A). IMO it feels wrong to have inversed parenting like that, not to mention being confusing when all the bones are connected in a chain (where it's difficult to see that these relationships, leading to unexpected problems). Maybe I'm wrong on this though, as I've never really seen a need for this kind of setups in my own rigs. Is this useful for anything at all?%%%

%%%54345: Fixed the problem with flipping not working the first time. It turns out it was flipping the bone twice, nullifying the effect. As for the parent relationships being removed, IMO this is not a bug. It doesn't seem useful/logical that you'd want a setup like A--> <---B (where both are pointed at each other) or <--A B--> (where both a rooted at the same point) where rotating A would rotate the move the pivot of B (which is no longer situated at tip of A). IMO it feels wrong to have inversed parenting like that, not to mention being confusing when all the bones are connected in a chain (where it's difficult to see that these relationships, leading to unexpected problems). Maybe I'm wrong on this though, as I've never really seen a need for this kind of setups in my own rigs. Is this useful for anything at all?%%%

Joshua Leung commented

2013-02-06 02:54:32 +01:00

Changed status from 'Open' to: 'Resolved'

Joshua Leung closed this issue

2013-02-06 02:54:32 +01:00

Tobias Oelgarte commented

2013-02-06 03:51:39 +01:00

%%%It makes a lot of sense to have opposing bones. Any good foot rig (biped) has them and often you just want a bone to be rotated the other way around while editing, so that the tip is at the desired target location or the rotation axis is located at the opposite end. It is often very convenient to just flip a bone if you work with snapping and need to be precise.

I consider this a bug, because it breaks dependencies without notifying the user. It is named "switch direction" and not "disconnect from parent and all children (also flips direction)". ;-)

I noticed it today as i worked on rig and notices that the head of a bone should be at the location of it's tail, just because one constraint (IK) can't aim for the head or tail, So i wanted to switch the direction and lost all parenting in the progress and noticed it later on as nothing worked as intended.

%%%

%%%It makes a lot of sense to have opposing bones. Any good foot rig (biped) has them and often you just want a bone to be rotated the other way around while editing, so that the tip is at the desired target location or the rotation axis is located at the opposite end. It is often very convenient to just flip a bone if you work with snapping and need to be precise. I consider this a bug, because it breaks dependencies without notifying the user. It is named "switch direction" and not "disconnect from parent and all children (also flips direction)". ;-) I noticed it today as i worked on rig and notices that the head of a bone should be at the location of it's tail, just because one constraint (IK) can't aim for the head or tail, So i wanted to switch the direction and lost all parenting in the progress and noticed it later on as nothing worked as intended. %%%

Tobias Oelgarte commented

2013-02-06 03:54:18 +01:00

%%%PS: It should disconnect bones that are connected, but should keep the parenting.%%%

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Armature "Switch Direction" removes parenting. #34123