Can't play sound? The illustrated version is right below.
The full narration of the video.
When you play a game, your computer paints sixty fresh pictures every second. Each one gets just sixteen milliseconds. Far quicker than a blink. Let's follow one picture through. Step one, the math: you pressed jump, so where is your character, and where did that bullet go?
Step two, the painting: every one of the thousands of things in view gets colored in. Both steps together have to be handed in within sixteen milliseconds. Make it, and everything looks smooth. Miss it, and that picture arrives late, and you see a hitch.
So optimization isn't buying a faster computer. It's making the same picture take less time. Trick one: if you can't see it, don't paint it. What's behind you, the room behind the wall, the camera can't see them, so skip them. Trick two: keep far things simple. A nearby tree gets every leaf. A faraway tree gets a few strokes. You'd never notice anyway.
Trick three: say it once for things that match. Every instruction costs a little effort. A hundred identical rocks shouldn't take a hundred orders. Trick four: mix the paint ahead of time. Each new kind of surface needs its own recipe for coloring. Mix it only when it's needed, and the picture has to stop and wait.
When some new games hitch as you start, or step into a new area, this is often why. So which trick comes first? People who optimize don't guess. They time it. Whatever step eats the most time gets fixed first. Then measure again, round after round.
A well-optimized game means: it looks just as good, and hands in every picture on time on many more computers. Next time a game stutters, open the settings. Turn the shadows down a notch, and see if it smooths out. If it does, you've just done a little optimizing yourself.
What else has you puzzled? Drop it in the comments, it might be next.
A game isn't a recorded video. Every time you move, the computer has to paint a brand-new picture on the spot.
To look smooth, it paints
about sixty a second.
Like a flip book: flip fast enough and the drawings come alive.
Sixty a second leaves each picture just 16.6 milliseconds, far quicker than a blink. Follow one picture through, and that sliver of time has to cover two jobs:
Make the deadline and everything looks smooth. Miss it and the picture arrives late, so the old one stays on screen a little longer. That's the "hitch" you notice.
Optimization isn't a faster computer. It's making the same picture take less time.
The camera is like a flashlight: it only lights up what's in front. Things behind you, the room behind a wall: they're not in this picture at all, so skip them.
Every dashed box is work this picture saved.
A nearby tree gets painted leaf by leaf. Walk away, and the same tree quietly swaps for a simple version made of a few strokes. It's so small you'd never notice.
Every time the computer gives the order "draw this," it costs a little effort. A hundred identical rocks, ordered one by one, means a hundred orders.
Make it one order:
"draw this a hundred times."
Each new kind of surface (metal, water, hair) needs its own "recipe for coloring." If that recipe is mixed only at the moment it's needed, the picture has to stop and wait.
When a new game hitches as you start or step into a new area, this is often why. It's also why many games spend a while "preparing" when they launch: they're mixing the paint ahead of time.
The first thing people who optimize do is time every step. Whatever eats the most time gets fixed first. Then they measure again, round after round.
"Shadows" is just an example. The slowest step is different for every game and every computer.
Well optimized means: just as good-looking, and on time on many more computers.
Using a sign-up page for a seafood dinner: walls, paint, switches, a shared notebook and a street address, no code required.
Key cards, hotel cards and anti-theft tags are the same trick: a battery-free tag that shouts its number back when a reader pings it.
WebSocket for total beginners: from "ask every five seconds" to "the other side shouts the moment something happens."
The whole toolkit: repos, commits, branches, pull requests, green squares. Treat it as save files in a video game and most of the jargon makes sense.