<div align="center">

Drakengard 1 · Europe

Static recompilation research for PlayStation 2

A source-only project working toward a native PC port of Drakengard.

Project site · Telegram channel

Progress · Getting started

</div>

Research in progress. No playable build is available. The native diagnostic runner progresses beyond the Chapter I mission briefing and renders Caim with his weapon, terrain, objects, radar and HUD. Analog character movement and a rendered melee attack animation are verified in bounded diagnostic runs. Hits, combat, audio, saves and recovery are not yet verified.

The project

The goal is to bring Drakengard (PS2, Europe) to PC through static recompilation, with explicit runtime support for the hardware and services its original code uses. Windows x64 is the initial host target. Linux portability is a later goal.

The observed input is SLES-52322 · version 1.00 · PAL. Exact ISO and ELF fingerprints are recorded in local intake output; the serial alone does not establish revision or dump authenticity. Game-specific bindings require the verified ELF hash.

Progress

Area	Verified milestone	Remaining work
Input & toolchain	Read-only intake, pinned tools and local European ELF lift	Broader translation and runtime coverage
EE ↔ IOP	Guest-owned reboot, two actual BOOTEND stores and SIF transfers	Broader device and service coverage
Guest modules & input	Original IOP modules execute; SIO2 accepts ordinary button presses/releases and menu selections	Broader controller coverage and in-game validation
Disc services	226 CDVD transfers and 5,997,856 bytes read from the verified ISO	Validate later disc operations
Graphics & gameplay	Main menu, prologue, Chapter I briefing, visible Caim/terrain/objects, actual analog movement and a Square-triggered melee attack animation after the opening script releases control	Verify hits, combat and sustained gameplay
Audio, saves & recovery	Not yet verified	Verify these in actual gameplay

Passing CI validates preparation tools and synthetic service contracts. It does not establish a working port.

Earlier GS output from the native runner: radar and message were visible, but character/environment rendering was not yet established in this captured checkpoint. The image is not evidence of playable gameplay or an independent host-window check.

Getting started

The public checks need no game or BIOS. Install Python 3.10+ and Git:

python scripts/doctor.py
python -m unittest discover -s tests -v
python scripts/check_public_tree.py

Standalone C++ service checks additionally require CMake 3.21+ and a C++20 compiler. CI runs synthetic checks on Windows and Linux. This does not build or validate the private native game runner on Ubuntu.

To work with your own completed local input, follow the local runner instructions and keep the original image outside the repository. The fingerprint tool inspects inputs; it does not extract an ISO or establish authenticity. The native runner is a diagnostic experiment and requires additional local preparation.

Contributing

Focused work on device contracts, CPU behavior and synthetic tests is welcome. For runtime reports, include the tool revision, input fingerprint, first blocker and a reproducible procedure. Keep game data, BIOS, generated guest code, saves and raw traces out of issues and patches.

Unsupported behavior stops explicitly. Changes should demonstrate the real operation and its failure cases before extending coverage.

Source-only & licensing

This repository distributes original project source, synthetic tests, configuration templates and the project README, plus the reviewed progress image shown above. It includes no game inputs, BIOS, original executables or generated game code. Supply your own local inputs; keep them in ignored directories.

Original project code and documentation are licensed under MIT. No upstream runtime or generated game code is vendored. Any future third-party integration needs its own license review.

Independent, unofficial research project. Not affiliated with the game's rights holders.