Edit Mode: Color Attribute node in Shader Tree ignores data passed from Geometry Nodes #62
Assignees
Triager-bot
Clear assignees
Triager-bot
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Triager-bot/blender-bug-reports#62
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Original bug report: https://projects.blender.org/blender/blender/issues/157252
System Information
Operating system: Windows 10 22H2
Graphics card: NVIDIA GeForce RTX 2080, 581.57
Blender Version
Worked: 4.2.19 LTS, 4.5.8 LTS
Broken: 5.1.0
Short description of error
Attributes passed from Geometry Nodes to drive shader parameters (via the Color Attribute node) are not applied in Edit Mode. In Object Mode, the shader is controlled correctly.
Blender 4.5.8 - object & edit mode
Blender 5.1.0 - object & edit mode
Report is clear
LLM Reasoning
Got it, let's see. The bug report has a clear title, describes the issue (Color Attribute node in Edit Mode ignoring Geometry Nodes data), compares Object vs Edit mode, includes images for both versions (4.5.8 and 5.1.0). The steps to reproduce are implied by showing the difference between modes. So the description is clear. So the answer should be Yes.
JSON Data
{
"llm_judgement": true,
"processing_time": 6.307043999999999
}
Report is specific
LLM Reasoning
Got it, let's analyze this bug report. The title is "Edit Mode: Color Attribute node in Shader Tree ignores data passed from Geometry Nodes". The body describes a specific issue where the Color Attribute node doesn't apply attributes from Geometry Nodes in Edit Mode (but works in Object Mode). There are comparisons between Blender versions and mode-specific behavior, plus images showing the difference. So this is about a specific feature (Color Attribute node) in a specific context (Edit Mode vs Object Mode) with data flow from Geometry Nodes. That's a specific issue, not generic. So the answer should be 'Specific'.
JSON Data
{
"llm_judgement": true,
"processing_time": 8.441375
}
Report flagged as duplicate by LLM
Blender 5.1: Attributes stored by a Geometry Nodes modifier are reflected in Object Mode, but are not reflected in Edit Mode even with "Display Modifier in Edit Mode" toggle enabled
https://projects.blender.org/blender/blender/issues/156552
System Information
Operating system: Windows-11-10.0.26200-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3090 NVIDIA Corporation NVIDIA 591.74 Vulkan Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Broken: 5.2
Worked: 5.0.1
Caused by 9a672cbe52
Short description of error
I am trying to store the Sun’s direction vector in Geometry Nodes and use it in the Shader Editor to calculate the dot product between that direction vector and the mesh normals. It works correctly in Object Mode, but in Edit Mode the effect is not reflected in the viewport even when “Display Modifier in Edit Mode” toggle is enabled. The same setup worked correctly in Blender 5.0.1. I tested it in Blender 5.1 and 5.2 alpha, and the issue occurs in both versions.
Exact steps for others to reproduce the error
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce.
Bug report 1: The issue is about the Color Attribute node in Shader Tree ignoring data from Geometry Nodes in Edit Mode, but working in Object Mode. The steps involve using a Color Attribute node with Geometry Nodes data, checking object vs edit mode.
Bug report 2: The issue is about attributes stored by Geometry Nodes not reflecting in Edit Mode even when "Display Modifier in Edit Mode" is enabled, while working in Object Mode. Steps include storing a vector (Sun direction) via Geometry Nodes, using it in Shader Editor for dot product, checking object vs edit mode with the toggle.
Both reports mention that in Object Mode, the attributes work correctly, but in Edit Mode they don't. The core problem seems to be the same: Geometry Nodes attributes not being applied in Edit Mode (even when display modifier is enabled) while working in Object Mode. The specific nodes or calculations might differ (Color Attribute vs dot product with normals), but the underlying issue of attributes from Geometry Nodes failing in Edit Mode is consistent.
So, are they duplicates? Let's check the key points: both have the same behavior (works in object mode, fails in edit mode) and involve Geometry Nodes passing data to shaders. The steps to reproduce also align in terms of checking object vs edit mode with modifiers enabled. So yes, they're the same issue.
JSON Data
{
"llm_judgement": true,
"processing_time": 19.392615,
"duplicate_report_number": "156552"
}
Report flagged as NOT a duplicate by LLM
Material node 'Color Attribute' does not find attribute if geometry nodes generate geometry other than Mesh
https://projects.blender.org/blender/blender/issues/117536
System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.33
Blender Version
Broken: versions: 3.6.x and 4.0.x
Worked: none
Short description of error
When we add color attributes to the output of Geometry Nodes, we can access these attributes in the Shader Editor.
However, if the geometry generated for the object is something other than
Mesh, theColor Attributenode does not find these attributes and turns red (even though they exist).See the attached screencast video that shows the issue:
Exact steps for others to reproduce the error
Not that the
Color Attributenode in the Shader Editor has a red input indicating that it is invalid.LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps.
Bug report 1: The issue is about Color Attribute node ignoring data from Geometry Nodes in Edit Mode (but works in Object Mode). The problem is mode-specific (Edit vs Object) for Mesh geometry.
Bug report 2: The issue is when Geometry Nodes generate non-Mesh geometry (like Points), the Color Attribute node doesn't find attributes and turns red. So this is about geometry type (non-Mesh) causing the node to fail, not Edit Mode.
The key differences are:
So they're different issues. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 12.698089,
"duplicate_report_number": "117536"
}
Report flagged as NOT a duplicate by LLM
Regression: Attributes not passed on in Geometry nodes
https://projects.blender.org/blender/blender/issues/156077
System Information
Operating system: Windows-11-10.0.26200-SP0 64 Bits
Graphics card: Intel(R) UHD Graphics Intel 4.6.0 - Build 30.0.101.1404 Opengl Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Worked: 5.0.1 (and previous versions)
Short description of error
Geometry nodes is not passing attributes forward with some nodes when changing domains.
Exact steps for others to reproduce the error
Start a new file, create a new geometry node group for the cube.
Simply store a named attribute on point domain, then use "mesh to points" selecting "faces".
Try to view the attribute with a viewer. (Images attached)
The attribute is not passed on to the resulting geometry (in previous versions 5.0 and earlier, the attribute would have been interpolated between domains and transmitted until the end)
There are two images attached, one with the working result of Blender 5.0, where you can see the attribute in the resulting geometry. Another with the bug in Blender 5.1, where the attribute is missing.
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce.
Bug report 1: The issue is about the Color Attribute node in Shader Tree ignoring data from Geometry Nodes when in Edit Mode (but works in Object Mode). The problem is with shader parameters driven by attributes from Geometry Nodes not applying in Edit Mode.
Bug report 2: The issue is about Geometry Nodes not passing attributes forward when changing domains. The steps involve storing an attribute on point domain, using "mesh to points" selecting faces, and the attribute isn't passed in Blender 5.1 (but was in 5.0). So this is about attribute propagation between domains in Geometry Nodes.
Now, check if they're the same issue. Bug 1 is about shader nodes (Color Attribute node) not receiving attributes from Geometry Nodes in Edit Mode. Bug 2 is about Geometry Nodes themselves failing to pass attributes when changing domains. These are different areas: one is shader tree interaction with Geometry Nodes in Edit Mode, the other is internal attribute handling within Geometry Nodes during domain changes. So they're not duplicates.
JSON Data
{
"llm_judgement": false,
"processing_time": 15.627912,
"duplicate_report_number": "156077"
}
Report flagged as NOT a duplicate by LLM
Data Transfer doesn't work in some situations (geometry nodes modifier preceeding the Data Transfer modifier)
https://projects.blender.org/blender/blender/issues/103799
System Information
Operating system: Windows 10
Graphics card: Nvidia GeForce GT960
Blender Version
Broken: 3.5.0 (2023/01/11)
Short description of error
Data Transfer does not work on geometry generated by Geometry Nodes
Exact steps for others to reproduce the error
Error is set up in the attached file:
Color Transfer Test.blend
Doesnt work in
MaterialorRenderedviewport mode either.Color Transfer Test 2.blend
I don't know if it's related (it feels like it is) but even setting color inside a geometry node (on geo node created meshes) doesn't work in Material or Rendered viewport modes.
GeometryNodesColorBug.blend
LLM Reasoning
Got it, let's analyze the two bug reports. First, look at the key sections: Description and Steps to Reproduce.
Bug Report 1 is about the Color Attribute node in Shader Tree ignoring data from Geometry Nodes when in Edit Mode (but works in Object Mode). The issue is specific to Edit Mode vs Object Mode for shader parameters driven by Geometry Nodes.
Bug Report 2 is about Data Transfer not working on geometry generated by Geometry Nodes, and also mentions that setting color inside a Geometry Node doesn't work in Material or Rendered viewport modes. So the focus here is on Data Transfer modifier and Geometry Nodes-generated geometry, with issues in viewport modes (Material/Rendered), not specifically Edit Mode like Report 1.
The core issues are different: one is about Color Attribute node in Shader Tree (Edit Mode vs Object Mode), the other is Data Transfer modifier with Geometry Nodes geometry (viewport modes). So they aren't the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 14.199296999999998,
"duplicate_report_number": "103799"
}
Report flagged as NOT a duplicate by LLM
Color attributes from geometry nodes have no effect on volumes
https://projects.blender.org/blender/blender/issues/107264
System Information
Operating system: Windows 11
Graphics card: NVIDIA RTX 2060
Blender Version
Broken: (3.5, 1be25cfff18b)
Worked: unknown
Short description of error
Color attributes passed from geometry nodes to volume shaders color inputs in materials have no effect.
This is broken on:
Exact steps for others to reproduce the error
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions. Bug report 1 is about the Color Attribute node in the Shader Tree ignoring data from Geometry Nodes in Edit Mode (but working in Object Mode). Bug report 2 is about color attributes from Geometry Nodes not affecting volume shaders (like Principled Volume, etc.).
The key differences: Report 1's issue is specific to Edit Mode vs Object Mode for the Color Attribute node. Report 2's issue is about volume shaders not being affected by the color attributes at all. So they're different contexts—Edit Mode vs volume shaders. The steps to reproduce also differ: Report 1 compares modes, Report 2 involves volume shaders and a blend file. So they aren't the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 12.159278999999998,
"duplicate_report_number": "107264"
}