Skip to content
TheChatArchiveThe Chat Archive
DeepSeekdeepseek-v3-0324· DeepSeekHugging Face LMArena Human Preference 140K

ok so on ps1 there was games that was on 2 or more discs, how much of duplicating core…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Qwenqwen3-235b-a22b’s answer.
  1. User

    ok so on ps1 there was games that was on 2 or more discs, how much of duplicating core logic of it would eat of the disc?

  2. DeepSeek Assistant

    On the PS1, duplicating the core game logic (executable code, engine, scripts, etc.) across multiple discs would take up a very small fraction of the disc space—usually less than 1% of a disc's capacity.

    Why?

    • PS1 discs (CD-ROMs) held ~650–700 MB of data.
    • Core game logic was tiny (often 1–5 MB, rarely up to ~10 MB).
      • Example:
        • Final Fantasy VII's executable is ~2 MB.
        • Metal Gear Solid's core code is ~3 MB.
        • Resident Evil 2's engine is ~4 MB.
    • Most disc space was used for assets (FMVs, audio, textures, levels).

    How Multi-Disc Games Worked

    1. Core logic was duplicated (if needed) to ensure the game could boot and run basic functions on every disc.
    2. Unique assets (FMVs, levels, music) were split across discs to fit within the ~650 MB limit.
    3. Swapping discs only happened when loading new large assets (e.g., after an FMV or entering a new area).

    Example: Final Fantasy VII (3 Discs)

    • Core logic duplicated on all discs? Yes (~2 MB per disc).
    • Total wasted space? ~4 MB (2 extra copies) out of ~2,100 MB (3 discs).
    • Percentage wasted? ~0.2% (negligible).

    Conclusion

    • Duplicating core logic barely mattered—it was a tiny trade-off for ensuring the game worked on all discs.
    • The real reason for multi-disc games was asset storage (FMVs, audio, levels).

    Would you like a breakdown for a specific PS1 game?

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.