DF Direct Q+A: PS5 Emulation on PC, Will Halo Move To COD Tech, Will PCs Replace Consoles?

Summary of technological concepts, features, and analysis (DF Direct Q&A)

1) PS5 emulation on PC: why it’s getting faster, and what it means long-term

• Recent success examples

  • The hosts mention Marvel’s Wolverine reaching the PS5 title screen via a PC PS5 emulator.
  • They also reference the broader idea that Dead Cells is already being run or made playable within this ecosystem.

• Core reason emulation is easier than older generations

  • PS5 emulation is framed as less like full CPU emulation (e.g., RPCS3) and more like a translation/adaptation layer.
  • Since the PS5 uses an x86 CPU, there’s less need to emulate the CPU instruction set.
  • Work focuses more on GPU/API translation and shader handling.

• Graphics pipeline approach

  • The discussion compares the emulation model to Wine/Proton:
    • Adapting Sony’s graphics API calls to a likely target such as Vulkan.
    • Recompiling shaders to run under the adapted pipeline.
  • Two strategies are discussed:
    • “True emulators”
    • Executable patching / binary translation, e.g., transforming graphics calls into Vulkan calls within the game binary

• LLMs accelerating reverse engineering

  • Oliver points to a “code-editing capability explosion” from large language models (LLMs).
  • This reduces engineering effort and helps vendor/platform-specific projects move faster and more broadly.

• Sony concerns: timeframe

  • Short-term: unlikely to be a major issue.
  • Long-term: could become larger as more high-profile PS5 titles approach “playable on PC” status.

• Why it could become a piracy problem

  • Emulators are generally described as legal because they don’t include copyrighted firmware/BIOS.
  • However, making PS5 games run may require obtaining/decrypting/discarding protections, complicating the situation and potentially tying it to piracy.

• Potential Sony responses

  • Do nothing and accept PC releases (with official PC availability potentially helping anti-piracy through better experiences).
  • Increase hardware/architectural barriers, i.e., make future systems harder to emulate.

• Customer funnel argument

  • Emulation may function as a marketing/pathway to future paying customers (e.g., early access to emulated games leading to later console purchases).

---

2) Frame generation on PS5 Pro: FSR 3.1 + PSSR 2 feasibility and constraints

• User question

  • Whether PS5 Pro could use FSR 3.1 frame generation plus PSSR 2 (upscaling), in a setup similar to Ghost of Yote (mentioned as already running around ~60fps).

• Technical feasibility

  • Oliver argues there’s no inherent reason the two techniques couldn’t be combined:
    • Console implementations of FSR 3.1 exist, allowing developers to integrate/customize.
    • FSR 3.1 (frame generation) and PSSR 2 (upscaling) are treated as separable components.

• Practical limitations / trade-offs

  • Latency penalty is emphasized.
  • Frame generation benefit depends on rendering headroom (not necessarily “double FPS”).
  • Display realities matter: many users use 60Hz TVs; frame generation is typically better with higher-refresh displays (120Hz+).

• Perceived Sony strategy

  • The team suggests Sony may prefer a Sony-branded solution or a tailored ML-based approach.
  • However, it may be lower priority today because many users won’t benefit fully without 120Hz/240Hz usage.

• Clarification: “2x frame generation” misconception

  • They correct the idea that frame generation doubles frame rate.
  • The GPU must do extra work, so the gain may be smaller (e.g., ~50–60% increase) plus added latency.

• Live example mentioned

  • The First Descendant is claimed to support PSSR and frame generation simultaneously on PlayStation, with some observed artifacts/testing described.
  • Still, the hosts doubt it’s broadly worth developers pursuing immediately.

---

3) PC vs consoles: Japan market growth and whether consoles remain relevant

• Stat mentioned

  • PC games’ market share in Japan is alleged to have doubled from 6% to 12% over four years.

• Main stance: console “dilution”

  • Consoles face dilution because PC and mobile are easier entry points:
    • Users already own devices.
    • Installs are straightforward.
  • Rising pressure around console price/access leads people to question “why not switch to PC?”

• Console survival requires differentiation

  • Nintendo is praised for delivering a distinct experience via unique hardware/form factors and exclusive libraries (with Switch 2 handheld efficiency/battery results specifically referenced).
  • Microsoft/Xbox is characterized as aiming toward homogenizing toward PC, reducing exclusive differentiation.
  • Sony is said to be trying to differentiate through exclusives, but overall PS5’s major games can largely be played on PC.

---

4) Halo after Microsoft restructuring: Unreal Engine 5 vs Infinity Ward/IW engine

• Context

  • Halo IP was said to have been handed over to Activision/IW teams.
  • This raises the question of whether Halo would use the IW engine or return to Unreal Engine 5.

• Two plausible paths

  1. Unreal Engine 5
     • If Halo’s existing Unreal-based workforces/assets can carry over.
     • If speed matters.
  2. Infinity Ward’s engine
     • If the team wants the strengths of a proven FPS engine.
     • If they can leverage CoD-staff expertise.

• Why Unreal seems likely (Oliver)

  • Halo Studios previously built a technical foundation to run parts of the Halo Reach engine within Unreal (described as the basis for Halo: Campaign Evolved).
  • There’s an emphasis on investment in assets suited for Unreal.
  • Halo Campaign Evolved is described as technically solid and visually impressive, using modern UE systems: Lumen and Nanite.

• Expectation

  • The biggest priority is likely to ship a Halo release soon.
  • Engine choice then depends on which team/resources can ramp fastest.

---

5) Project Helix (next-gen Xbox concept): could it replace both PC and Series S?

• Question posed

  • Could Project Helix replace an RTX 3060 PC and Xbox Series S?

• Main dependency: software “openness”

  • Whether it supports a Windows desktop.
  • Whether it allows access to PC storefronts like Steam or the Epic Games Store.

• Hardware/software caveats

  • Even if it’s “a PC box,” Microsoft could restrict desktop access, keeping it console-like.
  • HDMI/ports and vendor-specific tech could limit compatibility.
  • They mention potential issues like DLSS not being supported, implying reliance on AMD alternatives.

• What “unlocking” might look like

  • From an Xbox app launcher with links
  • To a full experience with Windows desktop
  • If open enough, it could replace both devices for most users; otherwise, users who want Linux or deeper modifications may still need a traditional PC.

---

6) If Xbox succeeded (Series S/X win), how would Helix differ?

• What-if premise

  • If the Series S/X had been a resounding success, what would Project Helix look like?

• Team reasoning

  • They link speculation to earlier planning leaks (May 2022 plans and later leaked details).
  • Helix differentiation might shift more on software offerings than on core hardware.

• But strategy might not map cleanly

  • Microsoft leadership messaging could shift between a high-end PC vision and a more console-organized mass-market direction.

• What Xbox would have needed to “win”

  • Oliver’s view: a stronger launch slate and major games closer to promises:
    • Halo Infinite matching early trailer expectations
    • Later follow-ups like Forza Horizon 5 landing as strong additions

• Long-term Helix implication

  • If Xbox had won, the rationale for consoles and tiers might remain more stable.
  • The discussion ends emphasizing that Microsoft still needs a consistent vision for Helix to make sense.

---

Main speakers / sources

• Will Judd
• Oliver Mackenzie
• Amber (viewer question)
• Anxious Figure (viewer question)
• Mikey Love (viewer question)
• Baron O’Beef (viewer question)
• John Steeboss (viewer question)
• Sarah Bond (referenced regarding statements about the next Xbox/Helix direction)
• Mark Cerny (referenced via a past comment about frame generation investigation)
• Rich (referenced regarding Xenia PS4 as a counterexample)