The editorial frames the cut as 'the software equivalent of firing your platform org and telling product to keep shipping.' It argues engine work compounds across generations — the megatexture code in idTech 5 informed virtual texturing in idTech 7 and GI in idTech 8 — so severing that lineage destroys institutional knowledge that game teams depend on.
The editorial argues idTech is one of very few AAA-grade renderers not built on Unreal or Unity, and has served as a proving ground for graphics techniques that later spread industry-wide. It cites Doom Eternal's Vulkan renderer hitting 60fps on Switch and 1000+ fps on high-end PCs from the same codebase as a portability feat Unreal 5 still cannot match — making the team's dismissal a loss for the broader industry, not just id.
The submitter surfaces a gamefromscratch report based on community reporting and developer social posts, noting Microsoft has not publicly confirmed the composition of the cuts and id Software has issued no official statement. The 200-point score and 194 comments suggest the community reads the conspicuous silence from Redmond as tacit confirmation of a badly handled decision.
Microsoft's latest round of Xbox layoffs — roughly 9,000 people across Microsoft Gaming, announced in early July — landed hard on id Software. According to reports circulating on Hacker News and gamefromscratch, the entire idTech engine team was cut. idTech is the in-house engine lineage that has shipped every id Software title since the original Doom in 1993, through Quake, Rage, Doom (2016), Doom Eternal, and Doom: The Dark Ages.
The engine group is separate from the game teams. A game team ships one title every few years; the engine team maintains the renderer, the tools, the asset pipeline, and the platform abstraction layer that every game team then builds on. Cutting the engine team while keeping the game teams is the software equivalent of firing your platform org and telling product to keep shipping.
Microsoft has not publicly confirmed the specific composition of the cuts at id, and id Software has not issued an official statement about the engine team's status. What we have is community reporting, developer social posts, and a conspicuous silence from Redmond. The scale of the Gaming layoffs — the largest in Microsoft's history for that division — is not in dispute.
idTech is not just another engine. It is one of a very small number of AAA-grade renderers not built on Unreal or Unity, and it has been a proving ground for graphics techniques that later showed up everywhere else. Doom Eternal's Vulkan renderer hit a steady 60fps on a Switch and 1000+ fps on high-end PCs from the same codebase — a portability story Unreal 5 still cannot match at that frame budget. The team behind that work is the one Microsoft just let go.
There is a real question of institutional knowledge here. Engine work compounds. The person who wrote the megatexture streaming code in idTech 5 informed the virtual texturing in idTech 7, which informed the GI system in idTech 8. When you fire that lineage, you don't just lose people — you lose the mental model of why the code is shaped the way it is. Bethesda and id have been burned by this before: the Starfield engine (Creation Engine 2) shipped with well-documented streaming and physics issues that longtime Bethesda engine engineers had reportedly flagged and left over.
The community reaction has been unusually blunt. John Carmack, id's co-founder, has publicly noted over the years that he was skeptical of the ZeniMax acquisition and later the Microsoft acquisition for exactly this reason: platform teams get cut first when a corporate parent looks for margin. On Hacker News, the top comments are converging on the same read — this is what happens when the acquirer decides the engine is a cost center rather than a strategic asset, and it almost always precedes a forced migration to Unreal.
Compare the trajectory with what happened at other acquired studios. Crytek's CryEngine team was gutted after successive restructurings; the engine now survives mostly as a licensing shell. Frostbite at EA had its central engine team downsized in 2023 and studios were quietly told to consider Unreal for new projects. The pattern is clear: bespoke engines are expensive, and the moment a parent company decides Unreal is "good enough," the in-house team's headcount is the first line item to go.
If you are one of the studios still licensing idTech or shipping on a fork — MachineGames' Wolfenstein and Indiana Jones and the Great Circle both use it, Tango Gameworks' The Evil Within used earlier versions, Arkane's Dishonored ran on a heavily modified idTech 5 — this is a supply-chain incident. Treat it exactly like an upstream open-source project going unmaintained: audit what you depend on, freeze the version you're on, and start planning migration paths now, before you have a shipped title stuck on a dead runtime.
For graphics engineers who used idTech's public talks as a reference — the SIGGRAPH papers on clustered forward rendering, the id Tech 6 Vulkan post-mortems, Billy Khan and Axel Gneiting's rendering deep dives — the practical impact is that the pipeline you've been learning from just lost its authors. The talks will still be online. The follow-up work won't happen.
There is also a broader lesson for anyone working inside an acquired company with a specialized platform team. Engine teams, infra teams, developer-tools teams, and internal frameworks teams all look the same on a spreadsheet: high salary cost, no direct revenue line, replaceable by an off-the-shelf option. If your team's value is legibility to product managers rather than a P&L number, the acquisition scenario is a liability. The engineers at id who built the fastest AAA renderer on the market are not exempt from that math.
The most likely outcome is that id's next Doom or Quake ships on a maintenance-mode idTech, and the one after that ships on Unreal 5 or Unreal 6. Microsoft has signaled repeatedly that it wants a smaller number of engines across its first-party studios; the Activision Blizzard acquisition brought in another set of proprietary engines that Redmond will want to consolidate. Losing the idTech team is not the surprise — the surprise is how quickly the calculus flipped from "strategic asset" to "cost center" after the ZeniMax deal closed in 2021. For developers watching from outside, the takeaway is unromantic but important: the engine that runs at 1000fps is only as durable as the org chart that funds it.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.