Geometry Nodes, modifiers after GN removes material #85893

Closed
opened 2021-02-22 18:17:07 +01:00 by Gurra · 8 comments

System Information
Operating system: Windows 10
Graphics card: RTX 3060ti

Blender Version
Broken: 2.93.0 Alpha 37e6a1995a

Short description of error
Exact steps for others to reproduce the error
When using geometry nodes to instance other objects on a surface and then add an array modifier for example after GN the instanced geometry gets the same material as the base surface. In 2.92 the array wont array the instances, but at least the material stays the same.
Also when making this example scene some of the instances got some weird shading when enabling that array modifier. Not really part of the bug report, but still something to look into maybe? :)
geometyrynodematerialbug2.jpg
geometyrynodematerialbug1.jpg
geometyrynodematerialbug.blend

**System Information** Operating system: Windows 10 Graphics card: RTX 3060ti **Blender Version** Broken: 2.93.0 Alpha 37e6a1995ac7 **Short description of error** **Exact steps for others to reproduce the error** When using geometry nodes to instance other objects on a surface and then add an array modifier for example after GN the instanced geometry gets the same material as the base surface. In 2.92 the array wont array the instances, but at least the material stays the same. Also when making this example scene some of the instances got some weird shading when enabling that array modifier. Not really part of the bug report, but still something to look into maybe? :) ![geometyrynodematerialbug2.jpg](https://archive.blender.org/developer/F9827982/geometyrynodematerialbug2.jpg) ![geometyrynodematerialbug1.jpg](https://archive.blender.org/developer/F9827967/geometyrynodematerialbug1.jpg) [geometyrynodematerialbug.blend](https://archive.blender.org/developer/F9827969/geometyrynodematerialbug.blend)
Author

Added subscriber: @Gurra

Added subscriber: @Gurra
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Thanks for the report. Looking into the file, for now this is expected. In order for the array modifier to work, the instances created by the point instance node must be converted into one mesh, and the code that combines all of the instances just doesn't combine the materials yet.

A workaround for now is to add all the materials on the final object and use the material_index attribute to control which to use.

It's possible, but we haven't focused on this use case yet. I will leave this as a known issue so we have a reminder.

Thanks for the report. Looking into the file, for now this is expected. In order for the array modifier to work, the instances created by the point instance node must be converted into one mesh, and the code that combines all of the instances just doesn't combine the materials yet. A workaround for now is to add all the materials on the final object and use the `material_index` attribute to control which to use. It's possible, but we haven't focused on this use case yet. I will leave this as a known issue so we have a reminder.
Author

Yupp, good to know, thanks!
And might be good for you to know for whenever you might fix this; tried out that material_index thing and it seems to work, except that when enabling a modifier after the geonode will remove all UV-maps. So in practice it's not really viable work around either. So I'll just have to wait :) Thanks again!

Yupp, good to know, thanks! And might be good for you to know for whenever you might fix this; tried out that material_index thing and it seems to work, except that when enabling a modifier after the geonode will remove all UV-maps. So in practice it's not really viable work around either. So I'll just have to wait :) Thanks again!

Added subscriber: @randum

Added subscriber: @randum
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Hans Goudey self-assigned this 2021-07-06 05:41:41 +02:00
Member

This has basically been resolved for 3.0 with the material assign node and the other material nodes.

This has basically been resolved for 3.0 with the material assign node and the other material nodes.
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#85893
No description provided.