realize - blossommerz/locus-hub GitHub Wiki

Home > Realize

< Previous: Auto Array | Next: Reference >

Bridging Modeling & Nodes

Realize - node graph into the model

The Realize node makes the node graph's geometry real in the Modeling window.

Dataflow across the Modeling | Nodes divide: a drawn object in the Modeling window is pulled into the node graph by a Reference node (a live pointer, model -> node graph), flows through node operations, and reaches a Realize node whose output is sent back into the model as realized geometry the node graph manages (node graph -> model). Reference and Realize are the two opposite-direction bridges between the windows.

Realize is one of the two bridge nodes. It takes whatever geometry a branch of the node graph produces and materializes it as real objects in the Modeling window - a live output you can see, style, and export.

How it works

Wire the geometry you want into a Realize node. Its result appears in the model as managed objects - "managed" meaning the node graph owns them: they update when the node graph updates, and removing the Realize node removes the objects it created.

Give the node a name (double-click its header); the objects it creates take that name in the Layers panel, so a well-named Realize keeps the model side tidy.

Realize is the usual endpoint

Most node graphs end in a Realize node - it's how a parametric network becomes something you can actually export and use. You can have several, each realizing a different part of a design.

When you want to edit the result by hand

A realized object is driven by the node graph, so you can't freely edit it in the model. To cut it loose into free, editable geometry, use Bake.

The matching direction

Realize's counterpart is Reference - where Realize makes the node graph real, Reference points the node graph at something already real.

< Previous: Auto Array | Next: Reference >

⚠️ **GitHub.com Fallback** ⚠️