Unit IIComputer Studio III

Animations & Walkthroughs

Moving the camera — and the render-time cost most students under-estimate.

≈ 35 min + studio task

A still shows a moment; a walkthrough shows the experience — scale, flow and light in motion. This unit builds the moving camera and teaches the lesson every student learns the hard way: an animation is hundreds or thousands of frames, so its render time is frames × per-frame time. Real-time engines turn days into minutes; then you edit, score and present.

Learning objectives

By the end of this lesson, you will be able to — mapped to the course outcomes for Computer Studio III:

CO2 · Understand

Explain the architectural walkthrough and fly-through and their purpose in communication.

CO2 · Apply

Set camera paths, keyframes and easing using the dolly, pan and orbit moves.

CO2 · Analyse

Calculate the render-time cost of an animation (frames × per-frame time) and choose real-time vs offline.

CO6 · Apply

Sequence, edit and score a walkthrough into a finished presentation video.

Walkthrough, keyframes, moves

Moving the camera

A walkthrough (eye-level) or fly-through (aerial) conveys spatial experience a still cannot; build it with keyframes, easing and the dolly-pan-orbit moves — and approve the path before you render.^{[6, 1]}

DiagramA smooth camera path curving through a building with keyframes marked, and the dolly, pan and orbit moves

Moving through the design

A WALKTHROUGH is an eye-level moving-camera animation through an unbuilt design; a FLY-THROUGH is the aerial version, over and around it. Their purpose is communication — conveying the spatial experience (scale, flow, the sequence of spaces, light and material in motion) that a single still cannot show. It is the most persuasive way to present a design to a client who cannot read drawings.^{[6, 1]}

Frames, render time, post

The cost — and the cut

Total frames = seconds × fps (a 90-second clip at 30 fps is 2,700 frames); render time = frames × per-frame time — the cost students under-estimate.^[1] Real-time engines export in minutes; then you storyboard, edit and score the clip.

DiagramThe render-time math — total frames equals seconds times fps, so 90 seconds at 30 fps is 2700 frames

fps and the frame count

FRAME RATE: 24 fps gives the cinematic film look, 30 fps is the arch-viz standard, 60 fps is smoothest (mainly for VR). Clients usually cannot tell 30 from 60 in a walkthrough — and 60 doubles the frame count and render cost. RESOLUTION: 1080p (1920×1080) is standard, 4K (3840×2160) for hero or print. Total frames = duration in seconds × fps.^[1]

DiagramOffline rendering taking days versus real-time rendering taking minutes for the same animation

The animation facts

At a glance

Aspect	One	The other
Output	Still: one image	Animation: total frames = seconds × fps (hundreds–thousands)
Frame rate	30 fps: arch-viz standard, half the cost	60 fps: smoothest, doubles frame count & render time
Render approach	Offline: photoreal, huge time cost (render farm)	Real-time: minutes not days, slightly less accurate
When to fix the camera	Before rendering (storyboard)	After rendering = re-render every frame (costly)
Deliverable	Raw rendered frames	Edited, scored video (cuts, sound, pacing)

Vocabulary

Key terms

Walkthrough / fly-through

An eye-level (walkthrough) or aerial (fly-through) moving-camera animation through a design.

Keyframe

A frame where camera position/target is set; the software interpolates the frames between keys.

Easing

Smoothing the acceleration and deceleration of a camera move so motion is not jerky.

Dolly / pan / orbit

Camera moves — dolly (forward/back), pan (rotate in place), orbit (revolve around a subject).

Frame rate (fps)

Frames per second — 24 (film), 30 (arch-viz standard), 60 (smoothest, VR).

Total frames

Duration in seconds × fps — the number of images the animation must render.

Render farm

Many networked machines rendering an animation's frames in parallel to cut wall-clock time.

Storyboard

A pre-planned map of camera path, viewpoints, transitions and pacing, made before 3D work.

Apply it

Studio task

Storyboard a 30-second walkthrough of one space — sketch the camera path and three key viewpoints — and calculate its total frame count at 24, 30 and 60 fps. Then estimate the offline render time at 15 minutes per frame, and say why you would render it real-time instead.

Check your understanding

Self-assessment

1. A 90-second walkthrough at 30 fps requires rendering —

2. Easing in camera animation refers to —

3. The main advantage of a real-time engine for a walkthrough is —

In a nutshell

Recap

A walkthrough (eye-level) or fly-through (aerial) conveys the spatial experience a still cannot — the strongest way to present to a client.

Build the camera with keyframes, easing and the dolly-pan-orbit moves — and approve the path before rendering.

An animation is total frames = seconds × fps (a 90-second clip at 30 fps = 2,700 frames); render time = frames × per-frame time — the cost students under-estimate.

Real-time engines turn days into minutes; then storyboard, edit and score the clip into a finished video.

The evidence

References & further reading

[1]3D Praxis Studio — Architectural Animation Guide (walkthroughs, camera, fps, render-time).
[2]Blender Manual — Animation & the Video Sequence Editor. Blender Foundation. https://docs.blender.org/manual/en/latest/
[6]Epic Games — Twinmotion Documentation (real-time animation export). https://dev.epicgames.com/documentation/en-us/twinmotion/twinmotion-documentation