Turning collections off and then back on resets the viewport visibility behavior of objects #70164

New Issue

Dimitar P. · 2019-09-22T17:57:57+02:00

Dimitar P. commented

2019-09-22 17:57:57 +02:00

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 25.20.100.6581

Blender Version
Broken: version: 2.81 (sub 12), branch: master, commit date: 2019-09-22 11:16, hash: 22a478e5ee
Worked: version 2.79

Short description of error
objectVisibility_bugReport.blend
When turning a collection off and there are objects inside of the collection hidden in the viewport, when the collection is turned back on, all objects are reset to visible in the viewport.

GIF demonstrating the issue:

Hidden-in-viewport properties for layers/objects should remember their state as they seem to do for whether objects get rendered or not.

Related to this: #69812 (Sub-collections on/off state not remembered if parent collection is switched off and then on)

Also conversation on devtalk: https://devtalk.blender.org/t/outliner-objects-collections-visibility-paper-cuts/9706

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 25.20.100.6581 **Blender Version** Broken: version: 2.81 (sub 12), branch: master, commit date: 2019-09-22 11:16, hash: `22a478e5ee` Worked: version 2.79 **Short description of error** [objectVisibility_bugReport.blend](https://archive.blender.org/developer/F7777529/objectVisibility_bugReport.blend) When turning a collection off and there are objects inside of the collection hidden in the viewport, when the collection is turned back on, all objects are reset to visible in the viewport. GIF demonstrating the issue: ![outlinerbug.gif](https://archive.blender.org/developer/F7758733/outlinerbug.gif) Hidden-in-viewport properties for layers/objects should remember their state as they seem to do for whether objects get rendered or not. Related to this: #69812 (Sub-collections on/off state not remembered if parent collection is switched off and then on) **Also conversation on devtalk: https://devtalk.blender.org/t/outliner-objects-collections-visibility-paper-cuts/9706**

Dimitar P. commented

2019-09-22 17:57:57 +02:00

Added subscriber: @Dimitar

blender-admin commented

2019-09-22 17:57:57 +02:00

#70307 was marked as duplicate of this issue

Germano Cavalcante commented

2019-09-30 20:07:02 +02:00

Added subscribers: @dfelinto, @mano-wii

Dalai Felinto was assigned by Germano Cavalcante

2019-09-30 20:07:02 +02:00

Germano Cavalcante commented

2019-09-30 20:07:02 +02:00

@dfelinto, is this a known limitation or does it work as intended?

Germano Cavalcante commented

2019-09-30 20:55:14 +02:00

Added subscriber: @carliel

Dimitar P. commented

2019-10-01 10:09:30 +02:00

In #70164#786595, @mano-wii wrote:
@dfelinto, is this a known limitation or does it work as intended?

I hope it hasn't been implemented correctly yet, as this wasn't the default behavior in blender 2.7. E.g. when having hidden objects on a layer in 2.7, and then turning that layer off, and then back on, the objects remain hidden.

The current behavior makes it very difficult to work with many collection layers, where i am constantly switching some on and off, as all the hidden-in-the viewport properties get reset.

In this case I am forced to create seperate sub-collections to house construction geometry. Yet as mentioned in #69812 (Sub-collections on/off state not remembered if parent collection is switched off and then on), sub-collections get reset to on state as well when parented to collection that is turned off and then back on.

I propose that for both collections/sub-collections on/off behavior and viewport visibility when collections are turned on and off work by remembering their states, similarly to the way that they remember their render on/off property.

A possible way to solve these issues is to create a state to remember the settings prior to executing the operators to turn on/off and show/hide

turn off main collection
sub-collections get all switched on
turn on sub-collection
turn on main layer
sub-collections and/or hidden/visible objects recall initial state prior to step 1

> In #70164#786595, @mano-wii wrote: > @dfelinto, is this a known limitation or does it work as intended? I hope it hasn't been implemented correctly yet, as this wasn't the default behavior in blender 2.7. E.g. when having hidden objects on a layer in 2.7, and then turning that layer off, and then back on, the objects remain hidden. The current behavior makes it very difficult to work with many collection layers, where i am constantly switching some on and off, as all the hidden-in-the viewport properties get reset. In this case I am forced to create seperate sub-collections to house construction geometry. Yet as mentioned in #69812 (Sub-collections on/off state not remembered if parent collection is switched off and then on), sub-collections get reset to on state as well when parented to collection that is turned off and then back on. I propose that for both collections/sub-collections on/off behavior and viewport visibility when collections are turned on and off work by remembering their states, similarly to the way that they remember their render on/off property. A possible way to solve these issues is to create a state to remember the settings prior to executing the operators to turn on/off and show/hide - turn off main collection - sub-collections get all switched on - turn on sub-collection - turn on main layer - sub-collections and/or hidden/visible objects recall initial state prior to step 1

Dalai Felinto commented

2019-10-01 17:04:48 +02:00

Changed status from 'Open' to: 'Archived'

Dalai Felinto closed this issue

2019-10-01 17:04:48 +02:00

Dalai Felinto commented

2019-10-01 17:04:48 +02:00

Hi, thanks for the report. It is working as expecting though. Right now if you want a permanent on/off visibility you need to turn off their global viewport visibility (the screen icon).

Dalai Felinto commented

2019-10-01 17:05:26 +02:00

Added subscriber: @brecht

Dalai Felinto commented

2019-10-01 17:05:26 +02:00

Poking @brecht in case he thinks otherwise

Paul Kotelevets commented

2019-11-20 00:22:53 +01:00

Added subscriber: @1D_Inc

Paul Kotelevets commented

2019-11-20 00:22:53 +01:00

Well, it seems to be Collection system design issue.
In short - it is too easy to lose current scene setup.
Almost any action with collections leads to that.
We are currently trying to generalize such issues.

Well, it seems to be Collection system design issue. In short - it is too easy to lose current scene setup. Almost any action with collections leads to that. We are currently trying to generalize such issues.

Dimitar P. commented

2019-12-17 13:19:34 +01:00

I am wondering if there are any updated thoughts in this bug? Whether I should re-open it or make a new report? In my mind, it is still i a bug because turning a collection off and then back on looses the visibility settings of the scene. It makes it rather difficult to work with turning collections on and off.

Poking @dfelinto and @1D_Inc

I am wondering if there are any updated thoughts in this bug? Whether I should re-open it or make a new report? In my mind, it is still i a bug because turning a collection off and then back on looses the visibility settings of the scene. It makes it rather difficult to work with turning collections on and off. Poking @dfelinto and @1D_Inc

Paul Kotelevets commented

2019-12-17 23:34:25 +01:00

In #70164#830274, @Dimitar wrote:
I am wondering if there are any updated thoughts in this bug? Whether I should re-open it or make a new report? In my mind, it is still i a bug because turning a collection off and then back on looses the visibility settings of the scene. It makes it rather difficult to work with turning collections on and off.

Poking @dfelinto and @1D_Inc

All related issues are united by paragraph
"Obtaining the actual setup is the goal of a collection management system.
Currently, it is too easy to lose the actual setup, since almost every collection operation is irreversible, and almost any action with collections leads to losing actual setup."

Yes, a lot of our users faced with this issue. The problem is this is not a software bug, but a workflow (design) issue.
We made an alpha version of proposal regarding content management systems.

> In #70164#830274, @Dimitar wrote: > I am wondering if there are any updated thoughts in this bug? Whether I should re-open it or make a new report? In my mind, it is still i a bug because turning a collection off and then back on looses the visibility settings of the scene. It makes it rather difficult to work with turning collections on and off. > > Poking @dfelinto and @1D_Inc All related issues are united by paragraph "Obtaining the actual setup is the goal of a collection management system. Currently, it is too easy to lose the actual setup, since almost every collection operation is irreversible, and almost any action with collections leads to losing actual setup." Yes, a lot of our users faced with this issue. The problem is this is not a software bug, but a workflow (design) issue. We made an alpha version of proposal regarding content management systems.

Dimitar P. commented

2019-12-19 16:41:05 +01:00

Ok, so with this behaviour i slightly understand what's happened. The hidden icon is second and meant only for very temporary situations whereas the disable in viewport icon has taken up the usage that we were used to in 2.7. That's fine, it takes a little bit of getting used to but it's fine. Not as much a dealbreaker as #69812 (Sub-collections on/off state not remembered if parent collection is switched off and then on).

Paul Kotelevets commented

2019-12-19 22:12:04 +01:00

They are the same, actually.
But this one contains both cases - loosing setup of nesting collections and objects visibility.

They are the same, actually. But this one contains both cases - loosing setup of nesting collections and objects visibility.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Turning collections off and then back on resets the viewport visibility behavior of objects #70164