# Spyro 1, 2 and 3 get a native PC port in progress, run from your own disc

> SpyroEngine, a work-in-progress PC port of the PlayStation Spyro trilogy, now reaches gameplay in all three games.

- Published: 2026-10-28T05:17:37Z
- Score: 9/10
- Tags: ps1, port, recomp, pc
- Port / platforms: PS1 -> PC (Windows) (Port)
- Web page: https://emu-radar.customfw.xyz/news/spyro-trilogy-native-pc-port-spyroengine/
- Sources: https://github.com/SomeoneIsWorking/psx-spyro

SpyroEngine is a work-in-progress native PC port of the original PlayStation Spyro the Dragon trilogy. It runs on your own legally obtained disc, and the repo ships no game code, assets, executables, disc images or BIOS. The project is built on psxport, a static-recompilation framework, but the README says the old generator that turned guest code into C is gone. Now the port hands the game's MIPS code from your executable to Lightrec, a runtime executor, for every instruction the native parts don't cover.

The README's status table covers all three games. Spyro 1 (`SCUS_942.28`) gets through the title and save flow, the opening cutscene and Artisans gameplay. Spyro 2 (`SCUS_944.25`) and Spyro 3 (`SCUS_944.67`) both reach gameplay from their own title screens, with Glimmer and Sunrise Spring as the levels the README names. There are caveats. On Spyro 1, the 60 fps path only changes the screen tint and letterbox, and widescreen keeps the retail culls and HUD. On Spyro 2, mobys, HUD, sky and particles have no producer yet.

The README calls the Spyro 1 boot and save-picker routes proof of wiring only. A later interactive gameplay milestone is still ahead, along with frame-time checks on each host architecture.

To try it from the repo:

1. Get a legal copy of one of the three games.
2. Install CMake and Ninja, plus the native dependencies listed in the docs. If something is missing, the build stops and prints the exact package command for you to run.
3. Check out psxport next to the project, since the launcher uses it as a live sibling checkout with Lightrec pinned by revision.
4. Run `./run.sh`. It sets up the `uv` environment, authenticates the disc, builds the product and launches it.

The build accepts GCC, Clang and AppleClang. The README I have doesn't mention a downloadable build, so expect to compile it yourself. The word "authenticated" appears in the README without a definition, so I can't say exactly what the check looks for.
