Using geometry nodes in other geometry nodes
I'd like to be able to use a geometry node as input in another geometry node.
Let's say I have a brick node which exposes a few properties such as width, height, depth, and a seed. Then I create a "Wall" node which takes the brick node as input and can manipulate the exposed properties.
This way I can put my brick node in the asset library for reuse and at the same time modularize and better organize my node setup.
It would be even better if we could have multiple input nodes. Let's say I want to build a castle. Then I could have two input nodes: one for the wall and one for the corner towers. Then I'd outline the castle with some simple edges and have walls build along the edges. Every time there is a steep angle between two edges I would place a tower.
Having something like that split up in multiple nodes would give a far better overview of what's going on.
6 Comments
I tried something like this with
node groups, and it failed unexpectedly because information "leaked" out of thenested note groupinto thetop-level node group; This means that "input" nodes such asPositiondid not function correctly as they were looking at geometry being generated within thenested node groupinstead of the downstream geometry in the top-level. Hopefully that makes sense... ?I have a feeling that this request would address my problem. My work around was to only ever do math within node groups, and only generate geometry in the top level, but it was not ideal.
Shift + A and searching your Node Tree under Group section is not what you are looking for?
Well, it sort of is, but the closest option is input type "Geometry" which takes a static piece of geometry. What I would like to have is a "Geometry Node" type as input.
Example: I have a "wooden planck" node which has a seed as input i.imgur.com/UGS3gQr.jpg
That seed I cannot modify when I drop it into my "fence" node i.imgur.com/qZpQg7G.jpg
I mean this node, can be any group node and that way you make assets for reusability: imgur.com/a/VegMR0v
I have a tree generator on the works that has this kind of behavior. I generate different leave variations from another GeoNodes. But instead of using the Geo Node as a template, it takes a bunch of points with the attributes values (such as number of lobes, height/width ratio, stem length, random seed) stored in them, and then it create one different leave for each point.