Layers working bad - restriction toogles are not stored and reseting #104209

Closed
opened 2023-01-29 01:42:11 +01:00 by ManBlender · 9 comments

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

Blender Version
Broken: version: 3.4.0, branch: blender-v3.4-release, commit date: 2022-12-06 18:46, hash: a95bf1ac01
Worked: (newest version of Blender that worked as expected)

Short description of error
When creating new layers and selecting/deselecting restriction toggles, then after change layer restriction toogles are not stored and resetting (especially disable in viewport, render, hide in viewport is more often stored).

Exact steps for others to reproduce the error
I'm working with many collections, and trying manage many layers, creating new, etc.
On test I just have problem with 3 layers, but around 20 collections.
Each switch between Layer 1 and change settings, then Layer 2 or 3 have changed disable in viewport, render but not hide in viewport.
Again fix around Layer 2 or 3 back to Layer 1 ang changes here, then again Layer 2 or 3 are broken.
The behavior is unexpected.

**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.41 **Blender Version** Broken: version: 3.4.0, branch: blender-v3.4-release, commit date: 2022-12-06 18:46, hash: `a95bf1ac01` Worked: (newest version of Blender that worked as expected) **Short description of error** When creating new layers and selecting/deselecting restriction toggles, then after change layer restriction toogles are not stored and resetting (especially disable in viewport, render, hide in viewport is more often stored). **Exact steps for others to reproduce the error** I'm working with many collections, and trying manage many layers, creating new, etc. On test I just have problem with 3 layers, but around 20 collections. Each switch between Layer 1 and change settings, then Layer 2 or 3 have changed disable in viewport, render but not hide in viewport. Again fix around Layer 2 or 3 back to Layer 1 ang changes here, then again Layer 2 or 3 are broken. The behavior is unexpected.
Author

Added subscriber: @ManBlender

Added subscriber: @ManBlender
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

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

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

Hi, are you referring to particular restriction toggle property here?
Perhaps #87111 (Objects do not retain View State when turning Collections Off then back On)

Hi, are you referring to particular restriction toggle property here? Perhaps #87111 (Objects do not retain View State when turning Collections Off then back On)
Author

Yes, looks similar issue nut I experience more wide problems around as no control around this all states.

Yes, looks similar issue nut I experience more wide problems around as no control around this all states.
Member

Could you specify those problem more precisely in report?
Provided steps in the description are not very clear to me.

Could you specify those problem more precisely in report? Provided steps in the description are not very clear to me.
Author

Let we say.. that have car, and many variations like sport, classic and related stuff around as parts to hide or show in each layer.
When adding manipulate this in version sport, eg. rims related to this version, then collection tirrs is hidden in case I not touched this on classic.
Then fixing on classic this tires and on sport something other is hidden in case I not touched this, not modified, etc. and again.. fixing here eg. mirrors version in classic, and on sport discovering other changes.

It's hard to explain coz I not understanding the why this happening, what is case for this relations.
I adding file where this can be observed. It was possible to repeat the behavior in some examples - I adding video.
https://recordit.co/vykJxyBNCp

layer_test.blend

Let we say.. that have car, and many variations like sport, classic and related stuff around as parts to hide or show in each layer. When adding manipulate this in version sport, eg. rims related to this version, then collection tirrs is hidden in case I not touched this on classic. Then fixing on classic this tires and on sport something other is hidden in case I not touched this, not modified, etc. and again.. fixing here eg. mirrors version in classic, and on sport discovering other changes. It's hard to explain coz I not understanding the why this happening, what is case for this relations. I adding file where this can be observed. It was possible to repeat the behavior in some examples - I adding video. https://recordit.co/vykJxyBNCp [layer_test.blend](https://archive.blender.org/developer/F14213357/layer_test.blend)
Member

Hi, I think I understood the issue you're explaining. This is not a bug though.
Hide in viewport is layer level property (individual for each object in each layer)
While other properties such as Disable in viewport, Disable in Renders are mapped to objects, their state is stored in object itself (that's why editing the toggle in one layer reflects the change in another layer).
Closing this report. Feel free to comment if there is misunderstanding from my side.

Hi, I think I understood the issue you're explaining. This is not a bug though. `Hide in viewport` is layer level property (individual for each object in each layer) While other properties such as `Disable in viewport`, `Disable in Renders` are mapped to objects, their state is stored in object itself (that's why editing the toggle in one layer reflects the change in another layer). Closing this report. Feel free to comment if there is misunderstanding from my side.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2023-02-16 14:33:58 +01:00
Author

The explanation have no sense in my opinion, coz then the Layer is not useful in this case to manage. And the properties can't be stored then in object (if now in this way is done) but in layer then, as related matrix for each object, or only if status is other as visible in array.
Worst.. as random case for this what is hidden or not after changes.

The explanation have no sense in my opinion, coz then the Layer is not useful in this case to manage. And the properties can't be stored then in object (if now in this way is done) but in layer then, as related matrix for each object, or only if status is other as visible in array. Worst.. as random case for this what is hidden or not after changes.
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#104209
No description provided.