Call of Duty 2: Big Red One

Call of Duty 2: Big Red One

SmokeDoggy044/CoD2-BRO-Native-Loader

A native loader for Linux and Windows: since the Xbox has an x86 CPU, the game’s original executable is loaded into memory and runs directly on the PC’s CPU, with nothing recompiled. Everything around it is replaced: the Xbox kernel and the libraries the game uses (Direct3D 8 on Direct3D 9 through DXVK, DirectSound on OpenAL Soft, and controllers, keyboard, and mouse through SDL3), plus a few patches. In 0.1.4, still a prototype, the campaign plays from the menus: missions 1 to 5 are tested through and mission 6 started. It runs at 60 fps, with widescreen, higher resolutions, and System Link multiplayer over LAN; Xbox Live isn’t available. It’s the proof of concept for a full native port, which is progressing in the same author’s decompilation. It states that most of the code and the reverse engineering were written by Claude, directed and playtested by the author.

You needThe files from your own copy of Call of Duty 2: Big Red One for Xbox. Plus 32- or 64-bit x86 Linux (glibc 2.30 or later) with Vulkan 1.3 and the 32-bit libraries, or 64-bit Windows 10 or 11.

Call of Duty 2: Big Red One

SmokeDoggy044/CoD2-BRO-Decomp

Work-in-progress decompilation of the Xbox version, by the same author as the native loader, also in this catalog. Each function is rewritten in C++ and compared byte for byte with the original inside the running game before it replaces it; the goal is a native Linux and Windows port that only needs the game’s files. As of October 19, 288 of 14,540 functions had been rewritten, starting with the renderer, and 1,633 named, many matched to the code of Quake III Arena, which the engine descends from. The nearly 5,000 functions of the mission scripts will be converted by an automatic translator. There’s nothing to play yet. It states that the names, the decompiled code, and the tools were produced by Claude, reviewed and tested by its author.