Named Attribute Nodes #91742
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
10 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#91742
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?
Named attribute nodes weren't initially included in the fields design because there wasn't consensus about how they would interact with the "share-ability" design of the new workflow.
However, user feedback and testing has made it clear that the current attribute input and output options can exist alongside named attribute nodes, and the the flexibility is necessary.
Three new named attributes nodes will be added:
Remove AttributeNamed Attributeinput nodeStore Named Attributelike the capture attribute node, but creates a named attribute.The nodes will initially be added behind an experimental feature flag, so that the visualization options can be further developed separately.
For the visualization and UX, there are a few separate tasks:
Past discussions about this topic:
Added subscriber: @JacquesLucke
Added subscriber: @SteffenD
Store Named Attribute node with mappingto Named Attribute NodesChanged status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @GeorgiaPacific
This issue was referenced by
d4e46c13ccAdded subscriber: @nl
Added subscriber: @satishgoda1
Added subscriber: @27Anonymous
Named attributes will take precedence over data with the same attribute in Group Output node. I'm not sure if this is intentional, but it is a bit confusing and I think it would be more intuitive for attributes with the same name in the group output, to overwrite named attributes.
I believe I have also encountered a bug with this, or at least something weird.
This is the ending part of my geometry nodes setup:
The numbers to the viewer node and the group output do not match, despite being from the same reroute node. This seems to originate from when the name attribute is retrieved and operated on. Named attribute node by itself works fine:
And my combine XYZ, with static values of 64, 85.333, 1, also works fine:
But as soon as I divide the named attribute by the static vector, it disappears from the value node, while remaining in the uv_map data:
As I attempt to debug further, I notice that if I remove the extra view node, all the values turn to 0 in the UV map as well:
I feel like something isn't connected right in the code, but it could also be me making a simple mistake and missing something.
Assuming this is a bug, I'm not sure if this should be reported here, or as a separate issue.
The reason I started using the profiler in the first place is that, strangely, the UV coordinates for this auto-UV-generator seem to be much smaller than they should be once they are converted from attributes and viewed in the UV editor. The upper part of this node setup resizes the UVs to be 1/64th scale on X, 1/(4096/48) scale on Y, but upon actually viewing it in the UV editor, they are 1/4096th size instead. This is more likely to just be a math issue on my part though.
I'm leaning more towards user error now as it seems to work more consistently if I extract the data with another named attribute node:
The performance without it is very strange though and should probably be a bit more consistent.
Making the nodes as follows makes the scale correctly be 1/64 instead of 1/4096:
Added subscriber: @HooglyBoogly
If you think you've found a bug (it's hard to tell based on the screenshots), please report it separately like a regular report. Thanks!
This issue was referenced by
3e7ee3f3bcAdded subscriber: @Oliver-9
Removed subscriber: @Oliver-9
Added subscriber: @Tams_3d
Can the Remove Named Attribute Have the input socket like join geometry, so that many attributes can be removed at once, and we can feed the input as named attribute. This Was their at the Blender 2.93 Geometry Nodes
We didn't implement it that way because it ended up being confusing that the socket accepted more than one input but you could only write one name in the string field. If we could find some way around that issue, I think it could be fine.
Changed status from 'Confirmed' to: 'Resolved'