Standard Graph Instances

A Graph Instance lets one Standard Graph use another as a reusable texture-processing component.

Conceptually: Source Standard Graph → Public Interface → Graph Instance → Parent Standard Graph. Several instances can reference the same live source while keeping their own inputs, parameter overrides, processing context, and seed values. As you can see in the example video below (and if you’re thinking it’s the same video from the Exposing Parameters page, yes, you’re right — we were too lazy to record a new one), we used the custom noise graph twice inside the main graph with different random seeds. We could have used it as many times as we wanted.

Inside a Standard Graph, add Shift+A → Input → Graph Instance and choose the Standard Graph you want to reuse. WonderTexture reads the source graph’s public schema and builds the instance automatically.

Source input Labels become socket names, and source Output roles, names, types, and Order define the result interface.

Source texture inputs can be fed differently by every instance. A reusable filter with Source and Mask inputs can therefore process different textures each time it is used.

One source texture input can be the Primary Input, providing the main input context for the nested graph. For resolution and precision inheritance, see Core Concepts → Resolution & Precision.

Exposed parameters become per-instance overrides. If the source defines Scale = 5, one instance can use 2 and another 12 without changing the source itself. Compatible parameters can also be driven through value sockets; a connected socket acts as the dynamic value used during evaluation, while an unconnected socket uses the instance’s stored UI value.

Groups authored in the source carry into supported instance interfaces and can keep complex reusable graphs compact. Expand Parameters when you need the source selector, Base Parameters, groups, and public controls; collapse it again for a cleaner graph canvas.

Graph Instances use WonderTexture’s normal Base Parameters and pass their resolved processing context into the nested source graph. The detailed resolution and precision rules are covered in Core Concepts → Resolution & Precision.

Each instance also has its own Random Seed. WonderTexture combines it with the parent graph’s seed context so several instances can share one source while still producing deterministic variation.

IMAGE Same Graph - Unlimited Variations

Source Output nodes become instance outputs. Keep their Order values unique and intentionalso the reusable result stays predictable.

A Graph Instance references a live source rather than a detached copy. Internal source edits normally flow through the graph lifecycle without changing the instance layout, while public schema changes can rebuild the dynamic interface.

When sockets are rebuilt, WonderTexture tries to preserve parent links by matching public socket names. Reordering is therefore usually safer than renaming or removing a public Input, parameter Label, or Output.

Configured instances provide manual Re-Sync Source Graph and Re-Sync All Instances controls for deliberate recovery when the public interface looks stale. Normal edits should still update through WonderTexture’s automatic source and dependency workflow.

For the full schema-change workflow, see Source Changes & Resyncing.

Build Reusable Graphs Like Public APIs

Instances form graph dependencies. If Graph A instances Graph B and B instances Graph C, the chain becomes A → B → C, and WonderTexture synchronizes the required sources before evaluating the parent.