Geometry Nodes: Dual Mesh Node doesn't handle materials #93663
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#93663
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: Windows 10
Graphics card: RTX 3070
Blender Version
3.1 Alpha
Short description of error
The mesh created with the dual mesh node doesn't have default material slots, and doesn't transfer materials. This causes things like the 'set material' node to not work properly.
Exact steps for others to reproduce the error
2021-12-06 13-21-38.mp4
Muting the dual mesh in the given node tree works as expected. The set material node only works properly after assigning a default material to all the faces. The selection itself is being created correctly on the mesh (checked via the viewer).
dual_mesh_index.blend
Added subscriber: @Sanctus
Added subscriber: @wannes.malfait
Changed status from 'Needs Triage' to: 'Confirmed'
Assigning materials in geometry nodes to the mesh from dual mesh seems to broken.
Geometry Nodes Dual Mesh Node strange behavior with Indexto Geometry Nodes: Dual Mesh Node doesn't handle materialsAdded subscriber: @HooglyBoogly
@wannes.malfait, I believe part of this problem is because
BKE_mesh_new_nomain
is used instead ofBKE_mesh_new_nomain_from_template
, which copies the materials/slots.Another is probably that face attributes are transferred to vertices, but that isn't possible with material indices. I guess there's probably some way to transfer face attributes to new faces? Though maybe that exposes some arbitrary decisions in the edge cases.
If
BKE_mesh_new_nomain_from_template
fixes the problem of not being able to assign materials correctly then I think just making that change should be good enough.There is no "good" way to copy material indices like you said. I don't think it's possible to to any better than if you used the
Set Material Index
node with the to point domain convertedMaterial Index
attribute. Since it's possible to do this with the current node, I don't think it's worth the added effort and complexity to add this to the node itself. I think in general you would want to assign materials after all the geometry processing is done anyway.That makes sense, thanks. I guess we can just do the first fix then.
Changed status from 'Confirmed' to: 'Resolved'
This bug seems to actually not be present anymore in latest master, so I'll just close this as resolved.