● Covered by 1 source · 1 reportMedium impact1 neutral
Resident Evil 4 GameCube Debug Build Decompiled to Byte-Identical C/C++
Key points
- Byte-identical decompilation of Resident Evil 4 GameCube debug build.
- Reproduces main.dol and 114 REL overlays.
- Requires original disc images; no game assets included.
- Provides tools for build verification and function comparison.
Project Overview
A complete, byte-identical decompilation of the Resident Evil 4 (GameCube) G4BE08 debug build has been achieved. This project specifically targets the "Nov 25 2004" prototype, which includes two discs and Bio4.sym files that name every function. The repository allows for the reproduction of the main.dol and all 114 REL overlays, verified through SHA1 checksums on every build.
Technical Requirements and Setup
The repository does not contain game assets or code copied from the discs. Users must provide their own images of the debug discs (disc 1 for main.dol and most RELs, disc 2 for the four island-stage RELs). The original files are read during the configuration process. The build environment requires Linux, Python 3, and ninja. Compilers and tools like decomp-toolkit, objdiff, and wibo are downloaded automatically, with the exception of the native SN GCC, which needs to be built from its GPL source drop.
Verification and Development Tools
After building, the project provides verification tools. Running `ninja` concludes with a progress report confirming 100% matching and linking for the DOL and REL modules. A `shasum` check confirms 115 OK lines. For unit-specific work, `bytecmp.py` compares objects word by word, and `fdiff.py` displays individual functions, aiding in detailed analysis and development.
Repository Structure
The repository is organized into several key directories. `src/game/` contains the game's C++ and newlib C units, with subdirectories for enemies, weapons, player characters, and rooms. `include/` holds headers and reconstructed struct layouts. Configuration files, unit lists, symbols, and linker scripts are found in `config/G4BE08/`. The `tools/` directory includes the build generator, ProDG driver, REL rebuild scripts, comparison tools, and the SN GCC build. `research/` contains a compiler-analysis kit, and `motion_export.py` with `motion/` handles animation export. Documentation in `docs/` provides an overview of the engine and details on the matching process.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
The daily brief
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Today's brief
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's brief
New every morning, and the back catalogue is archived by date.
Primary sources
GitHub cmc_internal/api GitHub github/collect GitHub adonis-singh/re4 GitHub _private/browser GitHub get-started/accessibility GitHub open-source/sponsorsReporting from
A complete, byte-identical decompilation of the Resident Evil 4 GameCube debug build (G4BE08) to C/C++ has been released. This project allows developers to reproduce the original main.dol and all 114 REL overlays, offering insight into the game's engine and development process.