Node Group - Node Input Default for sockets
In some cases it is not enough to assign a default value to a node group socket. Instead, it would be useful to be able to use another node's output as the default.
For this it is necessary to deactivate the input widget, otherwise it would be impossible to make a distinction between no input and the untouched default value.
5 Comments
The idea of use by default if not specified otherwise is very needed
Geometry nodes has something like this for its node groups, letting you set the context normal or position as the default input for vector sockets. I like your idea with the extra socket at the front of the group input node. Would be nice to have something like that for both shader and geometry nodes.
I'm half convinced by this. On one hand I understand the need, but on another hand:
Considering the default vector is a global setting that everyone with a bit of experience know and expects, having suddenly a different default value makes an inconsistency that will definitely make people scratch their head.
Perhaps this could be an easy fix by having the default input value automatically displayed. I.E. if you set the default vector input to Texture Coordinate > Reflection, the socket would be automatically suffixed
Texture Coordinate > Reflection. Though, it makes a cluttered messy looking node.Thx for the feedback. I admit this isn't a very polished idea. I just had this problem with my Magic Texture copy and wanted to see whether others would be interested in such a feature.
I thought the missing input widget on the group node would be a good enough hint that the socket might have a default node input. Maybe some sort of frame / coloring / small icon + tooltip would be a compromise.
Yes, I've often wanted this. There are just certain circumstances where I want Groups I've made to work one way by default, but I still want the ability to plug in another value for special situations without needing different versions of the Node Group with or without certain inputs in my assets. But right now having an input means I would have to plug in the input I would want to be its default every time I add the Group. I think having the Value hidden in that case would indeed be an intuitive indicator to anyone who we may share the Group with, as when inputs on official nodes have hidden values, we often expect that they must have some default. In-fact, by that token, my suggestion would be for all values on the Group Input Node should have input sockets. and if we plug something into one as you show in your illustration, that will become the default and the Value will become automatically hidden from the outside, and if any Inputs in the Group Input are left untouched, then those inputs will act exactly as they currently do.