Restriction Toggle Settings Are Not Unique To View Layers and Are Lost When Switching #72084

Closed
opened 2019-12-01 08:30:19 +01:00 by Ryan Inch · 12 comments
Member

System Information
Operating system: Linux-5.3.13-arch1-1-x86_64-with-arch 64 Bits
Graphics card: GeForce GTX 660M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.36

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: 26bd5ebd42

Short description of error
If you set Restriction Toggles in View Layer 1, switch from View Layer 1 to View Layer 2, make changes to Restriction Toggles in View Layer 2, and switch back to View Layer 1, your settings for View Layer 1 are now lost.

Exact steps for others to reproduce the error
Create a new Collection beside your initial one.
Show all Restriction Toggles.
Take note of what Restriction Toggles are enabled
Create a new View Layer.
Set all Restriction Toggles to off for the new collection.
Switch Back to the first View Layer.
Restriction Toggles are not the same as when you left.

**System Information** Operating system: Linux-5.3.13-arch1-1-x86_64-with-arch 64 Bits Graphics card: GeForce GTX 660M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.36 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: `26bd5ebd42` **Short description of error** If you set Restriction Toggles in View Layer 1, switch from View Layer 1 to View Layer 2, make changes to Restriction Toggles in View Layer 2, and switch back to View Layer 1, your settings for View Layer 1 are now lost. **Exact steps for others to reproduce the error** Create a new Collection beside your initial one. Show all Restriction Toggles. Take note of what Restriction Toggles are enabled Create a new View Layer. Set all Restriction Toggles to off for the new collection. Switch Back to the first View Layer. Restriction Toggles are not the same as when you left.
Author
Member

Added subscriber: @Imaginer

Added subscriber: @Imaginer

Added subscriber: @rjg

Added subscriber: @rjg

I can imagine that this would be a useful feature, but this is not a bug. The visibility state is tied to the object or collection, not the view layer.

I can imagine that this would be a useful feature, but this is not a bug. The visibility state is tied to the object or collection, not the view layer.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Robert Guetzkow self-assigned this 2019-12-01 14:09:49 +01:00

While this change could be a very useful feature in the future, it would also impact several parts of Blender's code, including the Python API. Therefore this is something that needs to be discussed, properly designed and approved by module owners.

I would suggest posting about this feature on [right-click select ]] to get feedback from other users and discussing it with the developers on [ https:*devtalk.blender.org/c/blender | DevTalk , if you want to be involved in the (potential) development.

I'll be closing this ticket because it's a feature request.

While this change could be a very useful feature in the future, it would also impact several parts of Blender's code, including the Python API. Therefore this is something that needs to be discussed, properly designed and approved by module owners. I would suggest posting about this feature on [right-click select ]] to get feedback from other users and discussing it with the developers on [[ https:*devtalk.blender.org/c/blender | DevTalk ](https:*blender.community/c/rightclickselect), if you want to be involved in the (potential) development. I'll be closing this ticket because it's a feature request.
Author
Member

Fine, while I still regard this as a bug, I can see how it would be better to be designed with and approved by module owners. But even though the current behavior is expected by developers, it is not clear to the user what to expect. Could the tooltips at least be made more consistent so that the user has a better idea what is View Layer specific and what is global across all View Layers?

Fine, while I still regard this as a bug, I can see how it would be better to be designed with and approved by module owners. But even though the current behavior is expected by developers, it is not clear to the user what to expect. Could the tooltips at least be made more consistent so that the user has a better idea what is View Layer specific and what is global across all View Layers?

@Imaginer Sure I don't see why not. You can submit a diff if you already have suggestions how a better description should look like. Although I think the tooltips are currently quite clear that they are applied globally. For example:

Disable in Viewports.
Globally disable in viewports.
*Shift to set children

Disable in Renders.
Globally disable in renders.
*Shift to set children

@Imaginer Sure I don't see why not. You can submit a diff if you already have suggestions how a better description should look like. Although I think the tooltips are currently quite clear that they are applied globally. For example: > Disable in Viewports. > Globally disable in viewports. > *Shift to set children > Disable in Renders. > Globally disable in renders. > *Shift to set children
Author
Member

@rjg Those ones are alright, but a couple of the other ones could use improvement. For example:

Hide in Viewport.
Temporarily Hide in Viewport.

(This is View Layer specific)

Disable Selection.
Disable selection in viewport.

(This is Collection specific)

Both of these are worded very similarly, but one affects the View Layer and the other the Collection.

And the one for show_restrict_column_select is just:

Selectable.
Selectable.

I'll submit a diff with hopefully, clearer wording.

@rjg Those ones are alright, but a couple of the other ones could use improvement. For example: > Hide in Viewport. > Temporarily Hide in Viewport. (This is View Layer specific) > Disable Selection. > Disable selection in viewport. (This is Collection specific) Both of these are worded very similarly, but one affects the View Layer and the other the Collection. And the one for show_restrict_column_select is just: > Selectable. > Selectable. I'll submit a diff with hopefully, clearer wording.

@Imaginer Thank you!

@Imaginer Thank you!
Author
Member

@rjg Here's the diff: D6364.

@rjg Here's the diff: [D6364](https://archive.blender.org/developer/D6364).

Added subscriber: @1D_Inc

Added subscriber: @1D_Inc

Well, we has got a scene setup saving system, that doesnot even saves some scene setups.

Well, we has got a scene setup saving system, that doesnot even saves some scene setups.
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
3 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#72084
No description provided.