Access GN Output attributes
Are you planning on allowing the Output Attributes to be used as drivers? At the moment, this doesn't seem to be a possibility :(
blender.stackexchange.com/questions/242227/accessing-geometry-nodes-attributes-in-drivers
Are you planning on allowing the Output Attributes to be used as drivers? At the moment, this doesn't seem to be a possibility :(
blender.stackexchange.com/questions/242227/accessing-geometry-nodes-attributes-in-drivers
5 Comments
This is very needed when trying to mix geometry nodes with more standard (and already know) techniques. I'm trying to get a a vector output from a geometry node that gives a random location (set by an specific ID) to be used as driver for the location of other objects that are not in the same geometry nodes (and can not be, due to interactive purposes).
I tried using the group output and the capture attribute node, but I don't find a possible way. Maybe I'm missing something. If not it would be great to be added.
Agree! I'm trying to output a distance (a float value) from a Geometry Node to drive a camera focal length (which is a float value too if im not mistaken)
Output attributes as vertex weights
YOU CANNOT USE THEM as scalar values. These are FIELDS
Geometric nodes work with fields
drivers with scalars
I didn't mean per component values generated though fields. What I meant was, dynamic singular values diluted and passed on to the output node to control a parameter via a driver. What I'm suggesting is basically a node that can write to a given channel (no field involved) much like the "Attribute Input node" in Animation Nodes. There's already the ability to read from any given parameter via the input node in GN, so a node that could write to an Attribute would be awesome to have.
This way, you can grab the x pos of a point as a float value and can get it to control any float parameter. I do hope that was clear enough.
Other than that, surely I'm aware that the attributes that are output come out as arrays as they are spewed out on a per component basis, thus enabling them to only be utilized in another GN network or as a per-point weight map scheme.
In input setting we already have "single value" switch. All we need is same setting in output.