THREE.JS / FOUNDATIONS 313

Save the graph.

A material graph becomes a stable application document, is rebuilt from JSON, and is compared with Three.js's native node JSON while keeping the native loader entry point and its runtime compatibility boundary explicit.

Preparing graph fixture—

The left and right meshes will render independent graph instances.

graph nodes
—
native nodes
—
connections
—
JSON bytes
—
native snapshot
—
NodeLoader
—
backend
—
frame samples
—
draw calls
—
application document—

Stable IDs and explicit slots are the app-owned persistence boundary.

native JSON—

Node.toJSON() exposes UUID-linked node definitions in the pinned release.

render parity—

Original and reloaded materials render the same authored graph until one is intentionally mutated.

graph event logwaiting

No graph events yet.

Drag to orbit · Node.toJSON() is released · native loaders are exported from three/webgpu and audited separately

Inspect material slot ownership →

LAB 313 / GRAPH PERSISTENCE