Architectural Walkthroughs & Flythroughs

First, a distinction. A walkthrough keeps the camera at roughly human eye height and moves at roughly human speed - it is the experience of a person moving through the building, and it is what sells how a space feels. A flythrough frees the camera into the air - sweeping over a masterplan, orbiting a tower, rising past a facade - and it sells form, scale and context. Most presentations use both: a flythrough to establish the object in its world, walkthroughs to inhabit it. Choose per shot; a flythrough of an intimate interior feels wrong, and a ground-level walk cannot show a whole campus.

Either way, plan before you rig. Sketch a shot list - a handful of shots, each with a purpose: the approach, the entry threshold, the reveal of the main volume, a key interior, a signature detail. For each, note the camera type (walk or fly), the lens, and roughly how long it holds. This is storyboarding, and it takes twenty minutes on paper but saves hours of aimless camera-wrangling. The question for every shot is not can I get the camera there, but what is this shot for - what does the viewer understand after it that they did not before.

Think about the audience and the platform while you storyboard, because they change the shots. A film headed for a phone screen wants tighter, simpler compositions and slightly faster cuts than one for a boardroom projector; a piece that loops silently in a foyer must make sense without narration; and anything that might later become a VR or interactive experience should avoid moves that would feel sickening in a headset. Note, too, how each shot connects to the next - a cut is instant, but a continuous move from one space into another has to be physically possible, so a path that walks through a door reveals the plan behind your shot list. Twenty minutes of this planning is the cheapest quality you will ever buy: it turns a vague intention to 'make a walkthrough' into a concrete list of five or six shots you can rig, time and judge one by one.

Hand-keyframing a long, smooth camera path is fiddly. Unreal gives you a purpose-built tool: the Camera Rig Rail, an actor that is a spline - a curved path you draw through the scene by placing and shaping control points. You attach your Cine Camera to the rail, and instead of keyframing the camera's position directly, you animate a single value - the camera's position along the rail (0 to 1, start to end) - in the Sequencer. The camera then glides along your drawn path, and because a spline is inherently smooth, the motion is smooth by construction.

This separates the two hard problems. The path is a spatial design you shape in the viewport - route it down the corridor, curve it around the column, hold it clear of walls - and can tweak endlessly without touching the timing. The timing and speed are the single rail-position track in the Sequencer, which you ease exactly as you learned in the last lesson - slow to start, glide, gentle stop. You can also independently animate where the camera looks (aim it along the path, or lock it onto a subject with a look-at target) so the camera tracks a facade while travelling past it. For rises and craning reveals, the sibling Camera Rig Crane actor mimics a real jib - arm length, height and rotation - giving that classic lifting-and-revealing move without hand-keying an arc.

A couple of practical rail tips save real grief. Keep the spline's control points few and evenly spaced - a path described by a handful of well-placed points is smoother than one crammed with them, which tends to introduce subtle speed changes and wobble as the camera negotiates each point. Watch the camera's height along the whole travel, not just at the ends: a rail that dips or rises unintentionally between points reads as a drift, so keep it level at about eye height unless a change is deliberate. And decide early how the camera should aim - locking a look-at target onto a facade or a focal object makes the camera track it like a real operator panning to hold a subject, far more compelling than a camera that stares straight down its direction of travel. For the airborne flythrough the same rail works, just routed through the air and often paired with a longer lens to compress and flatter the massing.

The most common walkthrough mistake is speed. Cameras fly too fast because the author, who knows the building intimately, is impatient - but the viewer is seeing it for the first time and needs time to read each space. A walkthrough should move at roughly walking pace or a touch slower, and hold on important moments. Rushing a space communicates nothing; the viewer arrives at the far wall before they have understood the room.

Build in holds and breaths. Let an establishing shot rest for four to six seconds before anything moves. Slow further at a threshold or a reveal so the moment lands. Ease every start and stop so the camera never lurches. And mind motion comfort: avoid fast pans, sudden direction changes and rapid vertical moves - they read as uneasy even on a flat screen and can be genuinely nauseating if the piece is ever shown in VR (Module 8 covers comfort in depth). A good rule is that the camera should move the way a thoughtful person with a Steadicam would move - deliberate, level, unhurried - not the way a drone or a first-person shooter does. Cut rather than whip: if you need to be somewhere else, a clean cut on the Camera Cut track is calmer than a fast fly-over.

Architecture is experienced as a sequence in time - the procession from outside to inside, from compression to release - and the best walkthroughs script exactly that. A reliable structure is: approach (establish the building in its context, often a flythrough or a low wide walk), arrival and threshold (slow at the entrance - the door, the porch, the compression of a narrow entry), the reveal (the camera crosses the threshold and the main volume opens up - this is the emotional peak, so pace it slowly and let the space breathe), then inhabitation (move through the key rooms at human pace, showing how the space is used), and finally details and closing (a signature material, a framed view, a last wide that leaves the viewer with the whole).

The reveal is the money shot, and it rewards deliberate craft: hold the compression a beat longer than feels comfortable, then release into the volume slowly, perhaps with a crane rise so the ceiling height lands. This mirrors how great buildings actually work on the body - Barragan, Kahn, a stepwell, a temple mandapa all play compression against release - and a walkthrough that honours that rhythm feels like architecture rather than a real-estate flythrough. Coordinate the other Sequencer tracks with the story: a door opening as you reach it, the light warming as you enter, furniture that reads as lived-in. The camera path is the sentence; the reveal is where it means something.

Getting the reveal to land is mostly about contrast and timing. The release feels bigger when the approach genuinely compresses first - a lower ceiling, a narrower frame, a darker or cooler light before the volume opens - so build the tension deliberately rather than starting wide. As the camera crosses the threshold, slow it further and, if the space is tall, add a gentle crane rise so the ceiling height is disclosed by the move itself; the eye reads height most powerfully when the camera lifts to reveal it. Give the volume a hold once it is open - a beat of near-stillness lets the space register before you move on - and consider letting a supporting beat coincide with the peak, a shaft of light reaching a wall or a door settling open, so several elements resolve together. That is the difference between a walkthrough that documents rooms and one that stages the experience the architecture was designed to give.