Three hours, give or take. Twenty minutes importing and proving the scale, ten roughing in a camera so you've got something to judge everything else against, forty on materials, fifteen on the sun, half an hour planting, twenty refining the frame — then you set the still going and make dinner while it cooks. That's the pacing we teach on the beginner course, and what makes it work isn't the settings. It's the order.
At the end of the session you should have two files: one 16:9 still at print resolution, and a twenty-second camera move. Not "an understanding of the interface". Two deliverables.
(If you've landed here because you're in D5 rather than Twinmotion, the diagnosis is almost identical but the panels aren't — that one's written up separately in our piece on the washed-out, plastic look in D5.)
Import the model, then immediately drop a human figure from the library next to a door opening. If their head is level with the head of a 2100mm door, your units survived the trip. If they're knee-high or standing on the roof, stop — fix it at the import dialog rather than scaling the whole model inside Twinmotion, because scaling after you've started painting materials rescales your texture tiling with it.
This is also where you pay a small tidiness tax that saves you an hour later. Imported geometry lands in the Scene Graph as whatever structure your host file had, which for a 3D Warehouse model usually means several hundred entries called Group#17. Right-click, create sub-containers, and sort it into four or five buckets — building, landscape, assets, vegetation. Two minutes. We teach it in the course because every single later problem ("which object is making that weird texture?") becomes a ten-second fix instead of a scrolling expedition.
One more thing while you're in there: if two bits of geometry are meant to be one surface and arrived as two, weld them in the host model and re-import. Coincident faces produce flickering junctions in real time and odd seams in the path tracer. Efficient geometry genuinely does render better.
Where the Buttons Went
This is the bit that makes old tutorials unfollowable, so here's the orientation in plain terms, based on the build we recorded the current course against.
The bottom dock is where the scene-building tools live — landscape, vegetation, the populate and scatter tools, lights, objects, and Media. The important shift is that Media isn't an export dialog you open at the end. It's a container. You create an image, a video, a panorama or a tour as an object in the scene, each with its own camera, aspect ratio and quality settings, and then you export the ones you want. If a tutorial tells you to go to a File menu to render, it predates this and you should close the tab.
Render mode is the second big change. You now choose between Lumen for real-time and the Path Tracer for final quality, and the path tracer's controls — samples per pixel, max bounces, denoiser, fireflies — are attached to the media item's export settings rather than buried in global preferences. A decent rule of thumb: if a tutorial doesn't mention a path tracer anywhere, it was made before Twinmotion moved onto the Unreal Engine 5 generation and the panels it shows you no longer exist.
Materials are edited in the right-hand panel after you pick a surface, and the library drag-and-drop still works the way it always did. That part hasn't moved.
"Plastic" Is Three Problems Wearing One Coat
Everybody writes about glass. Glass is rarely why your exterior looks fake. Concrete, render and metal are, and the cause splits neatly into three.
One: everything shares a roughness value. Importers map your host materials to a generic surface, so painted steel, polished concrete and a rough render all bounce light identically. That uniformity is the plastic look — your eye reads "one material, many colours". Set roughness deliberately, per material, and make the values far apart. Concrete high but never maxed. Metal mid, with reflection doing the work. Timber somewhere between, and different on the end grain if you care.
Two: the texture is tiling at the wrong size. A concrete texture squeezed to 300mm across reads as patterned plastic; stretched to four metres it reads as a photograph of concrete printed onto a wall. Set the texture size to the real thing it represents — a 215mm brick, a 1200mm board, a 600mm block — and the micro-detail lands where the eye expects it. This single fix rescues more renders than any post-processing slider.
Three: no relief and no dirt. Flat normals and clean albedo say "CGI" instantly. Add bump or relief to the big surfaces, drop the saturation a notch, and never leave anything at pure white — off-white, always. Then add the thing nobody does: staining. Water runs off cills and parapets and leaves marks, and in the course we deliberately dirty the stair treads on the Koshino House because clean concrete at 40 years old is a lie.
Glass, since you'll ask: swap imported glass for a library glass material rather than trying to fix opacity on the original, give it a touch of roughness and a faint tint, and make sure there's something inside worth seeing. Perfectly clean glass with an empty black room behind it is the second most common giveaway after flat roughness.
Your Sun Has a Postcode
Set the location, then the date, then the time — in that order, and from the real project, not from whatever looks nice. The default sun sits high and central, which is the lighting equivalent of a ceiling strip light: every surface gets the same dose and nothing casts a shadow long enough to describe form.
What you want is raking light. Low sun, long shadows across the elevation you're showing, with the building's own geometry doing the modelling. If your north point is correct in the host model, Twinmotion's sun becomes an argument — "this is the courtyard at four in the afternoon in April" — rather than decoration. That matters when someone asks whether the terrace actually gets any sun.
Sky next. Fully clear kills the ambient fill and gives you black shadows; fully overcast flattens everything you just gained. A broken sky with visible cloud structure gives contrast and shape, and it puts something in the top third of the frame other than a gradient.
If the image still looks washed out after all that, check exposure before you touch anything else. An over-bright exposure averages your hard-won contrast straight back out, and no amount of material work will rescue it.
Plant Less Than You Want To
Vegetation is where one-sitting renders go to die, because the library is enormous and painting trees is fun. Three rules keep it honest.
Density first: the default scatter density is far too low and reads as a diagram of planting rather than planting. Push it up and vary the age so you don't get a clone army. Turn the wind off — it costs you nothing in a still and causes smeared foliage in path-traced frames.
Species second: two or three types, maximum, plus one hero tree with a bit of character. Real sites aren't botanical collections.
Position third, and this is the one that does the heavy lifting: put something green close to the camera. A branch, a shrub, grass at the frame edge. The eye can only judge depth if it has near, middle and far to compare, and a render where the nearest object is the building thirty metres away always looks like an elevation.
People and cars: fewer than you think, and none of them looking at the camera. The populate path tools draw people walking and vehicles driving along a line you sketch, which is mostly wasted on a still but earns its keep in the twenty-second video — movement in the mid-ground sells a camera move better than the camera move does.
Frame It Like Someone Stood There
Rough your hero camera in early, refine it last. Everything you judge — roughness, sun angle, planting — is judged through that frame, so it needs to exist before the decisions do.
For exteriors, 28–35mm is where buildings look like buildings. Go wider and the corners stretch and the facade bends. Keep your verticals vertical; nothing marks a render as amateur faster than a building leaning back because the camera was tilted up to catch the parapet. If you can't fit the building in without tilting, step back or raise the camera, don't tilt.
Eye height around 1.6m by default, because that's where a person's camera is. Lift it to 2.5m if there's a boundary wall ruining the composition, but be honest that you've done it. Save the frame as a Media image immediately so you can nudge it and always get back.
Path Tracer for the Still, Lumen for the Video
For the hero still, use the path tracer. In the course we leave the fireflies setting alone, keep the denoiser on, and set max bounces to 10 so light actually carries through the scene. The number that matters is samples per pixel, and here's the honest version: the high preset — 256 — isn't enough for a hero image. The denoiser compensates by smoothing, and smoothing is why your crisp tree shadows go blotchy and soft. Push the samples up so the denoiser has less to do, accept the render time, and go and do something else.
4K at 16:9 for the still, or twice the width you intend to print. Oversized gives you crop room; undersized gives you nothing.
For the video, do it in Lumen at high quality. Path-traced animation is a weekend, not a sitting. Twenty seconds, three or four keyframes, one move only — a slow dolly forward, or a slight lateral drift past the facade. No orbits. A camera that moves like a person walking reads as architecture; a camera that swoops reads as an estate agent.
When It Looks Off and You Can't Say Why
Work down this list in order, because the top of it masks the bottom of it: exposure, then sun angle, then roughness variation, then texture scale, then camera height and lens, then foreground depth, then render mode. In practice, nine times out of ten the problem is in the first four and you were about to go and buy a new asset pack.
The first render of your first project will be mediocre. Export it anyway. Finished and ordinary beats unfinished and ambitious, and the second project — same workflow, same three hours — is the one you put on the portfolio.
