Digital Foundry retest: Oblivion Remastered still has major performance issues a year later
- Digital Foundry’s new one-year retest says Bethesda’s The Elder Scrolls IV: Oblivion Remastered still has the same stutter, hitches, and frame-time problems. - The most damning detail is support cadence: PC has not received a patch since Update 1.2 in July 2025, despite lingering run-time degradation. - That matters because the remaster was meant to be the definitive version, but now looks stuck unless Bethesda or Virtuos revisits it.
Oblivion Remastered is supposed to be the easy version of this story. Take a beloved RPG, modernize it, ship the cleaner definitive edition, move on. But a year later, that still is not what happened. Digital Foundry went back to retest Bethesda and Virtuos’ remaster and came away with basically the same verdict it had near launch — the game still suffers from major performance problems, and PC support appears to have stalled after July 2025. ### What broke in the first place? The original complaint was never just “the frame rate is low.” Digital Foundry flagged hitching while moving through the open world, uneven frame-times, and performance that seemed to get worse the longer a session went on — the kind of problem players usually describe as “it starts okay, then turns into sludge.” That’s more annoying than a steady low frame rate because the game feels unstable moment to moment. ### What changed this week? The new thing is the retest itself. Digital Foundry revisited the game roughly a year after release to see whether the rough edges had been cleaned up. Turns out the answer was mostly no. Its write-up says the results “ain’t pretty,” and IGN’s summary of the retest says the same launch-era issues are still there, including the worsening performance over longer play sessions. ### Why is the patch timeline such a big deal? Because it tells you whether a messy launch is still an active repair job or just the state of the product. On PC, the last patch Digital Foundry points to is Update 1.2 from July 2025. UESP’s patch page also lists 1.2 as the July 2025 update, with performance fixes and gameplay tweaks to address core technical complaints. ### Didn’t Update 1.2 help? A bit — at least on paper. The July 2025 patch was framed around fixes for quests, gameplay, and performance, and coverage at the time treated it as a meaningful improvement. But the retest matters more than the patch notes now. If the game still shows hitches and long-session degradation a year later, then whatever 1.2 improved, it did not solve the structural problem players actually feel while playing. ### Why does “gets worse as you play” sound so ominous? Because that points to something deeper than a single bad scene or one overloaded city. It suggests a run-time issue — often the kind of thing people loosely call a memory leak, even when the exact cause has not been publicly pinned down. Think of it like a backpack that starts light and quietly fills with rocks till you see that long-session degradation behavior in 2026. ### Is this just PC drama? No — but PC is where the support gap is easiest to track. Broader coverage of the retest says the remaster still struggles across platforms, even if the exact symptoms and severity vary. The core issue is that the “definitive edition” label now clashes with the game’s reputation among tech-focused players, who still treat it as compromised. ### So what would actually fix the perception? Not another vague promise. It would take sustained patching and a visible before-and-after improvement in frame-time stability. Some coverage is already speculating that a future platform push — like the rumored Nintendo Switch 2 version — could force a broader optimization pass, but that is still just hope, not a plan. ### Bottom line A bad launch can be forgiven if the repair work keeps going. The problem here is the opposite — one year later, Oblivion Remastered still looks like a game that got one meaningful cleanup pass, then stopped. That is why Digital Foundry’s retest lands so hard. It is not exposing a fresh bug. It is showing that the old ones never really left.