CRASH LANDING: THE BEAUTY OF FAILING SPECTACULARLY

The first time I watched my friend Marcus play BeamNG.drive, he spent twenty minutes building a perfect highway scenario. Four lanes, a concrete barrier, a cargo truck merging from an on-ramp, a hatchback doing ninety in the fast lane. He queued it up, hit simulate, and the hatchback clipped the truck's rear bumper, tumbled across three lanes, peeled its own roof off on the barrier, and came to rest upside down in the grass with one wheel still spinning. Marcus did not say anything for about four seconds. Then he said, "oh my god," and reloaded the scenario to run it again from a different camera angle. He watched that crash seventeen times. He never once ran the scenario with the two cars missing each other.

That's the whole essay right there, but I have two thousand more words to fill so let me keep going.

The crash is the content

There's a specific category of video game where failure is not a punishment. Failure is the product. You paid money, or you clicked the ad, or you downloaded the demo, because you wanted to see things break. Landing the plane is a nice bonus. Crashing the plane is the reason you booted the game up.

This inversion is so common now that I think we stop noticing it. Getting Over It with Bennett Foddy is built around the feeling of losing an hour of progress, and the falling is the part that gets clipped and shared. Surgeon Simulator's entire brand is your inability to perform the surgery. Hardspace: Shipbreaker gives you industrial equipment that can kill you in forty-seven distinct ways, and the death animations are so well animated that speedrunners have made careers out of them. Goat Simulator's physics bugs were left in on purpose because the bugs are funnier than the intended behavior. Just Cause 4's parachute exists so you can deploy it six feet above the ground and splatter yourself into a billboard.

None of these are accidents. Someone at the studio made the deliberate choice that the failure state would be more entertaining than the success state, and they built the rest of the game around that choice. This is a hard call to make because it violates the default assumption of game design, which is that games should reward you for playing well. A game where you are rewarded for playing badly feels paradoxical. But it works. It works so consistently that I think it should be the default assumption for certain genres instead of the exception.

Why crashing feels good

The neuroscience here is not complicated. Humans are attention-seeking creatures, and catastrophe is attention-grabbing. A plane landing safely looks like a plane landing safely. A plane crashing into a terminal looks like a plane crashing into a terminal, and you cannot look away from the second one. This is why news channels lead with disasters and why cars slow down to rubberneck accidents. We are wired to pay attention to things that go wrong because in our ancestral environment, things going wrong was information we needed to survive.

Video games exploit this in the safest possible way. You get to watch the catastrophe without any of the consequences. Nobody is hurt. Nothing is broken except pixels. The emotional hit of witnessing a spectacular failure is available at zero cost. That's a pretty good deal, and it's why slow-motion replay buttons have been a standard feature in driving games for thirty years. The developers know you want to watch the crash. They built you a replay system specifically to make that easier.

There's also a secondary hit, which is the feeling of having caused the catastrophe yourself. A car crash in a movie is entertaining. A car crash in a game that you caused by hitting the wrong button is entertaining plus a weird sense of ownership. You broke that. You authored that destruction, even if you authored it accidentally. The game gave you a tool, you misused it, and the game responded with a physical consequence that is directly traceable to your input. That traceability is the difference between watching a crash and being responsible for one, and responsibility is where the comedy lives.

Exaggerated physics as a design principle

Realistic physics are a problem for crash entertainment. A real car crash is not funny. It is a grim, short, violent event that usually ends with injured people and insurance paperwork. Nobody wants to play a game about a real car crash. The games we're talking about all lean away from realism in the direction of exaggeration.

BeamNG is interesting because it is technically a realistic soft-body simulator. The engineering underneath it models chassis deformation and panel flex with the kind of accuracy that companies use for actual vehicle design. But the way BeamNG's community uses it is not realistic at all. They launch semi-trucks off ramps into skyscrapers. They build compound pileups of forty cars. They drop school buses from orbit. The simulator is accurate, but the inputs are so far outside realistic parameters that the outputs become slapstick. A soft-body simulation of a semi-truck hitting a building at three hundred miles per hour is not a crash, it is a disassembly procedure.

Other games go the other direction and just make the physics dumber. Goat Simulator's ragdolls have too little mass. Just Cause's parachute catches wind that doesn't exist. Surgeon Simulator's hand is controlled through a rig that actively resists your inputs. These games are not simulating anything real. They are simulating a cartoon version of physics where impacts are springier than they should be, limbs are floppier than they should be, and every collision sends some part of the scene spinning off into the middle distance.

Both approaches work because both approaches produce results that are visibly different from reality. The player's brain registers that something is off, something is wrong, something is not how things usually go, and that registration is the first step toward laughing at it. You don't laugh at accurate simulations. You laugh at accurate simulations that have been pushed past their breaking point, or at inaccurate simulations that have been tuned to break in comedic directions.

Delayed consequences and the slow-motion camera

A great crash needs to breathe. This is a principle I learned from watching my own game's playtests back when I was working on a racing title about a decade ago. We had a wreck detection system that would slow the game to twenty percent speed for two and a half seconds when a major collision happened, then pull the camera back and orbit slightly to give you a better view. Players loved that feature. We pulled the feature in a later build to save performance, and the same players told us the game felt worse, even though they couldn't articulate why. The crashes were the same crashes. They just weren't getting time to watch them.

Every great crash game I can think of has some version of this. Burnout was the most famous example, with its Crashbreaker mode that explicitly existed to make wrecks longer and more destructive. BeamNG has a replay system that lets you scrub through the impact frame by frame. Hardspace: Shipbreaker pauses you in slow motion when a pressurized hull ruptures so you can appreciate the exact moment your workplace accident goes terminal. Even Getting Over It has a version of this, where the camera follows Diogenes down the full length of his fall and gives you time to register exactly how much progress you just lost.

The delay is important. If the consequence happens too fast, you don't get to process it. If the consequence happens too slow, it feels punitive. The sweet spot is somewhere around one and a half to three seconds of reduced-speed carnage, long enough to register what happened but short enough that you still have momentum going into the next attempt. This is a timing problem more than an art problem, and studios that nail it are studios where someone on the team understood that the crash is the content and budgeted animation time accordingly.

The skill of controlled failure

Here's the weird part. These games are about failure, but they still reward skill. The skill is just pointed in a different direction than in a normal game.

In a normal game, the skill is executing clean. You press the right buttons at the right times, you clear the level, you get a high score. In a crash game, the skill is executing dirty with intent. You learn the physics well enough that you can produce specific failure shapes on demand. You set up a BeamNG scenario where you know the semi will jackknife at exactly the right angle. You line up a Just Cause parachute sequence that puts you through three helicopters on the way down. You time a Surgeon Simulator grab so that the heart flies into the sink instead of the floor. The inputs are imprecise on purpose, but the outputs are being shaped by a player who has internalized the imprecision.

This is the same skill curve as a clean-execution game, just oriented around a different end state. Beginners crash randomly. Intermediate players crash frequently but repeat similar-looking crashes. Advanced players produce crashes that are specific, elaborate, and camera-ready. There's a whole subculture of Goat Simulator content creators whose entire craft is engineering specific ragdoll arrangements that look like they were storyboarded. They were storyboarded. The storyboard just exists in the player's head.

I think this is why crash-friendly games have such long tails on engagement. A normal game has a skill ceiling that corresponds to executing the intended content perfectly. A crash game has no such ceiling because the intended content is an open-ended set of failure states, and there's always a new failure state you haven't produced yet. BeamNG has been in early access for over a decade and its community is still inventing new ways to crash because the physics engine can always produce a crash nobody has seen before.

Hardspace and the crash as narrative

Hardspace: Shipbreaker deserves its own section because it does something weirder than the others. The game is about cutting up derelict spaceships for parts, and the failure states are not just catastrophic, they are educational. You cut the wrong bracket and a pressurized module explodes. You cut the wrong fuel line and the ship bursts into flame. You get too close to a live reactor and you die of radiation poisoning over the next thirty seconds, giving you plenty of time to contemplate your mistake.

What makes this work as failure entertainment is that every crash teaches you something specific. The game is a crash tutorial where the lessons are written in your own dismemberment. After a few dozen hours, you've internalized the ways ships can go wrong, and your ability to not-crash becomes a genuine skill that feels earned. But you never stop appreciating the crashes. The game respects you enough to let its disasters actually be disastrous. No rewind button. No undo. If you screwed up, you screwed up, and the screwup gets rendered in full detail while you're paying attention to it.

This is what I think a lot of crash-friendly games miss. The crashes have to matter. If crashing has no cost, then the crash is just entertainment for its own sake, which is fine but limited. If crashing actually sets you back, resets your progress, costs you something real, then the crash carries emotional weight. You're not just watching destruction. You're watching your own labor being consumed by physics. That's a more interesting feeling than pure slapstick.

How this applies to This Is Your Captain

Since I'm writing this blog on my studio's website, I should probably say something about my own game. This Is Your Captain is an arcade flight game about a comically unqualified pilot, and it lives in this crash-friendly design space by default. The plane has a health bar. The passengers have opinions. The autopilot is broken in specific directions. If I did my job right, the crashes in this game will be the part people clip and share, not the clean landings.

That was a decision I made early on and it changed almost everything about how I built the systems underneath. I could have built a realistic flight sim and called it a day, but a realistic flight sim produces realistic crashes, and realistic crashes are just sad. Instead I tuned the flight model so that the plane behaves like a real plane right up until it doesn't, and when it doesn't, the physics become springy and silly and full of unexpected bounces. You meant to execute a go-around and you ended up cartwheeling through an airport food court. That's the game. The food court is the content.

The principles I keep coming back to are the same ones that make all these other games work. Exaggerate the physics past the point of realism, because realism is not funny. Give the crash time to breathe, because a crash you can't see is not a crash. Let the player feel responsible for the disaster, because ownership is where the comedy gets its weight. And make sure the failure state is visually different every time, because repeated crashes are not funny, but novel crashes always are.

There's a real lineage here. Bennett Foddy's cauldron falling all the way to the bottom of the mountain. A goat flinging a tourist into orbit. A semi-truck folding itself around a lamppost. A surgeon waving a heart around a sterile operating theater. These games understood that the thing the player wanted to see was not the perfect performance. It was the spectacular failure, rendered with love, delivered with timing, shown from a good angle. If you can build a game that treats failing as the reward instead of the punishment, you've built a game people will keep coming back to long after they've stopped trying to win.

My nephew is eleven now. He's too cool to play Crazy Plane Landing anymore. He plays BeamNG. He still crashes every time. He still laughs every time. The game changed. The loop did not.