In *Fallout: New Vegas*, even 30 FPS is hard to maintain—the truth is even more alarming.

When you return to the Mojave Wasteland at night with headphones on, what hits you first is often not a Deathclaw, nor gunfire, but that strange feeling that the game could stutter at any moment and suddenly lose a chunk of smoothness. It’s like the flickering hallway light in an old horror movie: you know there’s a path ahead, but your footing never feels secure. On second thought, that unease wasn’t just the players’ imagination.

Chris Avellone, one of the principal developers of Fallout: New Vegas, recently recalled that he clashed with Bethesda over performance issues during development. The cause was simple, and rather jarring: in an interview, he was asked whether the game could run at a stable 30 frames per second, and he answered yes. In Avellone’s view, by the standards of the time, 30 fps should have been the bare minimum. But in a meeting afterward, that statement was criticized, with the technical director arguing that no such guarantee should have been made, which came as quite a surprise to him.

But what really unsettled me wasn’t the meeting itself, but the industry reality it revealed: at the time, the development team did not have full confidence in the game’s performance. Avellone pointed the finger directly at the Gamebryo engine, saying it imposed many limitations and already felt outdated back then, making it far from easy to keep the experience stable. It feels a bit like a “slow-boil sense of pressure”—not a sudden collapse in a single moment, but something you become more aware of the longer you play: the ceiling of the underlying technology is right there.

Bethesda later abandoned Gamebryo and turned to its in-house Creation Engine, debuting it in The Elder Scrolls V: Skyrim. Avellone also made it clear that this shift helped Bethesda avoid even bigger technical trouble down the line. To put it with a bit of sarcasm, that also amounts to an indirect admission that the old engine simply could no longer carry the load.

It’s long been no secret that Fallout: New Vegas had poor performance at launch. But what’s even more unsettling is that a game in such a rough technical state ultimately became one of the most beloved RPGs in the hearts of countless players. The reason is also clear: when the systems, storytelling, faction choices, and wasteland atmosphere are compelling enough, players will keep sinking into it while cursing the stutter. That’s not an attempt to whitewash technical problems, but rather to say that games with a real soul often survive their flaws.

If you still want to catch up with it on PC now, Fallout: New Vegas remains well worth playing, especially for players who enjoy branching narratives and wasteland role-playing. Many of its technical issues can now be patched up with MODs, and the experience is far more stable than it was at launch. Unlike games that rely on frequent jump scares to drive the pace, its appeal is more like psychological horror: the aftereffect lingers. It doesn’t stab you at first glance—it’s that many years later, you still remember the dust storms of New Vegas and the cost of its choices.

In the end, the most valuable part of Avellone’s recollection isn’t the phrase “30 frames” itself, but the way it tears back a curtain that veteran players had always vaguely sensed was there: great games are not necessarily born in comfortable technical environments. Sometimes they are more like survivors crawling back from the edge of failure. Fallout: New Vegas is exactly that—wounded, flawed, and yet somehow destined to become a classic.