Variables (Set & Get)

Variables let you share data between Scene Assembler node graphs in the same .blend file. They are useful when multiple graphs use the same camera, render settings, or collection configuration, and you want to define it once and reuse it everywhere.

How variables work

A Set node stores the value flowing through it under a named key. A Get node retrieves that value by name. Variables are available across all graphs in the file — if you set a variable in Graph A, a Get node in Graph B can read it.

Variables are rebuilt each time a graph is evaluated (when you send a job or build a preview). They are not persistent between Blender sessions.

Defining a variable

1. Add a Set node anywhere in a chain.
2. Set Type to match the kind of data you're storing (Collection, Camera, Render Settings, etc.).
3. Enter a Variable Name. This name must be unique per type across all graphs.
4. Connect the Set node inline — it passes its input through unchanged.

Reading a variable

1. Add a Get node where you want to use the value.
2. Set Type and Variable Name to match the corresponding Set node.
3. Connect the appropriate output socket (the Get node exposes outputs for all types simultaneously).

Evaluation order

Set nodes are evaluated before the main graph runs. If a Get node's graph depends on a Set node in another graph, the Set node is guaranteed to have run first. Circular dependencies (Set A reads a Get that reads Set A) are detected and reported as a warning.

Tips

• Variable names are case-sensitive.
• Duplicate variable names of the same type produce a warning. Only the first Set node evaluated will write the variable.
• Variables are a good fit for project-wide assets: the main camera, the hero collection, or the project's render settings template.