On a different note, are they any plans to give users control over if an input is a field or not? In most cases I just want a float to be a slider without the potential of an attribute being used for it
2 Likes
Nice. However I canāt really use instancing to generate the array as Iāll loose all relevant attributes prior
Not really sure what specifically you canāt get.
The attributes of the original are preserved, and if you need to associate the array with another mesh, you can use the transfer of attributes by index
It still looks sloppy, but more often than not, you need fewer attributes than copies of the object, which makes copy-paste of these nodes less
I agree that having this icon on every parameter is a real eyesore. There should be a way to hide it, or ideally just use a right click option to expose it in the first place. Also the icon design itself seems very out of place and does really indicate itās purpose.
3 Likes
For the most part, Iām creating an array of curves (which can have multiple splines), and not a mesh geometry so I can easily lose captured curve parameter, radius, etc that Iāve manipulated much earlier in the graph if I use instancing to make arrays. Also, I canāt really generate indices of the duplicates like you did as I mostly want my duplicates to remain in the exact same spot and then adjust their transform much later depending on what Iām working on. (either rotation location or scale). In my case, I use the set ID node as itās just more straightforward. Although I can imagine how instancing along a line and converting the position as the index can work and then later resetting the position of the instances to the same spot. However, itās just unnecessarily hacky IMO.
In the end, a dedicated duplication node is just the best solution
Stuff Iām working on
5 Likes
The best is a simple inheritance of the emitter attributes, as well as the ability to represent geometry as an attribute, for example, for a node for dividing a mesh into mesh islands.
1 Like
At present, it is impossible to read the data of the main camera. It is best to have a node that can obtain data such as the coordinate and rotating focal length of the main camera.
3 Likes
Hi, i need some help. I want to rotate a plane , so it points in the camera direction, but stays upright (locked track?). My inner artist thinks this should work, while my inner mathematician is too weak to understand why itās not:
Thx in advance!
I think it should be ārotate instanceā here instead of āset positionā?
Set position does not affect the rotation irrc.
1 Like
so i have to make things into instances before i can rotate them with fields? Oddā¦
Tried it. Doesnāt work:
The problem mainly is: The object is a single plane. Do i have to add a single vertex to the origin of the object in order to be able to spawn my instance there?
If i add a vertex to spawn at, my texture is brokenā¦:
ā¦while it should look like this:
EDIT: itās the UVs being killed by instancing the thing, right? Shoot! Yet another project to be on halt until we get things like UVs, unsubdivide, merge by distance etc. etc.
Or you can use a transform node? That rotates all geometry around the origin.
1 Like
but the sockets are round, and then you get a red noodle 
Thanks for your help. It kind of works now. The bulgy displacement is kind of broken, but at least the plane is sort of pointing in the cam direction:
EDIT:
Again: Thanks!!! What a great community!
1 Like
Hello to the whole community! Because This topic is about the Geometry Nodes project here I wanted to clarify if the Curves object will have support for attributes? I read the design of one task ā T92734 Support applying modifier on curve objects and as I understood from its description, curves will not be given the ability to store custom attributes. I am doing Grooming Hairs for games using curves and to create a more convenient process I expected to use curves and attributes in conjunction with Geometry Nodes. Please give clarification to ā HooglyBoogly or other people with knowledge of this. I really like your job!
The task means that edit mode / regular curves do not support attributes, but they do in geometry nodes, so there should be a warning when applying the modifier because at that point the geometry nodes curves have to turn into the old curves.
One of the goals for the future is to use the new curve data structures outside of geometry nodes too, so they would support custom attributes everywhere.
2 Likes
Andā¦ Another question 
Iām trying to understand if the sharability paradigm imposed on the fields workflow is the same concept I have In mind of what it means for a node group to be sharable.
So imagine I have two geo nodes modifier on two different objects. Object A has a āgenerationā node group that generates some random geometry by simply changing a seed input. Object B has a ādistributionā node group that distributes any object over its surface. Is it possible to distribute obj A over obj B such that obj B has access and writes to the seed parameter of obj A for every instance of obj A that is distributed. This way the instances are all uniquely generated based on obj A geo nodes modifier.
Is this possible currently or am I missing something.? I know I can easily do all this in one node group but it will be pretty neat to abstract complex set up into node groups on different objects. Or heck I donāt mind if this is doable on different geo nodes modifier on the same object. I just donāt know how to go about it yet so any help or advice is very much appreciated. Thanks
Curently i try to wrap my head around how to tell blender which curve from a bunch of them is the last. I guess it will have something to do with IDs. Is there currently a way to connect curve splines inside the GN tree? There isnāt right? The v.0.3 of my āNodesTreeā could benefit from help here 
3 Likes
