KS3 · Computer Science
Creating a 3D animation
Pause any animated film and you're looking at a still picture. So does an animator really pose every object in every frame? Almost never, and the trick is brilliant.
Computer Science · Algorithms
Trace table — dry run the code
A ball slides across the screen. The animator records just two keyframes. Step through and watch who fills in the rest. (Example frame rate: 10 frames per second.)
Ready when you are — step through one line at a time.
3D modelling · meshes
Layers
Explore
Turn the Faces layer off to see the cube as a wireframe, then explore each part.
The same cube after its four top vertices were moved inwards.
A 3D object isn't a solid lump. It's a surface built from points, lines and flat faces.
WHAT YOU'VE LEARNED
A quick recap of today's lesson.
You set a few key moments. The computer works out every frame in between, and then draws every single one.
What you need to know
- An animation is a sequence of still frames shown quickly one after another; the frame rate is how many frames are shown each second.
- The animator records keyframes (an object's position, rotation or scale at chosen frames) and the software calculates the in-between frames.
- 3D objects are usually meshes made of vertices, edges and faces, often built by editing simple primitives.
- Objects sit in a space with x, y and z axes and are changed by translating, rotating and scaling.
- Materials and textures, lights and the camera set how a scene looks; rendering calculates every final frame from them.
The big picture
An animation is a sequence of still frames shown quickly, and the frame rate says how many are shown each second. In 3D animation the animator records keyframes and the software calculates the in-between frames. The objects are meshes of vertices, edges and faces, changed by translating, rotating and scaling them along the x, y and z axes. Materials, lights and the camera decide how the scene looks, rendering calculates every final frame, and the whole project is planned for an audience, then tested against the plan and improved.
Key points
Worked example
Problem
A door in your scene needs to swing open by 90° over 2 seconds. Your project runs at 24 frames per second, and the door starts closed on frame 0. Which frames should you make keyframes, how many frames will the software calculate, and what angle will the door be at on frame 24?
⚠ Watch out
Thinking the animator has to move the object on every single frame. The animator only records the keyframes; the software calculates all the frames in between.
Memory hook
You set the keys, the computer fills the gaps, then the render draws every frame. Keys → gaps → draw.
Check yourself
A character's jump lasts 3 seconds at 20 frames per second. How many frames is that, which would you set yourself, and why does rendering it still take a while?
Flashcards
(12)What is a frame?
What does the frame rate tell you?
What is a keyframe?
Who makes the in-between frames, and how?
What are the x, y and z axes?
What is a mesh?
What is a primitive, and how does it become a complex model?
Translate, rotate, scale: what does each change?
Material or light: which gives an object its colour and shine?
What does the camera decide?
What is rendering, and why can it be slow?
What do you evaluate a finished 3D animation against?
Tap any card to flip it, or use Study as deck to go through them one at a time. In the full lesson these run as a spaced-repetition deck — you rate each card Hard, Good or Easy and the tricky ones keep coming back until they stick.
Learning with Lightbulb is opening soon
You can use this lesson now. Join the waitlist and we'll let you know when the full Lightbulb experience is ready.
Keep me postedMore KS3 Computer Science topics
- Abstraction in computational thinking
- Adding binary numbers
- Binary to denary conversion
- Boolean logic: AND, OR, NOT
- Bubble sort
- Building truth tables
- Client-server vs peer-to-peer
- Collecting and recording data
- Comparing sorting algorithms
- Compressing data
- Decomposition: splitting problems up
- Designing a mobile app
How this lesson was checked. This KS3 Computer Sciencelesson was published through Lightbulb Learning's human-designed editorial process — the educational standards, accuracy rules and publication checks it must pass were authored and approved by Philip Halpin. It passed subject-specific assessment, automated educational checks and technical publication verification before going live (publication checks completed 30 September 2026). Published pages are monitored, human spot-checking is ongoing across the lesson library, and anything found wrong is corrected or withdrawn. How our lessons are made and checked. Spotted a mistake? Email hello@lightbulblearning.co and we'll review it.