Support Exporting Nodes within Subgraphs or Groups:
Hello Team Material Maker,
I would like to propose a feature enhancement regarding the export functionality when using complex workflow organization (Subgraphs/Groups).
Context & Current Workflow:
In our specialized pipelines, we often create intricate workflows that involve grouping multiple nodes and setting up custom outputs. For example, I am creating a DDNA map for a game engine, which requires packing data from four separate sources into specific channels:
Red Channel: Albedo Color
Green Channel: Normal Map Green component
Blue Channel: Glossness/Smoothness Map (Note: Roughness is inverted before use.)
Alpha Channel: Normal Map Blue component
To manage this complexity, I build a dedicated group. This group not only houses the final Export Node but also handles automated metadata tasks, such as setting the output file extension using a template like $project_ddna.
The Limitation (Current Pain Point):
Currently, if the required Export Node is placed inside a Subgraph or Group—even though it is fully connected and functional—the main export function fails to recognize it. This forces me to flatten complex, organized graphs just to enable basic exportability, which defeats the purpose of using subgraphs for clean project management.
The Feature Request:
I request that the exporter be updated to recursively scan and execute Export Nodes located within Subgraphs or Groups. If all required connections are met within a contained group/subgraph, the system should treat it as if the node was at the root level.
This enhancement would significantly improve workflow organization and efficiency for complex export pipelines.
BTW:
Thank you so much for this software, its awesome!
Support Exporting Nodes within Subgraphs or Groups:
Hello Team Material Maker,
I would like to propose a feature enhancement regarding the export functionality when using complex workflow organization (Subgraphs/Groups).
Context & Current Workflow:
In our specialized pipelines, we often create intricate workflows that involve grouping multiple nodes and setting up custom outputs. For example, I am creating a DDNA map for a game engine, which requires packing data from four separate sources into specific channels:
Red Channel: Albedo Color
Green Channel: Normal Map Green component
Blue Channel: Glossness/Smoothness Map (Note: Roughness is inverted before use.)
Alpha Channel: Normal Map Blue component
To manage this complexity, I build a dedicated group. This group not only houses the final Export Node but also handles automated metadata tasks, such as setting the output file extension using a template like $project_ddna.
The Limitation (Current Pain Point):
Currently, if the required Export Node is placed inside a Subgraph or Group—even though it is fully connected and functional—the main export function fails to recognize it. This forces me to flatten complex, organized graphs just to enable basic exportability, which defeats the purpose of using subgraphs for clean project management.
The Feature Request:
I request that the exporter be updated to recursively scan and execute Export Nodes located within Subgraphs or Groups. If all required connections are met within a contained group/subgraph, the system should treat it as if the node was at the root level.
This enhancement would significantly improve workflow organization and efficiency for complex export pipelines.
BTW:
Thank you so much for this software, its awesome!