What does Veras 5.3 NODES change for architects?
Veras 5.3 NODES turns repeatable image, video and 3D procedures into saved graphs that can expose simple controls and return geometry to Revit, Rhino or SketchUp. Its value is a reusable method, not a prettier node canvas. Because NODES is beta, firms should version graphs and verify every baked result.
Chaos released Veras 5.3 on 19 October with a picture that will look familiar to anyone who has opened ComfyUI or Dynamo: boxes, wires and the faint promise that the messy part can now be called a system. NODES links generators, image analysis, video, simple geometry and host-application outputs in one canvas.
The official release post says a graph can accept images, text, video or GLB files; create depth and Canny maps; call an LLM; generate media or 3D; and bake the model into Revit, Rhino or SketchUp. Chaos labels NODES beta. Those are vendor-documented capabilities, not an ArchiGen product trial.
Why does this matter beyond another node editor?
Nodes are hardly a novelty. Dynamo turned Revit procedures into graphs years ago. Grasshopper made visual programming a daily language in Rhino. ComfyUI made the graph the visible anatomy of an image pipeline. Veras is interesting because it places those habits beside generative media and a route back into the authoring model.
That return path matters. A browser generator ends with a download. NODES can end with a Revit family, Rhino block or SketchUp component at the host origin, according to Chaos. Re-running a Revit or Rhino bake replaces the previous item instead of adding another copy. The output is still not automatically trustworthy, but it has crossed from reference image into model space.
This makes the release a companion to the split described in ArchiGen's Veras-in-V-Ray analysis: generative exploration stays separate from precise scene construction until a deliberate handoff. NODES makes that handoff programmable.
The graph should become an office tool
Chaos lets authors pin selected settings into a CONTROLS panel and designate a main output. A dense graph can therefore appear to a colleague as a modest interface with a prompt field, two sliders and a Run button. That is the best part of the release.
Most people in a practice should not spend Tuesday afternoon tracing wires. They need a bounded instrument: turn this approved massing into three material studies, keep the camera, save the results here. The graph author owns the complexity. The user sees only the choices that are safe and useful.
| Graph layer | Office rule | Review evidence |
|---|---|---|
| Inputs | Name accepted file types, units and source revision | Input snapshot and model ID |
| Controls | Expose only variables a user may change | Saved values and operator |
| Generation | Record model, seed and credit cost where available | Run history and result set |
| Bake | Set scale, origin and replacement behavior | Host-model check before acceptance |
That structure also separates authorship from operation. A computational designer can maintain the graph while a project architect runs its approved controls. The distinction is healthy. Shared automation becomes dangerous when everyone is quietly editing the mechanism while assuming someone else checked it.
Can the Nodes Agent safely build the graph?
Veras includes an agent that can add nodes, wire them, set values and run the result. Chaos says it asks before a run costing 25 credits or more, or one that would exceed the session budget. Cost consent is useful. It is not design approval.
An agent can produce a syntactically connected graph while misunderstanding the task. “Render my sketch in three styles and make a video” is easy to wire and hard to specify. Which lines are fixed? Which camera owns the final clip? May furniture move? Is generated geometry allowed to enter the BIM file as more than a placeholder?
Use the agent for graph assembly, then read the graph as a procedure. Inspect every external call, exposed setting and terminal output. The same caution sits behind ArchiGen's ComfyUI portability test: a graph file is not a reproducible workflow until dependencies, versions and inputs travel with it.
Partial reruns are useful, and easy to misread
Chaos says unchanged nodes reuse their last result. Editing a late prompt reruns only affected downstream nodes; changed inputs mark nodes stale. Up to four cloud jobs run at once, with the rest queued. This can save credits and time.
It also creates a provenance question. Two final images from the same graph may contain results generated on different runs. That is ordinary computational caching, but a review record must show which upstream outputs were reused. “Same workflow” does not mean “same execution.”
Veras saves workflow versions when the graph runs, when the agent finishes and when the user saves. Keep a named approved version outside the rush of automatic history. Pair it with the source model revision and chosen output, much as the V-Ray VFB history method ties an AI option to its parent render.
How should baked geometry be checked?
Chaos documents simple live geometry nodes for building forms, boxes, extrusions, booleans, arrays and transforms. The Building node can expose width, depth and height as controls. Capture View can send the resulting model into an image generator. That makes a neat loop from parameters to picture.
The picture is not the check. Before a bake becomes project geometry, verify units, dimensions, origin, orientation, category or block type, face quality and replacement behavior. Check the object after reopening the host file. A pleasing generated chair at the correct apparent scale can still arrive as an awkward family with no sensible use beyond the view.
ArchiGen's image-to-3D acceptance gate supplies the missing skepticism: generated mesh belongs in the model only after scale, topology, editability and intended status are recorded. NODES shortens the route. It does not waive the gate.
ArchiGen's take: standardize the boring graph first
The tempting demo is a twisting tower controlled by a slider, rendered in three moods and sent into motion. Fine. The valuable first graph is duller: a fixed source view, a named prompt template, two permitted material variables, a contact sheet and a saved record of the chosen result.
That graph can teach a practice whether controls are clear, results remain attached to inputs and reruns behave as expected. Only then should geometry cross into a project model.
Veras 5.3 does not make node workflows new. It makes them harder for BIM teams to ignore. The wire diagram is the easy part. The office standard is the product.
Evidence note: product capabilities were checked against Chaos's official “Veras 5.3: Introducing NODES” release post, published 19 October 2026 and accessed 20 October 2026. Chaos identifies NODES as beta. ArchiGen did not install or run Veras 5.3 for this article; control, review and acceptance recommendations are editorial analysis.