Sub-collections on/off state not remembered if parent collection is switched off and then on #69812

Closed
opened 2019-09-12 18:42:24 +02:00 by Dimitar P. · 20 comments

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: AMD Radeon (TM) Pro WX 7100 Graphics ATI Technologies Inc. 4.5.13559 Core Profile Context FireGL 26.20.11018.6

Blender Version
Broken: version: 2.81 (sub 10), branch: master, commit date: 2019-09-11 21:31, hash: 1e375ab5a1
Worked: (optional)

Short description of error
Sublayers do not remember their on/off state when a parent layer is turned off and then back on. Once the parent layer is on, all sublayers are turned on as well. Instead, the sublayers should remember their state irrelevant of whether the parent layer is on or off

Exact steps for others to reproduce the error

  • Create a collection
  • Create a number of sub-collections
  • Turn some sub-collections off
  • Turn off parent collection
  • Turn the parent collection back on
  • All the sub-collections are now on, instead of remembering their previous on/off state
**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: AMD Radeon (TM) Pro WX 7100 Graphics ATI Technologies Inc. 4.5.13559 Core Profile Context FireGL 26.20.11018.6 **Blender Version** Broken: version: 2.81 (sub 10), branch: master, commit date: 2019-09-11 21:31, hash: `1e375ab5a1` Worked: (optional) **Short description of error** Sublayers do not remember their on/off state when a parent layer is turned off and then back on. Once the parent layer is on, all sublayers are turned on as well. Instead, the sublayers should remember their state irrelevant of whether the parent layer is on or off **Exact steps for others to reproduce the error** - Create a collection - Create a number of sub-collections - Turn some sub-collections off - Turn off parent collection - Turn the parent collection back on - All the sub-collections are now on, instead of remembering their previous on/off state
Author

Added subscriber: @Dimitar

Added subscriber: @Dimitar

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2019-09-13 09:17:51 +02:00

This behavior is by design for this setting, to make it possible to enable sub-collections without their parents.

This behavior is by design for this setting, to make it possible to enable sub-collections without their parents.
Author

If it's needed for turning on sub-layers it could work in the following way:

  1. turn off main layer
  2. sub-layers get all switched on
  3. turn on sublayer
  4. turn on main layer
  5. sublayers recall initial state prior to setup 1

Otherwise I am struggling with the worlflow. How would one toggle visibility of a top level layer in a complex project with multiple sublayers of it's by design?

For example if I am working on an architecture project with a series of buildings:

  • plot 1
    • building 1.1
      • shell
      • interiors
    • building 1.2
      • shell
      • interiors
    • landscape
    • retail
  • plot 2
    • building 2.1
      • shell
      • interiors
    • building 2.2
      • shell
      • interiors
    • landscape
    • retail
  • plot 3
    • building 3.1
      • shell
      • interiors
    • building 3.2
      • shell
      • interiors
    • landscape
    • retail

If I turn off shell on building 1.1 and on building 1.2 and then I turn off plot 1 because it's in my way to focus on plot 2. When I turn on plot 1, I would have to go in and turn off layers for building shell so I can focus on the interiors. I would have to spend time of going through the UI and adjust again which layers are visible and which aren't. This is still a simple example that can get much more complex with sublayers

This behavior works as anticipated in other programs. The alternative is to hide instead of turning off, but I see that as a much more temporary way which can too easily and accidentally be reset with alt+h.

If it's needed for turning on sub-layers it could work in the following way: 1. turn off main layer 2. sub-layers get all switched on 3. turn on sublayer 4. turn on main layer 5. sublayers recall initial state prior to setup 1 Otherwise I am struggling with the worlflow. How would one toggle visibility of a top level layer in a complex project with multiple sublayers of it's by design? For example if I am working on an architecture project with a series of buildings: - plot 1 - building 1.1 - shell - interiors - building 1.2 - shell - interiors - landscape - retail - plot 2 - building 2.1 - shell - interiors - building 2.2 - shell - interiors - landscape - retail - plot 3 - building 3.1 - shell - interiors - building 3.2 - shell - interiors - landscape - retail If I turn off shell on building 1.1 and on building 1.2 and then I turn off plot 1 because it's in my way to focus on plot 2. When I turn on plot 1, I would have to go in and turn off layers for building shell so I can focus on the interiors. I would have to spend time of going through the UI and adjust again which layers are visible and which aren't. This is still a simple example that can get much more complex with sublayers This behavior works as anticipated in other programs. The alternative is to hide instead of turning off, but I see that as a much more temporary way which can too easily and accidentally be reset with alt+h.

Added subscriber: @horusscope

Added subscriber: @horusscope

That's a cruel and thoughtless design.
"Never save settings"

That's a cruel and thoughtless design. "Never save settings"

Added subscriber: @ZsoltStefan

Added subscriber: @ZsoltStefan

Ouch, that is bad. I thought it was a bug myself, just never got around to reporting it. Of course I would expect Blender to remember which collections are on or off, especially if I carefully set up my layers in a large scene.
I didn't know that it was possible to turn on sublayers without the parent, that's interesting. Seems like an override. But IMHO it shouldn't destroy the expected behaviour of "saving settings".

Thankfully there is a workaround, you can use the "Screen" filters ("globally disable in viewports.")

EDIT: I have to revise my comment. Using the screen filter is no replacement, as it disables the collections in every view layer, not just the current one.

Also, I was just working on a larger scene where this behaviour was really frustrating. I have several view layers, all of them set up carefully to show exactly the collections, subcollections and objects that I need. So then I turn a collection off and on, and it unhides every object, so that I have to go through the long list and reset the visibility filters. Certainly a bug.

Ouch, that is bad. I thought it was a bug myself, just never got around to reporting it. Of course I would expect Blender to remember which collections are on or off, especially if I carefully set up my layers in a large scene. I didn't know that it was possible to turn on sublayers without the parent, that's interesting. Seems like an override. But IMHO it shouldn't destroy the expected behaviour of "saving settings". Thankfully there is a workaround, you can use the "Screen" filters ("globally disable in viewports.") EDIT: I have to revise my comment. Using the screen filter is no replacement, as it disables the collections in every view layer, not just the current one. Also, I was just working on a larger scene where this behaviour was **really** frustrating. I have several view layers, all of them set up carefully to show exactly the collections, subcollections and objects that I need. So then I turn a collection off and on, and it unhides every object, so that I have to go through the long list and reset the visibility filters. Certainly a bug.
Author

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Author

Ok, sorry for reopening this, but I insist that this is a bug.

To add to what has been previously mentioned, when turning on and off sublayers, all objects inside a layer get their hidden/unhidden-in-viewport setting reset.

Layers and sublayers should remember their state as mentioned above.

Also, hidden-in-viewport properties for layers/objects should remember their state as they seem to do for whether objects get rendered or not. Here is a GIF demonstrating the issue:

outlinerbug.gif

Edit: created a seperate bug report for this issue.

Also created a topic on devtalk

Ok, sorry for reopening this, but I insist that this is a bug. To add to what has been previously mentioned, when turning on and off sublayers, all objects inside a layer get their hidden/unhidden-in-viewport setting reset. Layers and sublayers should remember their state as mentioned above. Also, hidden-in-viewport properties for layers/objects should remember their state as they seem to do for whether objects get rendered or not. Here is a GIF demonstrating the issue: ![outlinerbug.gif](https://archive.blender.org/developer/F7758733/outlinerbug.gif) Edit: created a [seperate bug report ](https://developer.blender.org/T70164) for this issue. Also created a [topic ](https://devtalk.blender.org/t/outliner-objects-collections-visibility-paper-cuts/9706/) on devtalk
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Member

Closing this because of the new bug report (#70164).

Closing this because of the new bug report (#70164).

Added subscriber: @YegorSmirnov

Added subscriber: @YegorSmirnov

@JacquesLucke Please reopen the task. You closed it because of #70164, but that one is claimed as incorrect (which is arguable) and closed. But this task is 100% correct and needs a lot of attention, as the current behavior will break your complex scene to the ground.

@JacquesLucke Please reopen the task. You closed it because of #70164, but that one is claimed as incorrect (which is arguable) and closed. But this task is 100% correct and needs a lot of attention, as the current behavior will break your complex scene to the ground.
Member

@YegorSmirnov, I will not reopen this myself because it has been closed by multiple devs who worked on this area. If it is very important, please consider bringing this topic up in blender.chat and/or talk to the ui team members directly.

@YegorSmirnov, I will not reopen this myself because it has been closed by multiple devs who worked on this area. If it is very important, please consider bringing this topic up in blender.chat and/or talk to the ui team members directly.

Added subscriber: @1D_Inc

Added subscriber: @1D_Inc

In #69812#831009, @JacquesLucke wrote:
If it is very important

This is, actually, one of the reasons our company banned 2.8x for production cycle.
Using scene setup management system that loses actual setup is like using a filesystem that loses files.
This is a bit unacceptable for business.

> In #69812#831009, @JacquesLucke wrote: > If it is very important This is, actually, one of the reasons our company banned 2.8x for production cycle. Using scene setup management system that loses actual setup is like using a filesystem that loses files. This is a bit unacceptable for business.
Author
Ok, conversation continued on the devtalk forum: https://devtalk.blender.org/t/outliner-objects-collections-visibility-paper-cuts/9706/7?u=dimitar
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
7 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#69812
No description provided.