Right-Click Select This is a read-only archive
← All ideas
  • Published 8 Apr 2021

Geometry nodes - multisocket output node

The Geometry output node should also have the multisocket like the join geometry node has, so you actually don't have to use the join geometry node unless you need to do geometry joining before other node operations. If I have just 2 or 3 node routes that I want to join at the end, I should be able to just connect them right into the output node and join them automatically.

blender-multisocket.png

90.9%

Development Status: Open

Upvote 50 Downvote 5
Dest
8 Apr 2021

10 Comments

xu

As far as I could understand, it is just a join geometry before final output. I understand that adding a join geometry node every time is kind of annoying. But I think they should be 2 separate nodes and my reasons are plased below :

  • Besides joining 2 noodles into 1, the join geometry node does some calculation, like re-calculating the index. Putting a join geo node could always remind people geos are different before and after joining;
  • I want the groupoutput node, as its name says, to do nothing but outputing. Currently we have only one mesh in one obj, so one port for output nodes is less confusing;
  • If we really have multisocket output node, the result in fig below could be more intuitive for me.

multisocket output node result

1
roelant.rijs

Best argument against: it could conflict with the ability to output several geometry objects from one GN tree, which I really hope gets implemented some day. A switch to choose which behavior to use might work, but perhaps "autojoin" for all output sockets plus the option to have more geometry outputs (that also use automatic joining) would be even better.

Dest Author

I moved this to the new Geometry Nodes category for better discovery.

1
giannife

This is an obvious and simplification extension. I always have that final join node that is in the way :-)

Vyach

How it should work? As geometry duplicator? I would prefer geometry instance then.

Dest Author

* @ Vyacheslav * exactly like "Join geometry node" as I stated in the description. To be precise, like join geometry node will work in 2.93

Vyach

* @Dest * oh, sorry for misunderstanding. So multiply input == join. Yes, nice idea and it is logical: when I want to output some geometry, I can output all at once.

mrajendra2150

Yes i like the idea, sometimes i think blender make things unnecessary complicated. Point scale, point distribute and many point nodes, why not just make a "+" icon inside point distribution if we want to add point scale, this will lead to quick decision making.

zorro.weaver

* @mrajendra2150 * Now I think that might be a little too far. We want to be able to choose the vector of our scale based on another value, right? Sometimes merging nodes is not the best idea. But I think auto joining in the group output makes sense.

1
zorro.weaver

I like that. The multi input socket exists, why not use it? Almost everyone ends up putting a join geometry node at the very end, so it would make sense to have it built in.