The Set material node messes up collection visibility in the geometry nodes graph #114681
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#114681
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: Win 11
Graphics card: RTX 2070
Blender Version
Broken:
368b38be37Short description of error
Certain nodes makes the node graph to make disabled collections items visible. See the attached video for what is happening.
Exact steps for others to reproduce the error
load the attach .blend
move the set material node on the node graph as seen in the video
Set material messes up collection visibility in the geometry nodes graphto Th Set material node messes up collection visibility in the geometry nodes graphTh Set material node messes up collection visibility in the geometry nodes graphto The Set material node messes up collection visibility in the geometry nodes graphI'll check this tomorrow/
I tried to test the attached scene in 3.5, 3,4 and the other 3x series but it is crashing those versions. I recreated a similar scene and this issue seems to be in 3.1 as well. It does not even respect any of the object visibility flags let alone the collection visibility.
I attached the Blender 3.1 version of the scene for testing
I see just inconsistency. If collection visibility is not matter, geometry nodes should display output instanced objects. In other case, objects visibility should be keeped in
for_each_instaces.I personally think that this is a bug given, the geometry nodes setup originally respects the collection or the object visibility until one attaches the set material node.
Any word on why this breaks the object visibility? As a user this is a pretty sucky one because the workarounds for this are quite ugly and definitely production pipeline buster.
Hm, could be solved by replacing
FOREACH_COLLECTION_OBJECT_RECURSIVE_BEGINwith something that does more visibility checks ingeometry_set_instances.ccandrealize_instances.cc. It's not super obvious to me right now under which circumstances which visibility flags should be used. Like we want to be able to instance the top-level collection if though it's disabled, but not the nested collection which is also "just" disabled.Will add this as a meeting topic for our module meeting.
If I remember right, none of the visibility flags made a difference as far as not being visible after a material node is added. In theory if a collection is excluded from the viewlayer via the checkbox, it should be disabled in the instancing given that flag also disables the collection from renders and render layers. Geometry Nodes should respect the visibility hierarchy. This type of setup can be used to enhance the renderlayers as well so it is crucial that there is no visibility logic discrepancy across the parts of Blender.