ok so on ps1 there was games that was on 2 or more discs, how much of duplicating core…
- 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?
Assistant
Ah, got it! Let’s dig deeper with specific examples and technical context to clarify how much space duplicating core logic would take on a PS1 multi-disc game.
Key Points Recap
-
Core Game Logic Size:
- The executable code (core logic) on a PS1 game was typically 1–10 MB.
- Even complex games like Final Fantasy VII (3 discs) or Metal Gear Solid (2 discs) had tiny codebases compared to modern standards.
- For example, Metal Gear Solid’s code was ~3–5 MB, while its discs held ~600 MB each (mostly FMVs, voice clips, and textures).
-
Disc Capacity:
- A standard PS1 disc held ~650–700 MB of data.
- Even duplicating the core logic (e.g., 10 MB) across 2 discs would use <2% of total space (10 MB × 2 = 20 MB total).
Why Core Logic Wasn’t Duplicated
-
PS1 Architecture:
The PS1 loaded game code into RAM (2 MB total system RAM, with 1 MB for the CPU). Once the game started, the disc was only accessed for streaming assets (like FMVs, audio, or level geometry). The core logic wasn’t reloaded from the disc unless the game specifically required it (which was rare). -
Multi-Disc Design:
- Disc 1 usually contained:
- Core game engine (code, scripts, base assets).
- Critical assets (e.g., UI, save/load systems).
- Disc 2/3+ contained:
- Additional levels, FMVs, audio tracks, or textures.
- No duplicate code was needed because the game kept the core logic in RAM.
Example: Final Fantasy VII (3 discs):
- Disc 1: Core engine + Midgar.
- Disc 2: Core engine (not duplicated) + Gold Saucer.
- Disc 3: Core engine (not duplicated) + Northern Cave.
- Disc 1 usually contained:
Edge Cases Where Code Might Be Duplicated
- Bugs or Poor Optimization:
Some games might have duplicated small chunks of code (e.g., shared libraries) across discs, but this was rare. Most developers avoided it to save space. - Language-Specific Assets:
If a game had region-specific text/audio (e.g., Japanese vs. English), the code might differ slightly, but this wasn’t true duplication—it was separate builds.
Practical Example: How Much Space Would Duplication Take?
Let’s assume a hypothetical PS1 game with:
- Core logic: 8 MB.
- Disc 1: 8 MB code + 600 MB assets.
- Disc 2: 8 MB code (duplicated) + 600 MB assets.
Total space used by code: 16 MB (2.4% of total 1.3 GB across both discs).
Total space saved by not duplicating: 8 MB (negligible for PS1 discs but valuable for assets like FMVs).
Conclusion
- Duplicating core logic on multiple PS1 discs would consume <1–2% of a disc’s total capacity.
- Developers avoided duplication because:
- RAM could hold the core logic.
- Asset size (FMVs, audio) was the real space hog.
- PS1’s CD-ROM drive was slow, so minimizing disc access was critical.
Multi-disc games were about asset management, not code. Even if code was duplicated (which was rare), it wouldn’t have impacted disc space meaningfully.
Let me know if you want to explore a specific game’s disc structure! 🎮
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.