9 min read

Your First Twinmotion Render, Start to Finish

Give yourself one afternoon and aim at two files: a 16:9 still big enough to print, and a thirty-second clip you'd put at the end of a presentation. Not a tour of the interface — two deliverables. Everything below is in the order you should actually do it, with flags on the places where a tutorial filmed two years ago will send you hunting for a button that has since moved.

One thing to settle before you start. Epic rebuilt Twinmotion on Unreal Engine 5, which is why you now have Lumen for real-time lighting and a Path Tracer for final output. Epic publishes minimum and recommended hardware specs for it — go and read those rather than a forum post, because the short version is that your GPU and how much VRAM it has will decide whether this afternoon is pleasant or a slideshow. Students and educators should also check Epic's own licensing terms before paying for anything; there is an education route and a free non-commercial tier, and the details change often enough that I'm not going to quote them at you.

Free Lesson

Interior Masterclass

1:20:57 · a free lesson from the same area of ArchAdemia

Watch free

Your first launch shouldn't be a treasure hunt

Open it and you get a project browser, not a scene. Start a new project, pick a blank one, and you are looking at an empty landscape with a sun on it.

The layout you see now is dockable. The Outliner — the hierarchical list of every object, light and camera in your scene — lives on one side, the asset Library on the other, and you can drag either of them wherever you like. This is the single biggest thing that dates old tutorials. If the video you're following shows a row of circular icons fixed along the bottom edge for weather, urban context, vegetation and media, you are watching the classic interface and the narration will not match your screen. The functions are all still there. They moved.

Second date-check: the renderer dropdown. You want to know where it is from minute one, because you will be switching between Lumen for working and Path Tracer for output all afternoon. If a tutorial never mentions either word, it predates the Unreal 5 rebuild and its lighting advice is worth very little to you now.

Get the model in, then go and measure a door

Epic ships Direct Link plugins for Revit, Archicad, SketchUp, Rhino and a few others. Use the plugin, not an exported file, for your first project. Direct Link gives you a live connection: change something in the host model, hit sync, and Twinmotion updates in place without destroying the materials and cameras you have set up. Exported files are for collaborators and archives.

The import will go wrong in one of three predictable ways, and all three are faster to fix than to diagnose.

Nothing is where you expect it. The model lands kilometres from the origin because the host file was modelled on real-world survey coordinates. Move the model to origin in the host application, not in Twinmotion. Far-from-origin geometry causes precision wobble in the viewport, and you will blame the renderer for it.

Materials arrive as grey. Procedural or generic materials in the host don't translate — they need an actual bitmap behind them. You're going to re-do the important ones anyway, so don't panic; just note which surfaces came through blank.

Faces are see-through from one side. Reversed normals. In our Koshino House walkthrough this bites on interior wall faces constantly, and the giveaway is a material that looks right in plan and vanishes in the camera. Check the underside and the inside face of anything you've just applied a material to — when a surface comes in looking strange, a flipped face is the first suspect, not the texture.

Now the scale check, and do not skip it. Drop a human figure from the Library next to the building and look at it against a door, a stair riser and a worktop. Not a measured dimension — your eye. A model that came in at a hundredth scale is obvious in two seconds this way and invisible for an hour if you only look at numbers in a properties panel. The same check catches imperial-metric mishaps and the classic SketchUp-component-scaled-by-accident.

a Twinmotion viewport showing a human figure standing beside a doorway in an imported concrete building, used as a scale check

Four settings before anything pretty

The temptation, once the model is in, is to start throwing trees at it. Don't. Four things decide whether the image reads as a photograph, and they all sit in the scene settings rather than the asset library.

Sun position. Set the location, date and time properly. Not because anyone will audit your shadows, but because a sun at 25–35 degrees above the horizon gives you long raking shadows that describe form, and a sun directly overhead gives you a flat grey model with a dark smudge underneath it. The angle of the sun is doing more work than any material you will apply later.

Sky. The default clear sky is a light source as much as a backdrop. A thin, broken cloud layer softens shadow edges and puts variation into the sky behind your building, which matters enormously if your composition has a lot of sky in it. Pick the sky before you judge any material.

Exposure. Turn automatic exposure off and set it manually. Auto exposure is why your walkthrough breathes in and out every time the camera passes a window — it is constantly averaging the frame and re-metering, and it will also quietly flatten every still you take. This is the same failure that ruins Enscape images, and we've gone through the mechanics of it in why your Enscape renders look flat if you want the longer version. Set it once, by eye, with your main camera framed.

Shadow quality. Drop it while you work and raise it before you render. Soft shadow quality is one of the heaviest live settings there is, and working at full quality for an afternoon just to see a shadow edge you'll re-render anyway is a tax on your own patience.

Concrete, glass, ground, timber, metal

Five surfaces sell an architectural image. Everything else is set dressing.

For a Koshino-type scheme that is: the board-marked concrete, the glazing, the ground plane, the interior timber floor, and the metal of the frames and handrails. Spend your material hour on those and leave the rest on whatever came through the import.

What to actually change on each:

  • Texture scale. The commonest reason a render looks like a toy is a brick or board texture tiling at the wrong size. Put the human figure back in shot and scale the texture until the grain is believable against them.
  • Roughness. Nothing outdoors is uniformly glossy or uniformly matt. Concrete that has sat in Japanese weather for forty years has variation across it. A single roughness value across a big plane is what reads as plastic.
  • Bump or displacement, sparingly. Enough that raking sunlight catches the surface. Too much and your concrete turns to porridge.
  • Glass. Get the reflectivity down to something plausible and check what is actually being reflected. Glass with nothing to reflect is a black hole in your elevation.
  • The ground. Students always under-invest here, and the ground is often a third of the frame. Variation in the ground material does more for realism than another tree.

And make folders in the Outliner as you go — vegetation here, furniture there. It feels like admin on a small project. It is the difference between finding things and not finding things on a big one.

The default density is a lie

Twinmotion's scatter and paint tools are genuinely excellent, and the default density is nowhere near what you want. When we paint bamboo around a perimeter in the course, the first pass comes out so sparse it looks like a planting schedule rather than planting; push density up, increase the plant age so you aren't landscaping with saplings, and turn the wind off while you work because animated foliage in the viewport will slow you down for no benefit.

Then the restraint. Place the things that sit in the first third of the frame deliberately, by hand, and scatter the rest. One person at the right distance doing something ordinary beats a crowd. A single car, parked, beats a populated street. The path tools will walk characters and drive vehicles along a drawn route, which is brilliant for a walkthrough and wasted on a still.

The test for whether you have overdone it: hide all the entourage and look at the image. If it is better without, your entourage is covering for a composition problem that entourage cannot fix.

side-by-side comparison of a scattered planting bed at default density and at corrected density with varied plant ages

The still: frame it, then go and make tea

One camera. Create it in Media, set the aspect ratio to 16:9, and resist the urge to make fifteen.

Stand the camera where a person stands and point it at the thing the building is about. Then switch the renderer to Path Tracer and wait, because this is where it stops looking like a game and starts looking like a photograph.

The path tracer settings are simpler than they look. Leave fireflies alone — I have never needed to touch them. Keep max bounces around ten, because bounce light travelling through the scene is most of what you're paying for. Keep the denoiser on, but understand the trade: the denoiser is cleaning up what the samples couldn't resolve, so the more samples per pixel you throw at it, the less it has to invent. Under-sample and denoise hard and you get blotchiness and lost detail — in our own render tests the first thing to go is the fine shadow detail under tree canopies, which turns to mush.

Twinmotion's High path tracer preset sits at 256 samples per pixel. For a final still, we've found that isn't enough. Push it higher and accept the render time. This is the one point in the afternoon where walking away from the computer is the correct professional decision.

Thirty seconds, one path, no drone

A walkthrough is not a flythrough. Create a video in Media, then set keyframes along a route a human could physically take: through the entrance, pause, turn, continue. Eye height throughout. Walking pace throughout.

Thirty seconds is roughly three to five keyframed moves, no more. The two mistakes everyone makes first time are moving too fast and changing direction too sharply — Twinmotion interpolates between your keyframes, so a tight corner becomes a lurch. Add an extra keyframe just before and just after any turn and the curve smooths out.

Check your clip in Lumen before you commit it to a path-traced export. Path tracing a thirty-second animation is an overnight job, and discovering at frame 400 that the camera clips through a wall is a specific kind of misery.

Export sizes nobody tells students

For screen — a portfolio PDF read on a laptop, a presentation, a website — 3840 × 2160 is plenty and most of the time 1920 × 1080 is honest enough.

For print, work backwards from the paper at 300 dpi. An A3 sheet at 300 dpi is about 4960 × 3508 pixels, so render at least that and crop down rather than scaling up. A render that looked crisp on screen and soft on the board is nearly always a render that was exported at screen resolution and stretched.

Export video as a standard MP4 at the frame rate you'll present at, and keep the project file. You will want to come back and re-render that camera at higher samples once you have seen it printed.

The second project teaches you more than this one

Your first Twinmotion image will take an afternoon and will not be as good as the thing in your head. That is fine and expected — the gap closes fast, because almost everything in the list above becomes muscle memory by the third project. What doesn't become automatic is judgement: knowing which five materials matter in a given scene, knowing when to stop planting, knowing that the sun angle was the problem and not the concrete.

Finish the still. Finish the clip. Then open the project again tomorrow with fresh eyes and fix the three things that are obviously wrong. That edit is where the work actually improves.

Written by

Adam Morgan

Architectural Director, ArchAdemia

About the team

Free Lesson

Interior Masterclass

From the same corner of ArchAdemia: watch "Interior Masterclass" free, no account needed.

New guides by email. Course releases, free templates and guides, and software tips worth stealing. One click to unsubscribe.