We Want Fallout New Vegas 2, But Not Like This

IGN's recent report that Obsidian Entertainment is tentatively gearing up for a new Fallout title-potentially a direct follow-up to the beloved New Vegas-has sent waves of cautious excitement through the RPG community. The project is reportedly led by Josh Sawyer, the game director and lead designer who became synonymous with the 2010 classic. For million of players, New Vegas remains the high-water mark of modern Fallout: a dense, morally ambiguous narrative woven into a reactive world that still inspires mods, retrospectives. And endless debate fourteen years later. On the surface, the idea of Sawyer returning to the Mojave-or some new slice of post-apocalyptic America-feels like a dream come true.

But the timing couldn't be more fraught. The news broke against the backdrop of devastating layoffs at Xbox, Microsoft's decision to close multiple Bethesda studios. And the quiet cancellation of Avowed 2-a project that would have expanded Obsidian's own Pillars of Eternity universe. Now, the same corporate machinery that just eliminated over a thousand jobs is expected to greenlight a sequel to one of the most narratively ambitious RPGs ever made. The dissonance is jarring. What kind of Fallout New Vegas 2 can possibly emerge from a skeleton crew, under the gaze of a parent company that has repeatedly demonstrated it will cut deep to protect quarterly margins? As someone who has spent nearly two decades building and shipping software products-including AAA open-world games-I'm less interested in the hype and more concerned with the engineering reality of making this game in 2025 and beyond.

The Weight of a Legacy: Why Fallout New Vegas 2 Feels Inevitable Yet Elusive

Few games carry the weight of expectation that New Vegas does. It wasn't just a commercial success-it was a statement. Obsidian took Bethesda's Gamebryo-era technology and built a narrative structure so intricate that the game's faction reputation system, dialogue trees. And quest reactivity are still cited as gold standards in game narrative design. To make a sequel now would mean not only living up to that original. But surpassing it in an industry that has fundamentally changed. Players will expect the same depth of choice and consequence. But rendered with modern fidelity, seamless open worlds. And the kind of systemic AI that we've seen in games like Red Dead Redemption 2-all while maintaining Obsidian's signature moral ambiguity.

From a software architecture standpoint, attempting to recreate this on a new engine or even a heavily modified version of the Creation Engine 2 (used by Bethesda for Starfield) is a monumental task. The original New Vegas was famously held together with duct tape and ambition; it shipped with notorious bugs and relied on a thriving modding community to achieve long-term stability. Today's console certification processes and player tolerance for performance issues leave far less room for that scrappiness. The engineering team behind any Fallout New Vegas 2 will need to build a robust, scalable entity-component system capable of tracking thousands of decision variables across a map that might be 5-10 times the size of the Mojave. They'll need to do all of this with a development budget and schedule that has likely already been constrained by the recent layoffs.

Xbox's Layoffs and the Shadow Over Obsidian: A Studio in Flux

When Microsoft cut 1,900 jobs across Activision Blizzard and Xbox in early 2024, followed by additional rounds including the closure of studios like Arkane Austin and Tango Gameworks, the message to remaining developers was clear: no project is safe. Obsidian itself lost staff during these restructurings and while the studio has publicly insisted its active projects (like The Outer Worlds 2 and the fantasy RPG Avowed) remain on track, the cancellation of Avowed 2-a title that reportedly had already entered pre-production-sends a chilling signal. If Microsoft can axe a direct sequel to a well-received game that hasn't even launched, how stable is any greenlit project?

For engineers and designers hoping to pour years of their lives into Fallout New Vegas 2, the risk calculus is grim. Game development is already a field plagued by crunch and short-term contracts; adding the constant threat of sudden studio closures erodes morale and institutional knowledge. The "bus factor"-the measure of risk concentration in critical team members-has skyrocketed. If a handful of senior engineers or the project director leave (voluntarily or otherwise), the whole try could stall. In my own experience leading tech teams through corporate acquisitions, I've seen firsthand how valuable tribal knowledge-unwritten engine quirks, toolchain workarounds, the exact flavor of Lua pinning a quest system together-vanishes the moment a layoff hits. Rebuilding that context takes months, if not years,

Josh Sawyer's Return: The Right Leader at the Wrong Time?

Josh Sawyer is, by any measure, the creative force most intimately tied to New Vegas's identity. His design philosophy, honed on projects like Pillars of Eternity and Pentiment, emphasizes historical authenticity, systemic narrative. And player-driven roleplaying. Bringing him back to lead a Fallout title feels like a no-brainer-except that great game directors aren't miracle workers. Sawyer would be stepping into a production environment with fewer resources, a volatile corporate parent. And an engine ecosystem (likely Starfield's Creation Engine 2) that he didn't personally shape. The original New Vegas succeeded in large part because Sawyer's team had deep familiarity with the Gamebryo codebase, having just shipped Fallout 3 mods and expansions as the studio's initial entry point.

In a modern context, Sawyer would need to quickly assemble a team of engineers, designers. And artists who can not only produce content but also adapt Bethesda's tech to support Obsidian's narrative-first approach. Bethesda's engine is famously opinionated about how world cells load, how scripts execute,, and and how save data is bakedOverlaying a faction reputation system as complex as New Vegas's-where the game remembers not just what you did, but in what order. And for whom-demands a robust backend that probably doesn't exist off-the-shelf. This is where seasoned technical direction becomes critical, and yet the very leaders who might solve these problems are often the first to depart following layoffs or stalled projects.

Game Development Under Duress: What New Vegas 2 Would Demand Technically

To build a worthy successor, the team would need to tackle several hard engineering problems from day one-and they'd have to do so while navigating the fallout (pun unintended) of Microsoft's restructuring. The first is the data persistence layer. In a reactive RPG, every quest state, NPC disposition, and world flag must be stored, queried. And synchronized across threads without bloating save file sizes or causing hitching. The original New Vegas solved this with a flat save format that, by level 40, could balloon to 20 MB and become a loading nightmare. Modern consoles demand fast SSD streaming; a new engine approach-perhaps an ECS with chunk-based delta serialization-would be necessary. Tools like Flecs ECS or Unity's Data-Oriented Technology Stack (DOTS) show the direction the industry is heading. But integrating such patterns into Bethesda's tech stack isn't trivial.

The second challenge is NPC AI and scheduling. New Vegas introduced a faction disguise system and dynamic combat alliances; a sequel would need to expand that into a living world where characters have daily routines - emotional states. And memories that persist across in-game days. Implementing this in a large open world without overwhelming the CPU is a distributed systems problem in miniature-you're essentially writing a scheduler that must gracefully degrade when too many actors are awake. In my own work porting AI systems between engines, I've found that maintaining determinism while achieving 60 fps on console often means leaning on precomputed pathfinding meshes and behavior tree blackboards that are carefully scoped. Without enough senior AI engineers-and with the specter of more layoffs-the team might be forced to compromise on exactly the features that made the original special.

The Creation Engine Conundrum: Can Obsidian Build on a Fractured Foundation?

Any discussion of a new Fallout game inevitably circles back to the game engine. Bethesda's Creation Engine 2, as seen in Starfield, is a deeply idiosyncratic piece of technology. It excels at object permanence, modular worldstreaming. And a heavily data-driven content pipeline that empowers designers. But it also suffers from long-standing issues: script latency, a notoriously slow cell-loading process. And animation blending that hasn't kept pace with industry leaders. For a studio like Obsidian-which has built its recent titles in Unreal Engine (The Outer Worlds) and Unity (Pillars of Eternity, Pentiment)-returning to a Bethesda-derived codebase means re-training a workforce on tools that the wider industry doesn't use.

This isn't just a matter of preference; it's a question of scalability and hiring. Unreal Engine 5 has become the de facto standard for AAA development, with a vast talent pool, robust documentation. And an asset marketplace that accelerates prototyping. Forcing Obsidian's engineers back into the Creation Engine ecosystem would limit their ability to hire experienced developers who can hit the ground running, and it would increase the cost of every external collaboration. Moreover, the engine's networking model (if the game includes any cooperative or live-service components) is effectively a black box to anyone outside Bethesda's Maryland studio. Without direct, sustained access to Bethesda's engine team-something that becomes less likely when corporate is busy closing studios-Obsidian could find itself fighting the tools instead of building the game.

Scoping the Wasteland: The Danger of Overpromising in a Live-Service World

One of the most troubling questions surrounding the rumored Fallout New Vegas 2 is whether it might be saddled with live-service requirements. Microsoft's gaming division has made no secret of its appetite for recurring revenue, as seen with Sea of Thieves, the Minecraft marketplace. And the aggressive post-launch plans for Halo Infinite. An open-world RPG that ships as a complete single-player experience-like the original New Vegas-is increasingly seen as a missed opportunity for "monetizable engagement" in executive circles. If the new project is greenlit with a mandate to support post-launch seasons, battle passes, or cosmetic shops, the engineering trade-offs multiply catastrophically.

From a software perspective