Named Attribute Nodes in Blender 3.0

[cata_cg]

Here’s an interesting one:

We already have a long list of pros and cons regarding Get/Set (Named Attributes) which is overwhelming in favor of it being added (added back?).

I don’t think it’s even an issue of “if”, but “when”, since even Dalai mentioned in his post, that they are considering this, it’s just a matter of time & deadlines (Last 2 sentences are important):

Geometry Nodes in Blender 3.0 - Status Update

If anyone needs any clarification on the current design, I will be glad to elaborate further. That said, I know some people want to talk about the Get/Set nodes, and this is not the point of this post. The focus here is on getting everyone aligned for the 3.0 release, so everyone can help with testing, new files, documentation, … Whether to support those nodes is a topic that can be revisited for 3.1. For now, there is enough on the agenda. And the current design of shareability is still the d…

What I’m aiming to say here: at this point, we should try to give strong reasons why it should be added in 3.0 instead of 3.1 (“when”), because the other battle is long over, (the “if”). Or at least I hope…

This is (kind of) hinted here:

@dfelinto

about possible 3.1 only targets.

Also, I think I understand why the huge focus on “share-ability”. For most of us (single user) it’s a smaller concern, compared to a team (multiple users). And remember that the development focus is for Blender Studio. They probably rely heavily on this concept.

That being said, I still agree with this statement:

@JuanGea

Share-Ability si not something that should be defined by the software, it must be defined by the tech artist / TD that is using the node tree, and that artist must learn to properly do this.