← Back to news

DOS Game "F-15 Strike Eagle II" reversing project needs DOS test pilots

neuviemeporte.github.io|79 points|20 comments|by LowLevelMahn|Jun 20, 2026

✈️ Recruitment: DOS "F-15 Strike Eagle II" Reversing Project Needs Test Pilots

"The airforce needs YOU!"From the journals of neuviemeporte


🛠️ Project Overview

This update is part of an ongoing hobbyist endeavor to recover the original C source code for the 1989 classic, F-15 Strike Eagle II. The methodology involves the meticulous reverse engineering of the original binary files to reconstruct the high-level logic.

📈 Unexpected Acceleration

The current velocity of this project has been, frankly, staggering.

A few weeks ago, it felt as though we were facing years of grueling assembly-to-C translation before the second executable (egame) would be viable, let alone tackling the third (end). However, the situation has shifted dramatically.

Current Status Report:

ComponentStatusNotes
C Code Reconstruction✅ CompleteAll executables fully reconstructed.
Data Migration✅ CompleteAssembly data moved to C structures.
Assembly Replacements🟢 Mostly DoneFunctional C equivalents written for asm-only code.
Naming Conventions🟢 Mostly DoneRoutines and structures given meaningful identifiers.
Porting Readiness⏳ PendingPreparing to fork the repo for porting soon.

The Technical Transition

We are moving away from the "safe" phase of simply verifying that reconstructed opcodes match the original binaries. We are now entering the volatile stage of maintaining a fully functional, running game.

While our tooling ensures opcode fidelity, it cannot automatically detect logic errors—specifically those stemming from data layout discrepancies.

👨‍✈️ Call for Test Pilots

Because community support has been so vital, the project is now opening its doors to the public. We need volunteers to take to the digital skies and help us identify remaining bugs.

📦 Installation Guide

The current build is v0.9.1. It is designed to work with version 451.03 of the original game, including the Desert Storm expansion.

Deployment Steps:

  • Create a backup of your original game directory.
  • Drop the new executables into the folder, overwriting the originals.
  • Delete f15.com (this prevents the old launcher from overriding f15.exe).
  • Launch and fly!

⚠️ Known Limitations

Please be aware that the current build bypasses the setup menu. It assumes the following environment:

  • Display: MCGA/VGA
  • Audio: Sound=0\text{Sound} = 0 (None)
  • Input: Joystick=False\text{Joystick} = \text{False} (Keyboard only)

Despite this, the core loop—consisting of the mission briefing, active flight, and debriefing—should be fully operational.

🐛 Bug Reporting Protocol

We are hunting for crashes, visual artifacts, and unresponsive controls. If you encounter an issue:

  1. Document the Action: Describe exactly what you were doing before the glitch occurred.
  2. Capture Visuals: Use Ctrl+F5 in DOSBox to take a screenshot.
  3. Verify Originality: This is a bug-for-bug reconstruction.

Reconstruction Fidelity    New BugOriginal Bug\text{Reconstruction Fidelity} \implies \text{New Bug} \neq \text{Original Bug}

[!IMPORTANT] If a bug existed in the 1989 version, it must remain in the reconstruction for now.

Examples of "Accepted" Original Bugs:

  • 3D objects spontaneously vanishing.
  • The aircraft "falling" toward the sky when inverted and out of fuel.

Placeholder for F-15 Screenshot


Closing Thoughts: A massive thank you to everyone who has contributed to reaching this milestone. I am thrilled to have you all along for the ride as we push toward the next phase of the project!