Geometry Nodes

at the moment, one of the most common requests from developers is the ability to inherit the attributes of an instantiation object, for example, indexes …

  • you should capture the attribute before instantiating so that it can be used (in theory)

I have a suspicion that the easiest way would be to transfer attributes using the transfer attribute
them and try to use not remesh, but the volume of dots, but I’m not sure if this fits

Here is one way of doing it

Hi, there is no support for transferring attributes from curves right now (it works only by index).

@Grinsegold remesh modifier destroys attributes and other data layers. You could make a separate remeshed object and transfer attributes from the original, though. I think that would work.

1 Like

Thank you. I dont really understand it, but it seems to work. Btw… aren’t you capturing the same attribute 2 times?

It’s me again :smiley:
I’ve tried to replicate your setup and its very close to what i need. But sadly i won’t work on instances other than 90 degrees. Wich seems logical, because the transfer attribute tries to get the closest parameter possible and this is not working on steeper angles. I really need a single value per instace (the value of the instanced origin).
If transfering information to point instances is not possible, then i sadly hit a roadblock here.

Replying to myself, because i found a workaround for my situation. I am using the attribute statistic to remap the spline index to a 0-1 range. Anyways… inherting the attribute from the instancer object would be more elegant. Thanks for everybodys help!


Hey I’m new to using fields and I’m in the process of making a procedurally generated building. I want to rotate points without changing underlying geometry, and without instancing again as used to be possible with the old point rotate node. How would this best be possible? see 10:10 of this tutorial

I didn’t watch the tutorial but I looked at the file you posted:
and I rebuilt it in a less troublesome way:
geometrynodespractice4 modified.blend.txt (1.2 MB)
Just delete the txt at the end because this forum does not support *.blend files

It’s my birthday and this is an amazing gift. Thank you so much

1 Like

Dear Blender devs, first many thanks for the great work and effort you put in the development and evolution of geometry nodes.
I have a small question: I am encountering a massive performance drop when pluging in the boolean node, even when working on a simple scene. Why is that? Is there a way to circumvent this? Others have talked about this issue before, for example in this youtube video you can see it at about 8 Minutes:

1 Like

It is because devs do not want to include fast boolean solver availalble in the modifier.

Is there a way to circumvent this?

Include fast boolean solver.


What does this node bring ? by definition nodes allow for duplication of data through branching so this seems redudant at first glance, I am very curious what I am missing

If you look at the example, you can do the equivalent of the array modifier with this.

1 Like

Oh, I see, so it does a sort of chained transform… and isn’t it the kind of thing we would get for free with loops ?

Probably indeed, in other applications you have both as well, but it seems the loop node has not the best performance, but I don’t know if that would be the case in Blender.

1 Like

The very first thing that I see in the example is the replacement of the instantiated duplication of the grid, in which so far the index cannot be obtained without deception

This node would be super useful for the kind of work I do with geometry nodes. I already have a hacky way of duplicating by branching as you can see in my previous post where I’m using the ID to store the duplicate index.

My node group for duplication normally looks like this!

This is for only making up to 15 copies of the same geometry with unique indices. Imagine the horror when I need to make up to 200 copies :cold_face:


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
Screenshot 2021-11-22 130954


I use this node for make array

1 Like