Hide children with parent
Although it can be achieved with the collection system; the possibility to link the children to the parent visibility of some objects/collections would help a lot. (A script allows to create this effect on all the existing children, but the driver created in that manner has to be activated running the script, and applies to all children of the scene without exception.)
In general all the fields that does not support drivers (hide in viewport; render X/Y resolution; ...) become a bag-end for blender hackers.
16 Comments
yes, this would be great. honestly I'd love to see it as a general preference that worked globally- it is VERY rare that I want to hide a parent object and see its children, and currently the only way to make a quick and easy "one button hide hierarchy" is to dump everything into a collection and hide the collection. not an ideal workflow.
* @testure * agree, when coming to maya is really annoying XD also there are no null groups, so to parent stuff, you need to add empties and it becomes a nightmare pretty early :v
I have a script that fixes this but it should really be standard
Do you?
I'd really like to try it.
Its a very simple script, all it does it recursively selects all children of the selected items and hides them. Heres the pastebin pastebin.com/uSKf5rP7
It makes 0 sense to me that hiding a parent doesn't hide the children. I believe most programs would hide them. Photoshop, godot, CSS, all hide children when parent is hidden. If the devs disagree, at least give us an option.
What the hell. Few hours ago here was like 17 votes or something. Is it again some moron twink attack?
* @IIIFGIII * I beg you perdon?
* @Melodicpinpon * Nevermind.
If I understand correctly what you are trying to do, this is achieved by pressing Shift while clicking on the "eye" icon of an object. That way you hide the object including child hierarchy.
* @Dest * You are right, it is quite simple and with the '.' finding in the outliner, it is easy. Although I knew about this option; I would like to reach this function without passing by the outliner: I try to use/convert Blender as/into an anatomy atlas and to invite non-blenderian (at all) people to use it. If I parent the labels to the objects or certains structures that have no meaning without their parent; I would prefere to make sure that it can not be shown without the parent. I would like to avoid having a label 'mandible' floating in the empty space -because somebody missed the Shift-lmb eye in the outliner-, or worse: pointing at another structure passing through the mandible (just an exemple).
* @Melodicpinpon * Then maybe, like you said in the description, collections is the way to go. You can parent/children collections and use the "exclude" checkbox on collection level instead of the "eye" for hide in viewport (or the other ones for disabling in viewport/render) if that can be taken advantage of.
* @Dest * Right, but this four-level hiding system (hide; disable, exclude and render) is too much for most cases and most people. Why not to make something like the 2D softwares by default: what you see is what you get; and leave the rest optional?
* @Melodicpinpon * well because it's not a 2D software. Generally you use a 3D software like Blender with the goal of rendering. And you need to be able to temporarily hide parts of your scene to clearly see and work on other ones while not affecting you render result. It would be inefficient to unhide everyhing just to check if your render would come up the way you want and then rehiding everything again to work some more on a deeply buried object. That's why you have options. I'm not saying it wouldn't be helpful having an exclude checkbox on a per object basis that would trickle down the hierarchy, but if you are parenting a quite populated hierarchy, you might as well use the collections.
I always parent objects as collections because that makes it easier to append a specific branch/subcollection to another blend file.
* @Melodicpinpon * So once again this is another proposal related to an EXTREMELY specific use case that has more to do with the non-blenderian (at all) general public instead of actual Blender Users. Wow.
The proper solution for this job is to hire a user interface designer and a web developer who knows webgl or three.js and have them make a user friendly system using data exported from Belender that does exactly what your target audience needs it to do.
* @thinsoldier * Please do not 'wow' me. I just wonder why everything accepts drivers but not the eye icon. The other posts that I made may help you appreciate the kind of obstacles one can face when dealing with complex hierarchies: blender.community/c/rightclickselect/Zthbbc/ blender.community/c/rightclickselect/Ythbbc/ blender.community/c/rightclickselect/Xthbbc/