Duplicated objects with children don't have visibility options in outliner just only object #95056

Closed
opened 2022-01-19 16:55:53 +01:00 by ManBlender · 7 comments

System Information
Operating system: Windows-10-10.0.18363-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-16 23:26, hash: 34d424fd64
Worked: (newest version of Blender that worked as expected)

Short description of error
As on image, there are sometimes cases where Duplicated objects with children don't have visibility options in outliner.
This situation doing case when must select object in outliner, but to manage visibility must go to object visibility and operate around checkboxes not in outliner.
The case is problem when we doing some masks for boolean modificators, where some objects are children for main parent object and must be hidden as cloned.
In the oldest blender I meet this same problem time ago. Not sure it's bug or I'm doing something wrong in this type process.
obj_visibility.png

Exact steps for others to reproduce the error
I'm not sure how the issue is produced. In simple example like in attachment no problem.
I don't know it's related with modification like bevel or boolean, but I used this and meet this problem.
I often doing shift+g to select all children then again shift+parent object, and alt+d or shift+d.
visibility_problem.blend

Edit:
Ok, I replicated the problem.
visibility_problem_replicated.blend
The issue is related with movements around collections and tree.

**System Information** Operating system: Windows-10-10.0.18363-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77 **Blender Version** Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-16 23:26, hash: `34d424fd64` Worked: (newest version of Blender that worked as expected) **Short description of error** As on image, there are sometimes cases where Duplicated objects with children don't have visibility options in outliner. This situation doing case when must select object in outliner, but to manage visibility must go to object visibility and operate around checkboxes not in outliner. The case is problem when we doing some masks for boolean modificators, where some objects are children for main parent object and must be hidden as cloned. In the oldest blender I meet this same problem time ago. Not sure it's bug or I'm doing something wrong in this type process. ![obj_visibility.png](https://archive.blender.org/developer/F12811625/obj_visibility.png) **Exact steps for others to reproduce the error** I'm not sure how the issue is produced. In simple example like in attachment no problem. I don't know it's related with modification like bevel or boolean, but I used this and meet this problem. I often doing shift+g to select all children then again shift+parent object, and alt+d or shift+d. [visibility_problem.blend](https://archive.blender.org/developer/F12811640/visibility_problem.blend) Edit: Ok, I replicated the problem. [visibility_problem_replicated.blend](https://archive.blender.org/developer/F12811648/visibility_problem_replicated.blend) The issue is related with movements around collections and tree.
Author

Added subscriber: @ManBlender

Added subscriber: @ManBlender

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

This is because these objects are children of another object, but at the same time they are not in 1 collection. As far as I can see this is correct behavior. Or do you want to report, that these objects should all end up in same collection but they don't? in such case please add steps to reproduce such behavior.

This is because these objects are children of another object, but at the same time they are not in 1 collection. As far as I can see this is correct behavior. Or do you want to report, that these objects should all end up in same collection but they don't? in such case please add steps to reproduce such behavior.
Author

This is because these objects are children of another object, but at the same time they are not in 1 collection.

I understood this case, but in fact this made dissonance, coz user can easy move children to another collection, and due that have many parents the options about visibility are not available in many place in outliner,buy this user must operate in properties. Now we can have case, when in some instance this children should be not visible but in other visible and this not working correctly then and not comfy to manage this.

Or do you want to report, that these objects should all end up in same collection but they don't? in such case please add steps to reproduce such behavior.

In my opinion to resolve dissonance this visibility options should be available in whole outliner as in object properties.
The feature that children are not main object as gray/transparent or alpha (not sure how to describe the object name in shadow) is enough to understand that is duplicated object.
If user prepared workspace that properties is hidden coz need long outliner then is this type problem that must open properties coz hard to find in outliner main source of objects.
In fact of usage in this type interface before illumination here that object properties can help me I spent some time to find source objects of copy. In case was many copies, then problem was more pungent.

The main question is, what is reason to turn of in outliner the visibility options? Regarding this case.

> This is because these objects are children of another object, but at the same time they are not in 1 collection. I understood this case, but in fact this made dissonance, coz user can easy move children to another collection, and due that have many parents the options about visibility are not available in many place in outliner,buy this user must operate in properties. Now we can have case, when in some instance this children should be not visible but in other visible and this not working correctly then and not comfy to manage this. > Or do you want to report, that these objects should all end up in same collection but they don't? in such case please add steps to reproduce such behavior. In my opinion to resolve dissonance this visibility options should be available in whole outliner as in object properties. The feature that children are not main object as gray/transparent or alpha (not sure how to describe the object name in shadow) is enough to understand that is duplicated object. If user prepared workspace that properties is hidden coz need long outliner then is this type problem that must open properties coz hard to find in outliner main source of objects. In fact of usage in this type interface before illumination here that `object properties` can help me I spent some time to find source objects of copy. In case was many copies, then problem was more pungent. **The main question is, what is reason to turn of in outliner the visibility options?** Regarding this case.

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'

I can't give you exact link to any document describing why, there may be more than 1 reason. For example as you pointed out if you turn of visibility of collection with parent, but children are in different collection, the parent/child relationship does not override collection visibility.

In any case, UI developer confirmed, that this is expected behavior.

Closing as this bug tracker is only for bugs and errors.
For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

I can't give you exact link to any document describing why, there may be more than 1 reason. For example as you pointed out if you turn of visibility of collection with parent, but children are in different collection, the parent/child relationship does not override collection visibility. In any case, UI developer confirmed, that this is expected behavior. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#95056
No description provided.