Geometry Nodes: Simulation are losing material of geometry #108178
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#108178
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: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits, X11 UI
Graphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07
Blender Version
Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-05-22 09:38, hash:
2decfe4f002aWorked: (newest version of Blender that worked as expected)
Short description of error
Exact steps for others to reproduce the error
Example file:
simulation_nodes_losing_material.blend
Geometry Nodes: Losing material in Cycles F12 renderto Geometry Nodes: Simulation are losing material of geometryAlready confirmed this with @JacquesLucke
The bug right now is that it is inconsistent. Currently, simulations are not expected to propagate materials, but that's not a fundamental limitation. Will look into solving that later this week.
Can we close this report? Now the behavior is consistent in viewport and final render. And also there is design task for material support with simulation nodes (#108410) so I think we don't need another task to track it.
Feel free to reopen though :)
Thank you for adding
Simulation nodes loosing materials #109556
Looks like the problem has been solved :
[Pratik Borhade] added Status Resolved
Will the version of Blender correcting the problem be published on this thread later on ?
(just hoping for a 3.6.1 rather than 4.0)
This has been closed because the reported inconsistency has been resolved. Materials were "supported" for some cases but mostly by accident. They way it worked would break in many situations like when baking.
There is a design task for this topic: #108410.
I actually started working on this topic this week.
Thank you for this information. May be you have seen in #109556 that I try to use simulation node for architecture in a static way as a substitute for "pseudo loops", and not for animation. This kind of use does not require baking or cache.
Would it be acceptable to not remove materials when baking and cache are not used ?
Unfortunately, not really as that would also require keeping around potentially dangling pointers to materials. For 3.6 I you will have to rely on workarounds for this unfortunately. (set the materials after the simulation)