Asset Workflow with Node Groups. Complete a task quickly, logically and appropriately. The NodeGroup to share :-)
- A node group performs a specific task
Depending on the TASK, the End User can make Adjustments within a certain framework:
The closed NodeGroup, which the NodeGroup Creator has defined.
- This Nodegroup has what it needs, in the right amount, with the most useful CONTROLS, FOR THIS particular TASK.
Short: There are three types of nodes: Input, Output and the "Others". Every "Other" node has inputs and outputs for the "main functions". What about the "other values"? The "unimportant" options and "unimportant" values? Those can only be changed, if you open one nodegroup around the other until you have the nested node in front of you. No matter which Node. No matter which value, which selection or which function; Everything should be able to be pulled into the NodeGroupInput. If this NodeGroup is closed, the corresponding "field" can be seen as in the original Node itself. :-) In my dreams :-) or in a other way. This workflow could be used in all areas where NodeGroups can be created in such a way that the presets are structured and clear.
Depending on the task:
-
The creator of a nodegroup does NOT want to use ALL sorts of things from all existing nodes!
-
He can CONTROL everything so that this particular TASK can be achieved as quickly as possible.
-
He can DEFINE which values can be changed in which number range.
-
Depending on the TASK, the Creator And The EndUser!
You don't have to take all of them. But nice if you could ;-)
Why: Share NodesGroups from shaders, geometrynodes and others with the community:
-
In a way that everyone immediately understands, can fine adjust and use your preset, which fulfills a "certain task".
-
Learning easier
-
Optimize your own work processes
-
Sharing is caring
Roger
8 Comments
I read your proposal twice and still have no real idea what you're proposing. What problem are you trying to solve with this proposal? This is written with a lot of detail that assumes some context that is missing here.
Hello Testure. Thank you for your time. I apologize for writing complicatedly.
The problem is that not all values from nodes can be pulled into the group input.
@testure Do you have any questions? What do you think of this workflow with custom groups? Any other suggestions?
Btw.. the stright lines on node is probosal betwen curves? Or how to set this type style in nodes?
Fig. 4. Not all options can be used for a preset.
Fig. 3. The user, sometimes me, has everything for the task at hand. Don't have to think about how what works. Just push until the result is good.
Figure 2. The creator defines the name, default value, minimum and maximum value.
Figure 1. Opened NoedGroup. The inputs can be adjusted on the right.