Excluding and then Including a collection in the Outliner resets object visibility #65730
Labels
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#65730
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.71
Blender Version
Broken: version: 2.80 (sub 74), branch: blender2.7, commit date: 2019-06-09 21:43, hash:
030c7df19d
Worked: (optional)
Short description of error
If you click the checkbox to the left of a collection to disable/exclude it, then you click the checkbox to re-enable it, all of the hidden objects in the collection will become unhidden. This shouldn't be the case. If you disable a collection, when you re-enable it, it should be added in with the same object visibility as it had when it was disabled.
Exact steps for others to reproduce the error
Start a new scene. Duplicate the default cube 3 times. Put all three cubes into a new collection.
Set the visibility of one of the cubes to hidden by turning off the eyeball icon in the outliner.
Click the checkbox next to the collection to disable/exclude it.
Click the checkbox next to the collection to include it. The hidden object will no longer be hidden.
Added subscriber: @stevewarner
Added subscriber: @ZedDB
You can just open the default cube scene and toggle visibility of the cube and then uncheck and recheck the collection to reproduce this.
Changed status from 'Open' to: 'Archived'
This is by design.
The moment you exclude a collection from your view layer you are letting of of the bases as well (the information storing the objects visibility for that view layer).
If the object is also linked in a different collection its visibility state will be preserved.
Added subscriber: @1D_Inc
What is the point of such a design?
If you hide objects, it is supposed that they will remain hidden until you will not perform unhiding operations via visibility.
Hiding objects mean "I don't want to see that objects until I will not unhide them" - not via excluding, not via renderabilty, not via indirect only - unhiding only via visibility.
Unhiding caused by non-unhiding operations is a design flaw, causing workflow issues, and should be fixed as similar inconsistency was fixed .