Evidence at a glance
Based on the linked sources. The author's reported result and independent confirmation are separate checks.
- AI involvement
- Reported models: Claude. Tools: ps3recomp, Python, Tk, CMake, Vulkan. The writeup below describes the work attributed to AI.
- Reported result
- Research. This is the directory's source-based outcome classification.
- Independent confirmation
- Not reported.
- Human work and limitations
- The project is strictly for research and does not contain game data or firmware. It relies on the user to provide a decrypted ELF from their own game disc.
Original sources
What was done
A research project attempting to statically recompile God of War: Ascension (BCUS98232) into a native Windows executable using the ps3recomp toolkit. The game currently boots, plays intro movies, and reaches the first level with limited performance.
This project is a research effort to statically recompile the PlayStation 3 title God of War: Ascension (BCUS98232) into a native Windows executable. The port utilizes the ps3recomp toolkit, which provides the PPU and SPU lifters, HLE runtime, and Vulkan/D3D12 RSX backends. The repository includes a game-specific port, analysis tools, and a Python-based launcher for managing game assets and runtime configurations. As of October 2026, the game boots, plays intro movies, and reaches the first level using the Vulkan backend at approximately 1.5 frames per second. Development is currently in an early bring-up phase. Documented work includes mapping the gameplay critical path, implementing Vulkan draw batching, and resolving various SPU-related race conditions and stack leaks. The project credits Claude Opus 5.5 as a co-author for contributions to commit history and analysis. Limitations include persistent memory corruption during long runs, texture garbage in some dumps, and the requirement for users to provide their own legally acquired game data and firmware.
Reproduce it
Dump the game disc, decrypt EBOOT.BIN to an ELF, run the ps3recomp loader/lifter, apply patches from the repository, configure via scripts/cfg.bat, build with scripts/build.bat, and execute the resulting binary.