Your model lands in Twinmotion and it looks like a planning application photographed in a multi-storey car park. Grey everything, a sun directly overhead, a sky like a cheap duvet. That is the default state, it happens to everyone, and it takes about three settings to get out of.
What follows is one project from import to two deliverables — a still and a twenty-second walkthrough. Not a tour of every panel. You will not touch half the software and that is deliberate; the half you skip is where beginners lose a weekend. Where the interface has shifted since the tutorials still sitting at the top of YouTube, I've flagged it, because the 2023 rebuild moved enough that a 2022 video is now actively misleading.
In SketchUp or Revit, check your units are set to something sane and that the model is actually built at that scale. A model downloaded from 3D Warehouse — which is where the Koshino House model we use on our own course came from — can arrive at any size its author fancied. Purge unused components. Turn off anything you will never see: furniture inside a closed box, structural framing, the survey linework.
Then name your tags or layers properly. Twinmotion builds its Outliner from that hierarchy, and if everything comes in as "Layer0" you will spend the rest of the project hunting for the one pane of glass you need to change. The Outliner tree is one of the bigger things the 2023 UI overhaul brought in — older tutorials show a flat scene graph and a very different left-hand dock, so if the video you are following doesn't have a nested tree, it predates the version you installed.
Last thing: face orientation. Reversed faces look fine in SketchUp's shaded view and come into Twinmotion as holes or as the wrong material. In our course material this bites during the interiors every single time — a floor that looks right from above and takes a completely different texture from below.
Import, Then Prove the Scale Before Anything Else
Two routes in. Direct Link, which keeps a live connection to Revit, Archicad, SketchUp, Rhino and friends and pushes changes across as you make them. Or a straight file import, which is a snapshot and nothing more.
Use Direct Link if the design is still moving. Use a file import if the model is signed off, because a live link to a file you are also editing is a reliable way to lose an afternoon to a sync that overwrites your material assignments. That's our habit rather than a rule from Epic, but it has saved us more than once.
Now the scale check, which almost nobody does and everybody should. Drop a human character into the scene next to a door. If the figure's head is level with the handle, your import came in at the wrong unit and everything you do from here — grass height, furniture, depth of field, the lot — will be wrong in a way you can feel but can't name. Fix it at import, not later. Rescaling a populated scene is misery.
The Three Settings That Stop It Looking Like a Default Scene
In this order.
One: change the renderer. The default raster view is fast and it is a liar. Switch to Lumen and the scene gets real-time global illumination — bounce light, contact shadows, interiors that aren't pitch black. In the course videos we flip to Lumen before touching anything else because every judgement you make about materials under raster is a judgement you'll reverse later. Path Tracer is also in that same renderer selector, and it is for final output, not for working. Leave it off for now.
Two: move the sun. Set the real location and a real time of day. Overhead sun is the single thing that makes a render read as "software output" rather than photograph — it flattens every elevation and kills the shadows that describe depth. Drop the sun low, get long shadows raking across your main surface, and rotate the azimuth until the shadows fall where you want them rather than where the geographic truth puts them. Nobody is checking your solar geometry in a portfolio image.
Three: take control of exposure. Auto exposure will average a bright sky and a dark interior into grey mush, and it will drift mid-walkthrough as the camera turns. Set it manually and expose for the thing you care about. We've written up the same problem in Enscape in more detail — the diagnosis transfers directly, and it's worth reading if your images keep coming out lifeless: why your Enscape renders look flat.
Three settings. Two minutes. The scene is now worth working on.
Materials: Big Surfaces First, and Stop Early
The instinct is to start with the interesting stuff — the timber slats, the brass handle. Wrong order. Go after whatever occupies the most pixels: the ground, the main wall, the sky, the glass. Get those four right and the image is eighty per cent there.
For each one, texture scale matters more than the texture choice. A concrete material at default tiling on a six-metre wall reads as sandpaper. Check the scale against something you know — a brick course, a floorboard width, a paving joint — and adjust until it feels like the real thing at that distance. Imports from SketchUp carry their own UV mapping across and it is frequently nonsense on anything that wasn't textured carefully in the host model.
Glass is where interiors live or die. If you can't see through the window from outside, the room behind it is a black hole and the whole elevation goes dead. Push the transparency, drop the reflection a touch, and go look at it from the camera position rather than from wherever you happen to be orbiting.
Then stop. Resist the urge to assign a bespoke material to every skirting board. You have one camera to satisfy, not a model viewer.
Vegetation: Density, Age, Wind Off
The populate tools are at the bottom of the screen and they are the fastest way to make a scene look inhabited or to crash your laptop, depending on restraint.
Foliage gives you paint and scatter. Paint is for deliberate placement — a hedge along the boundary, bamboo against a wall. Scatter is for filling a ground plane. Whichever you use, three parameters do the work: density, which defaults far too low and makes planting look like a municipal car park; age, which controls how grown the asset is and therefore whether your trees look like saplings in a scheme that's meant to be mature; and wind, which you should turn off while you're working because the animation eats frame rate and will make your still render blurry at the edges if left on.
The mistake to avoid is scattering high-poly trees across an entire site context when only a tenth of it is in shot. Fill what the camera sees. Put your vegetation into its own folder in the Outliner so you can hide the lot in one click when the viewport starts to crawl — that organisational habit sounds fussy until the first time you need it.
One Camera, Set Up Like a Photograph
Stop orbiting. Create one camera and commit to it.
Set the aspect ratio to 16:9 before you frame anything, because framing a shot and then changing the ratio crops out the thing you framed for. Put the camera at eye height — roughly 1.6m, not 15m in the air where the mouse wheel left it. Keep the camera level so your verticals stay vertical; a tilted camera gives you converging lines that read as amateur unless you are doing it on purpose.
Then choose a focal length deliberately. Wide angles exaggerate depth and distort anything near the frame edge. Something closer to a 35mm or 50mm equivalent looks like how a person actually sees the building. Save the view. In the current build these live in the Media panel alongside your images, panoramas and videos — another piece that moved in the rebuild, so if your tutorial is pointing at a filmstrip across the bottom of the screen, it's an old one.
Export One Still and One Twenty-Second Video
For the still, switch the renderer to Path Tracer. Leave the denoiser on and max bounces at 10 — you want bounce light moving through the scene. The one thing to change is samples per pixel. What we found while recording our own course is that even the High preset's 256 samples isn't enough for a clean architectural still; push it higher and the denoiser has less work to do. That matters because the denoiser is what quietly eats fine detail — the lacework of a tree shadow goes blotchy long before you notice it on the big surfaces.
Path Tracer needs a ray-tracing capable GPU. Epic's own system requirements list which cards qualify; check before you plan a deadline around it.
The video is where the arithmetic bites. Twenty seconds at 30fps is 600 frames. Render one frame, time it, multiply by 600. If a path-traced still takes several minutes, your twenty-second clip takes days. So: render the walkthrough in Lumen, not Path Tracer. Real-time renderers exist for exactly this. Keep the camera path simple — one slow move, no sudden turns, no orbiting a corner at speed, because fast rotation is what exposes the temporal artefacts in any real-time GI system.
Export the still at full resolution and the video at 1080p. That is your first deliverable set. Done.
What To Do With the Second Project
The thing the first project teaches you is that Twinmotion is quick. The thing the second project teaches you is that quick isn't the same as good, and the gap between a scene that works and a scene that convinces is mostly accumulation — a bit of staining on the stairs, leaves on the ground, something visible through the trees rather than empty sky, planting with varied density instead of uniform carpet.
None of those are settings. They are decisions, made one at a time, over a couple of hours, by someone who has looked at enough photographs to know what's missing. That is learnable and it is worth more than any render preset.
Go and finish a second scene before you read another tutorial.
