The Twinmotion Workflow

Twinmotion is a real-time visualization engine made by Epic Games and built on the same Unreal Engine technology that powers modern video games. That heritage matters: it means the image is computed continuously, tens of times a second, so you navigate a fully lit, shaded, reflective scene the way you would move through a game - not by pressing render and waiting.

The single idea that defines the Twinmotion workflow is the live link between your design model and the render. You do not draw buildings in Twinmotion; you build them where you always have - in Revit, Rhino, SketchUp, Archicad or another host - and Twinmotion reads that geometry and keeps reading it. It is a render layer bolted onto your existing modelling tool, not a replacement for it. Your design stays the single source of truth; Twinmotion is where you dress it in light, materials and atmosphere.

This reframes what the tool is for. Because bringing a model in is nearly free and updating it is one click, Twinmotion is not just a place to make final images - it is a place to look at your design throughout the process. Drop the model in early, and every design review can happen in believable light and materials rather than in flat working views. The pretty pictures at the end are a by-product of a faster, more visual way of working. That mindset - render as a live design companion, not a final gloss - is what separates people who get value from real-time engines from people who merely produce screenshots with them.

The mechanism that makes this work is the Direct Link (Twinmotion's live plugin) installed into your host application. Once it is in, a small Twinmotion button or panel appears inside Revit, Rhino, SketchUp or Archicad, and one click streams the current model straight into Twinmotion - no exporting an intermediate file, no rebuilding the scene by hand.

What comes across is the geometry, the object hierarchy, and as much material and metadata as the host exposes. Revit brings its categories and family structure; SketchUp brings its groups, components and tags; Rhino brings its layers; Archicad brings its element classes. Twinmotion uses that structure so you can, for example, select every 'wall' or every object on a given layer at once and assign a material to all of them. Cameras and some views can travel across too, so a scene you have already framed in the host arrives ready to refine.

The crucial verb is synchronise. After the first link, you keep designing in the host - move a wall, add a window, swap a floor - then press sync, and Twinmotion updates only what changed, preserving the materials, lights and entourage you have already added. This is the round-trip that makes real-time engines feel alive: the model and the render stay in step, so a late design change is a five-second refresh rather than a full re-import and re-dress. It also means the render can never quietly tell a different story from the model, because it is always reading the model. We will go deeper into keeping that link clean in the Live Link lesson; for now, the habit to build is: change geometry in the host, everything else in Twinmotion.

Twinmotion's interface is deliberately friendlier than a traditional 3D package, which is a large part of its appeal to architects who do not want to become full-time CG artists. At the centre is the real-time viewport - the lit scene itself - which you fly through with game-style navigation using the keyboard and mouse, exactly as you would explore a game level. Everything else is arranged around it as a few clearly-labelled docks.

Along one edge sits the library or asset dock: a big built-in collection of materials, vegetation, people, vehicles, furniture and props that you drag straight into the scene. Along another sits the scene graph or object list, showing the imported hierarchy plus everything you have added, so you can select, hide, group and organise. A dock of settings exposes the environment - sun position and time of day, weather, seasons, sky, and the overall lighting - as simple sliders and dials rather than parameters buried in menus, so changing the whole mood of a scene is a matter of dragging one control and watching the viewport respond. And an output or media area is where you set up the still images, videos, 360 panoramas and interactive presentations you will export, each saved so you can re-render them after a design change.

The learning curve is gentle by design: the same dozen controls cover most of what you need, and the real-time viewport gives instant feedback on every change, so you learn by seeing rather than by reading manuals. That does not mean the ceiling is low - there is real depth in the lighting, the path tracer, the material editor and the animation tools waiting when you want them - but you can produce a respectable image on your first afternoon, which is exactly why it is such a good on-ramp into real-time work. For the exact current layout and shortcuts, the official Twinmotion documentation is the reference to keep open beside you as you learn.

Twinmotion's strengths follow from what it is. Speed and approachability are the headline: a model becomes a walkable, lit scene faster than in almost any other tool, and the interface does not demand prior CG experience. Its asset library is large and, thanks to Epic's ownership, draws on high-quality game-industry content, so you are rarely short of a tree, a person or a material. Because it is built on Unreal, it also offers a path tracer for higher-fidelity stills when you want to push past the real-time look, plus strong output options: stills, video, 360 panoramas, and interactive presentations you can hand to a client. It runs on Windows and macOS, and it links to the widest set of hosts of any tool in this module, which makes it a safe choice whatever your practice models in. The flip side of that breadth is that it is a separate application to sit beside your modeller rather than a window inside it - a small workflow difference that matters when you compare it with Enscape in the next lesson.

The free-versus-paid question comes up immediately, and the honest answer is: it depends on what you are doing and on the current terms, which Epic changes from time to time. Historically Twinmotion has offered a genuinely capable free tier that lets students and individuals learn, design and explore the full real-time workflow, with the paid tiers unlocking commercial use, higher-resolution and video export, cloud and team features, and the full path-tracing pipeline. The trap to avoid is assuming a free tier covers paid client work - licensing terms for commercial output can differ from the free allowance. So the rule is simple and it protects you: learn on whatever tier is free, but before you deliver paid work, read the current licensing on the official Twinmotion page. The capability you learn transfers regardless of tier; only the rights to sell the output change. Treat the free tier as a full-featured place to build your skill and your studio work, and the paid upgrade as a business decision you make when real client delivery begins - not as a wall between you and learning the craft.