Geometry Nodes

[RiccardoBancone]

I agree but, are you aware of these threads (I assume you are talking about named attributes topic)?

Hardcoded Attribute Names Removal [Proposal]

The object/collection input sockets in these nodes have to be removed as well I understand the problem. There would be no way to know from within the GN nodes which attributes are available inside an object. Each object could have a different set of attributes. Would there be a way to have ‘attribute classes’ or ‘attribute traits’ (a set of attributes, associated with a label)? An example of a class could be something like “Basic”, which associates with attributes (uv map | position ). Any…

Shareable Named Attribute Node [Proposal]

It seems that all these concepts topic are finally hitting reality now, surprising some users Touché Note that I do not understand why this “problem” of sharability is such a big deal. Such a big deal, that it apparently justified the removal of the get/input named attribute accessibility within nodetree? As @Hadriscus Said well Also, important point: Assuming constant re-usability is a wrong assumption. The design paradigm of re-usable nodegroups do not apply to geometry node, because…