# Breath of Fire III Static Recompilation Project Brings the 1997 PlayStation RPG to PC

> A new static recompilation project translates Capcom's Breath of Fire III into a native PC executable with no interpreter in the hot path.

- Published: 2026-11-04T18:26:19Z
- Score: 8/10
- Tags: ps1, recomp, pc
- Port / platforms: PS1 -> PC (Windows) (Recompilation)
- Web page: https://emu-radar.customfw.xyz/news/breath-of-fire-3-static-recompilation-pc/
- Sources: https://github.com/thiagoreis/BreathOfFire3Recomp

A new static recompilation project by thiagoreis brings Capcom's 1997 PlayStation role-playing game *Breath of Fire III* to PC. The tool translates the original Japanese release's MIPS R3000A machine code ahead of time into C before compiling it into a native executable. This is not an emulator, meaning there is no interpreter in the hot path and the game's code runs directly on the CPU.

The project builds on [psxrecomp](https://github.com/mstan/psxrecomp) and [recomp-ui](https://github.com/mstan/recomp-ui) as submodules. It targets the Japanese release with serial SLPS-00990 and requires users to supply their own disc dump.

## Status and Features

The project is currently in pre-alpha. It is playable into the game but not through to the end. The executable boots, renders graphics, plays audio, accepts input, and handles memory-card saves.

* **Clean compilation:** Recompilation runs under strict settings across 35 shards with zero skipped functions and zero unsupported instructions.
* **Overlays compiled:** All ten RAM bands comprising 405 unique code sections and 3.6 MB are extracted from the disc and compiled in to dispatch natively. Coverage inside those bands still grows from live play, because the static walk misses entry points reached only through dynamic dispatch.
* **Savestates:** In-game slot saving works, including during combat, though savestate files can still refuse to save in overlay-heavy code.

The project extends static recompilation from Nintendo platforms to fifth-generation CD-based hardware, and its overlay-heavy code runs through the same pipeline.
