A new Join Geometry Portal Node
Join Geometry Portals would act like the normal Join Geometry Node but the input and output doesn't need to be connected on one tree (would be better if shown below).
It behaves like a group node over the fact that it can be duplicated as much as you want but it stores the data it collects over every individual one of it.
The goal is to try to separate every trees that does function and will eventually be added to the entire geometry anyway, As seen in the image below, you can see little trees that does its own thing but have to be connected to the main output,
The stressing thing is trying to connect all nodes together because as it gets bigger and bigger the tasks gets more repetitive and once you have two trees that you want to be close with one another, youll have to disconnect and reconnect it again.
This image below shows how tidy it can be with this Join Geometry Portals
Yes every Join Geometry Portal nodes should also be assigned with a universal color for a more visual distinction given how important it is
4 Comments
A more general solution for many things like this is "variable definition node" where you input a piece of data and assign a unique name to it. You can then put that node all over the place and put the same name in to get the same data.
There would need to be a feature for quickly locating all instances of that variable and the location where the variable was defined.
Interesting ! But maybe inconvenient with looped nodes ? If you could details it on a Idea on RCS I'd love !
I think my idea might be literally this exact proposal just with the name "portal" instead of "geometry portal".
Absolutely in love with this idea. I never heard something like this for nodes, and in facts it looks really good. Maybe it would be better just to have a "hide links" toggle property in each join geometry ? With this, we will keep the visual aspect of the nodetree, but improving visibility when needed.