Volume-type geometries always seem to use the object material while mesh primitives are unpredictable #113712

Closed
opened 2023-10-14 08:41:14 +02:00 by Artem-Shakhov · 4 comments

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68

Blender Version
Broken: version: 3.6.4, branch: blender-v3.6-release, commit date: 2023-09-25 13:24, hash: 21bfc5e7fe3f
Worked: (newest version of Blender that worked as expected)
I also have checked 4.0b, 4.1a and 3.5.1. It works the same over there.

Short description of error
Relinking object materials relinks geometry node material.
This error occurs with points, hair, converting curves to mesh, converting mesh to volume. This works correctly with procedural primitives.

Exact steps for others to reproduce the error

  • Open attached .blend file Relink_bug-simplified.blend - Note that each geometry uses the material that was set in GN
  • In Properties > Material, change the material Link to Object - Note that both generated geometries now use the material set to the object
  • Mute the Mesh to Volume node

The Icosphere has the material that we assigned inside the GN.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68 **Blender Version** Broken: version: 3.6.4, branch: blender-v3.6-release, commit date: 2023-09-25 13:24, hash: `21bfc5e7fe3f` Worked: (newest version of Blender that worked as expected) I also have checked 4.0b, 4.1a and 3.5.1. It works the same over there. **Short description of error** Relinking object materials relinks geometry node material. This error occurs with points, hair, converting curves to mesh, converting mesh to volume. This works correctly with procedural primitives. **Exact steps for others to reproduce the error** - Open attached .blend file [Relink_bug-simplified.blend](attachments/b586bdf0-7123-49d2-90cd-58a80b89bcd3) - Note that each geometry uses the material that was set in GN - In `Properties` > `Material`, change the material `Link` to `Object` - Note that both generated geometries now use the material set to the object - Mute the `Mesh to Volume` node The Icosphere has the material that we assigned inside the GN.
Artem-Shakhov added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2023-10-14 08:41:15 +02:00

Might be duplicate of #112372

Might be duplicate of https://projects.blender.org/blender/blender/issues/112372

I can confirm the problem.

It is similar to these others:
#112372: Set Material Index node does not work on some GN-created geometry
#98834: Broken material assigment after changing mesh-linking to object-linking
#99996: Replace object-linked materials feature
#93455: Set Material Node does not reuse existing empty slot
#105993: Applying geometry nodes modifier create an empty material slot for no reason
#85578: "Join Meshes" changes the material slot assigned to faces of the original mesh

However there is a peculiarity in the provided .blend file.
Volume-type geometry always seems to use the material set for object, while other geometry types can use any material.

I believe that, although probably related to some of the above, this issue has not been specifically reported before.
So I'll confirm (after editing the description a little).

I can confirm the problem. It is similar to these others: #112372: Set Material Index node does not work on some GN-created geometry #98834: Broken material assigment after changing mesh-linking to object-linking #99996: Replace object-linked materials feature #93455: Set Material Node does not reuse existing empty slot #105993: Applying geometry nodes modifier create an empty material slot for no reason #85578: "Join Meshes" changes the material slot assigned to faces of the original mesh However there is a peculiarity in the provided .blend file. Volume-type geometry always seems to use the material set for object, while other geometry types can use any material. I believe that, although probably related to some of the above, this issue has not been specifically reported before. So I'll confirm (after editing the description a little).
Germano Cavalcante changed title from GN: Relinking object materials relinks GN material to Volume-type geometries always seem to use the object material rather than that set by geometry nodes 2023-10-16 17:36:36 +02:00
Germano Cavalcante changed title from Volume-type geometries always seem to use the object material rather than that set by geometry nodes to Volume-type geometries always seem to use the object material while mesh primitives are unpredictable 2023-10-16 17:42:34 +02:00
Author

Thanks for your work. This is my first bug report. And such a quick response. I am delighted. It's so hard to find an undocumented bug. I will consider that I succeeded. So now I have a small personal achievement. You are doing a great job. For me, the blender command is the command that I constantly cite as an example when I talk about bugs in any other software. If it is inappropriate to write such things here, please delete this message and I will draw conclusions. Thanks again!

Thanks for your work. This is my first bug report. And such a quick response. I am delighted. It's so hard to find an undocumented bug. I will consider that I succeeded. So now I have a small personal achievement. You are doing a great job. For me, the blender command is the command that I constantly cite as an example when I talk about bugs in any other software. If it is inappropriate to write such things here, please delete this message and I will draw conclusions. Thanks again!
Member

I fear this is the same issue as in many other similar cases. Geometry nodes does not make guarantees about specific material indices (see material_index attribute). It only guarantees that materials attached to some geometry will stay there, but the underlying material index may change fairly arbitrarily. By using the (somewhat legacy) object material overwriting feature, you are making assumptions about specific material indices which leads to seemingly unexpected behavior.

It's planned to replace the material overwrite feature with something that works better with procedural effects (#99996).

I fear this is the same issue as in many other similar cases. Geometry nodes does *not* make guarantees about specific material indices (see `material_index` attribute). It only guarantees that materials attached to some geometry will stay there, but the underlying material index may change fairly arbitrarily. By using the (somewhat legacy) object material overwriting feature, you are making assumptions about specific material indices which leads to seemingly unexpected behavior. It's planned to replace the material overwrite feature with something that works better with procedural effects (#99996).
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2024-03-02 23:45:12 +01:00
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
4 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#113712
No description provided.