Search documentation Ctrl K

Docs / Interface / Graph Explorer & Baked Node Library

Interface • WonderTexture

Graph Explorer & Baked Node Library

Navigate WonderTexture graph dependencies, inspect external resources, browse reusable baked nodes, and add assets back into your graphs.

// PROJECT TOOLS

Three Different Ways to Find What You Need

WonderTexture has three tools that can look similar at first but solve different problems:

Graph Explorer

Shows WonderTexture graphs, dependencies, and Bitmap resources inside the current Blender file.

Baked Node Library

Manages reusable WonderTexture nodes that you baked locally or installed from a .wtnode package.

Header Library

Provides a fast visual browser for adding available built-in and reusable nodes to the current graph.

The distinction becomes much more useful once a project grows beyond a single graph.

Graph Explorer

Open Graph Explorer from the WonderTexture N-panel. It shows the current Blender file as a package and organizes the WonderTexture graphs inside it by dependency. Different graph types use different icons, so Standard, Function, Pixel Composer, and FX-Map graphs remain easy to distinguish.

Open Graphs and Find Their Instances

Click a graph name to open it in the current WonderTexture Node Editor. The graph you are currently editing is marked Active.

When one graph depends on another, Graph Explorer can also help you locate the instance nodes in the parent that reference that dependency, including an instance count when the same source is used more than once.

WHY GRAPH EXPLORER MATTERS

Large procedural systems often contain several reusable graphs. Graph Explorer lets you navigate those systems by dependency instead of manually hunting through node trees.

GRAPH EXPLORER

// DEPENDENCIES

Independent, Unrooted, Missing, and Cyclic Graphs

Graph Explorer also highlights structures that deserve attention. Independent Graphs are not currently part of another dependency chain, while Unrooted Graphs cannot be represented in a normal rooted hierarchy. Missing references and cyclic dependencies are reported as problems rather than normal runtime states.

DEPENDENCY ERRORS

Missing references and dependency cycles are project-structure problems. Graph Explorer surfaces them early so they do not become harder to diagnose later.

// BITMAP RESOURCES

Track Images Used by WonderTexture Graphs

The Resources branch tracks Bitmap images used by WonderTexture graphs:

BITMAP RESOURCES

INPUTTYPEDEFAULTDESCRIPTION

ExternalResourceValidThe image references an external file that WonderTexture can currently resolve.

PackedResourceValidThe image data is packed into the Blender file.

Missing fileResourceProblemThe referenced external image cannot currently be found at its resolved path.

No file pathResourceProblemThe Bitmap uses image data that does not provide a usable external file path.

Expand a resource to see which graphs and Bitmap nodes use it. Click a usage to open the corresponding graph and select the node, and refresh Resources after external files or image assignments change.

Browse Your Reusable WonderTexture Assets

The Baked Node Library manages reusable WonderTexture nodes in your user library. It can contain local author bakes created on your system and imported packages installed from .wtnode files.

The panel shows how many assets are currently visible compared with the full library, and Refresh reloads changes made outside the current Blender session.

Search and Filter the Library

INPUTTYPEDEFAULTDESCRIPTION

SearchTextEmptyFilters reusable assets by name.

CategoryFilterAllLimits the browser to assets belonging to a selected category.

TypeFilterAll TypesFilters assets by Standard Graph, Pixel Composer, or Function Graph bake type.

Use Reset Filters to return to the complete library, then select an asset from the thumbnail browser for more detail.

// ASSET MANAGEMENT

Edit, Export, Import, and Remove

For locally authored bakes, Edit Details updates user-facing metadata, Export creates a shareable package, Import installs a compatible package, and Remove deletes the selected asset from the user library.

IMPORTED PACKAGES

Assets installed from managed .wtnode packages are treated differently from local author bakes. Their updates are expected to arrive through packages rather than by exporting the installed copy again.

The full bake, package, update, and sharing workflow is covered later in the Graph Baking and Sharing documentation.

// PREFERENCES

User Node Library Location

You can inspect the user-library location at Edit → Preferences → Add-ons → WonderTexture → User Node Library. If the directory exists, WonderTexture also provides an Open Library Folder action.

Normally, manage assets through WonderTexture rather than editing package contents by hand.

Previous← Favorites Shelf Next2D Preview →