DF Direct Q+A: Oblivion Remastered - Can Switch 2 Optimisations Fix PS5/PC/Xbox Versions?

Storyline (Oblivion Remastered)

• The subtitles don’t discuss quest progression or plot specifics for Oblivion Remastered. The focus is almost entirely on technical performance, platform optimization, and hardware/publishing strategy, not narrative.

Gameplay / Technical Highlights & Key Issues Discussed

Core performance problems (across PS5 / Xbox / Switch 2)

The panel frames the “broken” experience as four major categories:

• Unstable frame pacing at 30 FPS
• Hitching / stutter, especially in open-world traversal (less in dungeons/cities, but still present)
• Crashing
• Degrading performance over longer play

They also mention:

• A recurring major world “tanks” moment during runs (sub-120ms frame times are referenced), attributed to how the original game world/cells stream.
• Uneven frame pacing and hitching being tied to the original engine behavior underneath a Unreal Engine 5 (UE5) wrapper.

Suspected technical cause

• The panel suggests the remaster is essentially the original Oblivion engine (referred to as “Gamerio”) wrapped under UE5, and that this legacy architecture:
  • may not scale well beyond single-core / limited-thread bottlenecks
  • causes synchronization/interaction overhead between the original engine and the UE5 layer
• They emphasize segmented world/cell design as a reason hitching persists even if some areas (dungeons/cities) can be better.

Switch 2 version: what appears improved (and what didn’t)

The panel argues that Switch 2 shows visual success (noted improvements/faithful features):

• RT reflections are maintained
• Lumen GI presentation is described as impressive
• The port is called an intelligently done conversion

However, major performance issues are still reported:

• At least one severe stutter (described as ~1–2 second stutter), presented as worse than PS5 behavior
• Frame pacing at 30 FPS remains problematic
• Evidence of performance degradation is described as inconclusive due to the 30 FPS cap

Crashing details (memory leak theory vs observed behavior)

• On PS5/Xbox, the panel claims they could reproduce crashes reliably (linked to behavior resembling a memory leak, after roughly ~20 saves and reloading).
• On Switch 2, they claim:
  • the same “save-load marathon” didn’t crash during their test
  • crashes they could reproduce were more associated with relying on autosave after death, which some viewers also reported as black-screen issues after reloading.

This leads to speculation that “optimization” might be primarily bug fixes around save/autosave, not a fundamental performance overhaul.

Strategies / Key Tips

No step-by-step gameplay strategy is provided. The closest “actionable” guidance is implied testing logic:

• The panel watches for patch changes by comparing replayable performance issues and crash reproduction methods, and says they would re-check after any patch using prior archived data.

Hardware / PC Longevity Discussion (Unrelated to plot, but a major topic)

VRAM vs longevity

They discuss whether more VRAM (e.g., 24GB on 3090 vs higher-tier GPUs) is the real limiter, or whether:

• compute/RT performance will become limiting first
• texture settings may be reduced rather than total “cliffs”

General takeaway:

• 16GB should still provide a good experience for next-gen titles for a while
• but if consoles ship with very large memory capacities (30GB+), matching exact console-equivalent settings on PC may require more than 16GB over time

Business / Platform Strategy (Nintendo vs Microsoft/Sony)

Why Nintendo can move quickly (Switch 2)

They argue Nintendo can accelerate past crossgen because:

• Nintendo is the primary driver of Switch sales (they estimate ~half of revenue on Switch 1 comes from Nintendo)
• Nintendo has historically committed aggressively to new hardware each generation
• Nintendo’s exclusive-first strategy reduces the incentive to keep older systems as the main platform

Xbox “Helix” uncertainty

• The panel calls Xbox Helix strategy unclear and flip-floppy, stressing that messaging and product positioning (price, audience, exclusives) will matter heavily.
• They note constraints: Microsoft still depends on console revenue, so it likely needs an “anchor” device rather than abandoning consoles entirely.

Steam Deck Verified Criticism

• They strongly criticize Valve’s Steam Deck “Verified” system when it allows titles to be marked verified despite:
  • very poor frame rates (example complaints mention 15 FPS and bad image quality)

Key point:

• Verified criteria are described as prioritizing input/seamlessness/system/display support, while the panel thinks performance thresholds should be a major requirement.

Unreal Engine / Epic and Future Hardware

• They don’t think Epic will define a single hardware standard or release a competing “Unreal” machine.
• They suggest Epic already has influence via collaboration with platform makers, but consoles remain hardware-first while engines adapt to hardware.

Featured Gamers / Sources (Mentioned in the Subtitles)

• Tom Morgan
• Oliver McKenzie
• Todd How (referenced as “Todd How put it” regarding “bones of the original game”)
• Bethesda Game Studios (tweet referenced)
• Virtuos (mentioned as working with Bethesda on Switch 2)
• Mark Cerny (mentioned as speaking with developers/hardware architects)
• Asha Sharma
• Phil Spencer
• Sarah Bond
• Alex (referenced in context of “Alex’s test” about console-equivalent settings)
• Kepler_L2 (referenced for memory leak/claims)
• Epic / Epic Games (Unreal Engine discussion)
• Valve (Steam Deck “Verified” discussion)
• Steam Deck Verified (system/label; not a person)
• Skyrim Fest 26 FPS edition (viewer/author of a question)
• Marcus (viewer/author of a question)
• Yotssuya (viewer/author of a question)
• Lucas_ (viewer/author of a question)
• Craig.wtf (viewer/author of a question)
• what does dog need with a starship? (viewer/author of a question)
• DF DirectX Q&A / Digital Foundry (channel/source)