How would this be a better solution for Blender?
The proposed design is useful when nodes contain hudge amount of options so you get smaller node in the graph but this needs duplication of informations (on the node itself to connect things, and on a contextual menu like the N panel).
Since Cycles/Eevee only display the strictly necessary for shading directly on the nodes, each one can stay relatively small, yet still very powerful. To compensate that, you have a bit more nodes to play with which is good for flexibility!
1
l
lsscpp
It's way better how it is now! The principled shader is a big node anyway, so why not make use of that blank space? We also are not forced to open the side panel to even just see values
1
T
Thane5
The current sliders are part of blenders design language and likely wont be changed anytime soon
3 Comments
How would this be a better solution for Blender? The proposed design is useful when nodes contain hudge amount of options so you get smaller node in the graph but this needs duplication of informations (on the node itself to connect things, and on a contextual menu like the N panel).
Since Cycles/Eevee only display the strictly necessary for shading directly on the nodes, each one can stay relatively small, yet still very powerful. To compensate that, you have a bit more nodes to play with which is good for flexibility!
It's way better how it is now! The principled shader is a big node anyway, so why not make use of that blank space? We also are not forced to open the side panel to even just see values
The current sliders are part of blenders design language and likely wont be changed anytime soon