Have you tried to assign the group index to the position?
Capturing the position, setting it to the index, then setting it back will merge points with the same indices.
Then I need only capture the indices of the original geometries before joined and add them together:
For reference, here’s what it’s like without the merge node in this case:
And here’s with the regular merge by distance:
It feels just a little cheaty, but hey, it works!
A post was merged into an existing topic: Precipitation with Geometry Nodes
8 posts were split to a new topic: Nested Instances - individual random values?
That’s clever. Still, a generic merge node would be nice. It would have a single group index input -all elements sharing a group index would be merged together. No need to build kdtrees and all that, probably a good performance saving
Hi folks, thinking some more about this… I wonder if the following would seem useful ? →
Instead of having a “merge by distance” node (or in addition to it), what about splitting the merge functionality into its own node, give it an input where the user can connect anything (a sort of “merge index”) and make the kdtree (or whatever structure is used to store proximity) accessible on its own (new node) for other purposes? I wonder what these could be. I’m thinking geometry generation : creating faces or lines/curves between groups of points…
@HooglyBoogly you probably have other things on your mind right now,… but how does this sound to you? do you think it would open the door for new things?
One precedent for this kind of thing is the split edges node that went from “split edges by angle” to just “split edges” with a selection input
Kdtree, closest element that is not self would be dank
oh or return a geometry that is points !!
input index-> output that points data if it exists
A post was split to a new topic: Precipitation with Geometry Nodes
3 posts were split to a new topic: Aligning a texture along a GN curve
6 posts were split to a new topic: Accessing original mesh data from geometry nodes
12 posts were split to a new topic: Is it possible to control light intensity with geo nodes?
4 posts were split to a new topic: Rebuilding a curve that generated a mesh
8 posts were split to a new topic: Is there a way yet to properly link up a hierarchy chain that runs along a path?
2 posts were merged into an existing topic: Is it possible to control light intensity with geo nodes?
Getting really closed to being finished with this, been working on it for a while now in my free time and I’ve learned so much about geometry nodes in the process.
Really can’t wait for a loop node to be made, because having iterations avaliable would make a lot of busy work c/p node groups over and over. Ces’t la vie. I’m really happy with how it’s turning out.
5 posts were split to a new topic: Random value for each curve in “setposition”
It seems that the community decided that this is the official support, showcase and everything else about Geometry Nodes thread. And no one can stop us. Old habits are really hard to break.
I’ve noticed. I’ll continue on this in the other thread.
This thread is closed. Please continue discussion about the development of Geometry Nodes here:
Experiments and support questions for GN should be posted in the appropriate category, using the #geometry-nodes tag.