Latest news
D5 Render: sky, HDRI and weather settings – step-by-step guideChaos Vantage Scene States: Managing Day-Night and Material Variations from a Single SceneHow to enable realistic caustics in Corona Renderer and D5 Render: a guideArchitectural render videos with Runway Gen-4: a camera movement prompt guideSpeeding Up Presentation Prep with Enscape Visual Settings PresetsBuilding your own render workflow with Veras 5.3 NODES: a step-by-step guideHow to Generate Music for Architectural Presentation Videos with Lyria 3.5 Clip PreviewToonflow: open-source AI platform for short drama and video productionInstant NeRF: Training 3D Scenes from Photos in Minutes — Setup and StepsUsing Gaussian Splat in V-Ray: a step-by-step guide for Maya
Tips & GuidesSketchUpRevitRhino

Building your own render workflow with Veras 5.3 NODES: a step-by-step guide

The NODES tab introduced in Chaos's AI visualization tool Veras 5.3 lets users build custom node-based render workflows and send them directly into Revit, Rhino and SketchUp.

A scene in a bright architecture studio showing a massing model on screenAI image
Representative image, generated with AI.Image: 3dsınıfı / FCA AI

In brief

  1. The NODES tab in Veras 5.3 combines image/video generation, analysis and parametric 3D geometry into a single graph.
  2. The AGENT tab can automatically build a node graph from a written description.
  3. Bake to Revit, Bake to Rhino and Bake to SketchUp nodes place the generated 3D model directly into the open project.
  4. The CONTROLS and OUTPUT panels turn a built graph into a simple, reusable tool.

Chaos has announced a new tab called NODES in version 5.3 of its AI-powered visualization plugin Veras. NODES lets users combine image and video generation, analysis, and parametric 3D geometry creation into a single node graph, then send the result directly into Revit, Rhino or SketchUp. The feature is currently in Beta and is included with the existing version of Veras.

This guide, based on Chaos's official documentation, walks through how architectural visualization teams can use the NODES tab in practice, step by step.

What is NODES and how does it work

NODES provides a node canvas. Each node performs a single task: loading an image, writing a prompt, generating an image, removing a background, or creating a video. Nodes are connected to each other with "wires," and the entire chain is run with the RUN GRAPH command.

According to the documentation, node categories are grouped as follows:

Node CategoryExample NodesFunction
InputsImage, Video, 3D Model (.glb), TextBringing in external data
GeneratorsImage Generator, Video Generator, 3D GeneratorContent generation
AnalysisDescribe Image, Depth Map, Detect Objects, LLMImage/text analysis
GeometryBuilding, Box, Extrude, Boolean, ArrayParametric 3D massing creation
OutputsSave 3D Model, Bake to Revit, Bake to Rhino, Bake to SketchUpSaving/placing the result

Step by step: building your first workflow

  1. Open the NODES tab and drag your desired node onto the canvas from the panel, or click it.

  2. Right-click or double-click on the canvas and search for a node in the Add menu that appears.

  3. When you drag a wire into empty space, the menu only lists nodes that accept the data type carried by that connection, reducing the risk of a wrong link.

  4. You can drag an image or video directly from the workspace strip onto the canvas to use it as an input.

  5. Once the graph is complete, press RUN GRAPH; results drop into the workspace one by one as each node finishes.

According to the documentation, up to 4 cloud jobs run simultaneously at a time, and the rest are marked Queued. Nodes that haven't changed aren't re-run; Veras reuses the previous result, saving credits and time.

Automatic graph creation with AGENT

The AGENT tab in the NODES panel works like the agent in the MODEL tab, but instead of a model it builds a workflow. Simply type what you want:

Prompt
render my sketch in three styles and make a short video of each

The agent adds nodes based on this request, connects them, configures their settings, and moves important settings to the CONTROLS panel. According to the documentation, the agent asks the user before running anything that costs 25 credits or more, or that would exceed the session budget.

Turning the graph into a tool with CONTROLS and OUTPUT

The CONTROLS panel gathers important settings in one place. A setting can be pinned to CONTROLS using the ⊕ icon that appears when hovering over it. The OUTPUT view shows the workflow's result at full size; the result can be an image, a video, or a 3D view that can be rotated in Shaded/Arctic Clay/Wireframe modes.

The Math node can compute a number from up to four inputs, for example:

math
a * 2 + 1

This way, a slider value can directly feed another node's setting.

Baking to Revit, Rhino and SketchUp

Inside the host software, nodes in the Outputs category place the generated 3D model directly into the open project:

  • Bake to Revit places the model at the internal origin point as a family.

  • Bake to Rhino places the model at the origin as a block, either as full geometry or a lightweight proxy.

  • Bake to SketchUp places it at the origin in the same way, as full geometry or a proxy.

In Revit and Rhino, re-running the node overwrites the previous bake instead of creating a duplicate. Important note: each bake node is only listed in its own host; that is, Bake to Revit only appears inside Revit.

What this means for architectural visualization teams

NODES is particularly valuable for offices that want to set up repetitive visualization steps once — for example, rendering a massing study in different styles, cleaning up backgrounds, or stitching together a video — and then reuse them repeatedly. Thanks to CONTROLS and OUTPUT, a workflow built this way can turn into a "turn a slider, hit render" tool even for a team member without technical knowledge. However, it's worth remembering that AI-powered nodes (Image Generator, LLM, 3D Generator) consume credits on every run, while nodes in the Geometry category (Building, Box, Extrude) run locally for free and instantly.

Common mistakes

  • Running the entire graph from scratch (Run all) on every small change wastes credits; only the node that changed is automatically marked Stale, and re-running just that one is enough.

  • Looking for the bake node in the wrong host: each bake node only appears inside its relevant plugin (Revit/Rhino/SketchUp).

  • The "Bake chunk out of order" error seen in older versions when the Veras window is reopened a second time in SketchUp; this issue has been resolved by updating the SketchUp plugin to version 5.3.

  • Ignoring the cost warning before an expensive run; the RUN GRAPH menu shows the estimated cost before execution.

Sources

2 sources
B
blog.chaos.comblog.chaos.com/veras-5.3
Summary
B
blog.chaos.comblog.chaos.com/veras-5.3
Quote

Source texts are not republished; short quotes are marked, everything else is our own summary and commentary.

3dsınıfı’s take
3dEditor’s assessment

For offices in Turkey, NODES makes the most sense for those looking to standardize repetitive visualization steps rather than one-off render requests. Tasks like rendering a massing study in three styles and turning it into a video can now be set up in a single graph and shared with the team via CONTROLS, making it easier for junior team members to produce output without wrestling with complex settings.

That said, it's important to keep in mind that AI nodes consume credits and that the feature is still in Beta. Since the license plan (Community, trial, or paid) directly affects credit allocation for corporate use, offices planning heavy usage should budget accordingly, and shift as much of the workflow as possible to geometry nodes once they realize these run free and locally.

Frequently asked questions

Which version of Veras introduced the NODES tab?

NODES was added with version 5.3 of Chaos's Veras product and, according to the documentation, is currently in Beta.

Can a 3D model created with NODES be exported directly into Revit?

Yes, the Bake to Revit node in the Outputs category places the generated model as a family at the internal origin point; the same function is available for Rhino and SketchUp via separate nodes.

Which nodes in NODES run for free and instantly?

Geometry nodes like Building, Box, Extrude, Boolean, Array and Transform run locally on the machine, are free, and update instantly as settings change.

Comments and the forum are in Turkish.Join the discussion
+

Related news