(Port Idea) Star Wars Episode I: The Phantom Menace (1999) – Playing to Saturn's strengths?

Hey guys,
I’ve been thinking about late PS1/PC games from 1998–1999 that could actually shine on the Saturn, and Star Wars Episode I: The Phantom Menace came to mind—not just as a straight port, but actually improving on the PS1 version by playing to the Saturn's strengths.
Why it fits the Saturn (and where it could beat the PS1 version):
  • Faster Loading Times: The PS1 version was notorious for long, frequent load screens. With smart data streaming and taking advantage of Saturn's extra RAM/cache, load times could be way smoother.
  • Superior Audio (Ponesound + ADX): Using Ponesound with ADX streaming for John Williams' score and all the spoken dialogue would sound cleaner and punchier than the heavily compressed PS1 audio, without eating up sound RAM.
  • Cleaner FMVs (PC-sourced Cinepak): Encoding the cutscenes into Cinepak directly from the higher-resolution PC video files (instead of the heavily compressed PS1 STR videos) would make the movie clips look way sharper.
  • Visual Upgrades (No PS1 Wobble + VDP2): Running on VDP1 eliminates the classic PS1 polygon wobble and texture warping, while the VDP2 can handle crisp high-res UI/dialogue menus, parallax backgrounds, and cleaner lighting/transparency effects for lightsaber blades and Droideka shields.
  • Tight Overhead Levels & Existing Decomp: Most stages are enclosed corridors (Trade Federation ship) or narrow streets (Mos Espa, Theed) with a fixed top-down camera, avoiding massive draw distances. Plus, the PS1 version already fits in 2 MB of RAM and has an active decomp (tpm-decomp), alongside OpenPhantom for PC, so the assets and formats are already documented.
Phased approach (if anyone ever experiments with it):
Using SRL or Jo Engine with the original assets in small steps:
  • Phase 1: Load a single small level and walk around with a free camera.
  • Phase 2: Add Qui-Gon's model, fixed overhead camera, and basic floor/wall collisions.
  • Phase 3: Lightsaber combat, blaster deflection, and basic droid AI.
  • Phase 4: Sound effects, voice streaming, and music via Ponesound + ADX, plus PC-sourced Cinepakcutscenes.

I'm not a programmer myself, just wanted to share the idea and see what you guys think. If a dev ever decides to mess around with a Phase 1 tech demo, I’d gladly help out with real hardware testing, cover/manual artwork, and physical collector cases.
Do you think the VDP1 could handle the angled floor textures cleanly, or would that be the main bottleneck?
 

Attachments

  • IMG_2023.jpeg
    IMG_2023.jpeg
    894.4 KB · Views: 0
  • IMG_2022.jpeg
    IMG_2022.jpeg
    247.5 KB · Views: 0
  • IMG_2021.jpeg
    IMG_2021.jpeg
    225 KB · Views: 0
  • IMG_2025.jpeg
    IMG_2025.jpeg
    179 KB · Views: 0
  • IMG_2024.jpeg
    IMG_2024.jpeg
    241.3 KB · Views: 0
  • IMG_2020.jpeg
    IMG_2020.jpeg
    231.1 KB · Views: 0
Please stop spamming the Saturn-Dev section with AI Generated what if posts. Most of the "improvements" you've posted don't really make any sense.
  • Cinepak at best is going to match PS1 quality, not really exceed it. Both are lossy formats that will have their own kinds of artifacts.
  • The PS1 games use the PS1's native ADPCM compression support and are most likely 37.8KHz. Ponesound does not support that with ADX, you'd need a different approach to get that quality or better.
  • Both systems have a 2x CD ROM drive, so load times won't really be that much better or worse. If anything they might get worse due to needing more textures due to the lack of UV Texture coordinates.
Using AI isn't a problem, but if you don't know what you're talking about you're just going to get nonsense back. Which is exactly what keeps happening with every post you make. Either take the time to learn the hardware and how it actually works so you can prompt the AI intelligently, or stop wasting our time.
 
Back
Top