Duplicate objects including childs by default
Currently when you shift+d to duplicate parent object that hosts childs only parent object gets duplicated. You first would have to use e.g. "select hierarchy" to select childs and then duplicate.
Why on earth would somebody only want to duplicate partent object if it has childs?!?!
Please enable duplicate parent including child by default when shift+d or if there is a valid reason to only duplicate parent although it has childs make an option for default behavior in settings.
Thanks, Manu
4 Comments
This used to bother me, until I started using Collection Instances to group things. Think that's a more elegant way to manage grouping.
blender.community/c/rightclickselect/P7PA/ Duplicate parent with child (other way)
duplicating things that the user didn't explicitly select for duplication is counterintuitive and makes too many assumptions about the intent of the user.
say, for example- I have a rigged humanoid and want to duplicate the arm bones to another area that will have similar behavior, I select the upper and lower arm and duplicate. with your proposal I would select the upper arm and duplicate, and end up with an extra boatload of finger bones, wrist bones, roll helpers, up vector empties, FK/IK controllers, etc, etc, etc. All so you don't have to press one more button? hard pass.
there are a lot of people who use Blender in many different ways, and often I find that proposals on RCS fail to consider the broader implications of what "changing the default" actually means when they ask for it.
Agree, Maya does this and it's often annoying at best, if not causing big freezes or even crashes because the little dummy object you selected made you inadvertently duplicate a bunch of heavy mesh objects adding millions of polygons to your scene.
Hence, it should not be the default behavior, but instead something the aware user specifically asks.
There are multiple solutions, it could be an option amongst these:
Or, it could simply be an option from the duplicate operator itself, which can have a hotkey assigned. Or a different operator (though I think it would be best to not make different operators, as the same ability would be expected for Instance duplication, making secondary operators for every duplication-alike will be quickly messy).