What it is, and what it isn't
The project describes itself as an unofficial PC port of the Xbox 360 version of Sonic the Hedgehog (2006), created through static recompilation. That makes it neither an emulator nor a remake.
- Not an emulator. An emulator interprets or translates console code while you play. Static recompilation converts the code ahead of time, so the result is an ordinary native program. One catalogue entry describes this as translating the original machine code automatically and then building it as a native PC program.
- Not a remake. Unlike Sonic P-06, which recreates the 2006 adventure, Marathon Recompiled runs a converted version of the original Xbox 360 game.
- Not a PS3 port. The README says the PlayStation 3 version's files can't be used. Its formats are proprietary to that platform, so supporting them would need an entirely new recompilation. The significant PS3 differences are instead offered as options.
The toolchain is documented in the project README. XenonRecomp and XenosRecomp convert the game's PowerPC code and Xenos shaders into C++ and HLSL. The README credits the Unleashed Recompiled team with creating much of the groundwork. The recompilers were inspired by N64: Recompiled, which produced Zelda 64: Recompiled. If you've followed the recent run of native PC ports built from console binaries, this is the same lineage.
System requirements
These come from the project README.
| Component | Minimum |
|---|---|
| OS | Windows 10 version 1909, a modern Linux distro, or macOS 15.0+ |
| CPU | 64-bit x86 with AVX (Intel Sandy Bridge or AMD Bulldozer), or 64-bit ARMv8 |
| GPU | Direct3D 12.0 (Shader Model 6), Vulkan 1.2, or Metal 3 |
| Example GPUs | GeForce GT 630, Radeon HD 7750, Intel HD Graphics 510, Apple M1 |
| Memory | 8 GB |
| Storage | 6 GiB |
The README flags that the Radeon HD 7750 is the 2012 card, not the RX 7000 series.
Builds follow the platform list. The initial release includes Windows x64 and ARM64 builds, an Apple Silicon macOS build, and Linux Flatpak packages for x86-64 and ARM64. The release notes warn that outdated Intel or AMD graphics drivers may cause crashes or graphical glitches, so update them before playing. Steam Deck users should choose the x86-64 Flatpak.
You must bring your own game
The download contains no SEGA assets. You need files from your own legally acquired Xbox 360 copy, on disc or digital. The README lists DLC as optional.
Getting the files
- Dump from a real Xbox 360 using a hard drive or USB storage device. A hard drive needs the transfer cable or a compatible SATA-to-USB adapter.
- Or dump a disc on a PC using a disc drive compatible with OmniDrive.
- The README links separate dumping guides for each method.
- Another catalogue site says the title update from the same region is also needed. The README itself warns that discs and title updates from different regions fail to generate a patch.
Installer notes
- Download the release only from the project's GitHub Releases page. The README says builds will never be distributed through other sites, Discord servers or third-party update tools.
- Extract it where you want the game installed and run the executable.
- Provide your files when asked.
- Add Files accepts containers or images dumped from an Xbox 360. These are often very large files with no extension.
- Add Folder wants a directory of already-extracted raw files, such as .xex, .ar.00 and .arl. It does not scan folders for compatible content.
- Don't supply compressed archives such as .zip, .7z or .rar.
- Don't supply modified files. The installer accepts only original, unmodified ones.
If the installer says your files are invalid: check that you dumped everything correctly, that nothing is compressed, and that all the files come from the same region. If you instead get black screens or crashes after installing, the README says reinstalling won't help.
Steam Deck: the Game Mode file picker may not work until you've booted into Desktop Mode at least once. You can also do the whole install from Desktop Mode.
The bugs are the point
The project preserves the original game's bugs on purpose. The README says bugs present on the original hardware are intentionally preserved, apart from a few minor visual patches that don't affect gameplay. Bug reports for original-game issues will be rejected. Any bug that appears only in Marathon Recompiled must come with footage from original Xbox 360 hardware showing it doesn't happen there.
You can switch on optional fixes in two ways:
- Edit the configuration file.
- Open the debug settings. On the title screen, press Up, Down, Left, Right on the D-pad or arrow keys. A jingle plays and a new section appears in the Options menu.
My view is that this is the right call for a preservation-minded project. Fixing a notorious game by default changes what it is. Leaving the fixes opt-in respects both the archive and anyone who just wants to finish the game. The cost is that newcomers will hit the glitches and have to work out whether they're a port issue. The report policy is written to head that off.
Controls, saves and housekeeping
- Modern PC extras. Coverage from Sonic City lists ultrawide support, mouse camera controls, achievements and optional gameplay fixes. The README's credits mention achievement support and custom menus.
- Keyboard and mouse. The README gives a full binding table. Examples: Space for A, Escape for B, Left Shift for X and E for Y. You can edit bindings in config.toml, though the README says a controller is encouraged until action remapping arrives in a future update.
- Controller quirk. If a PlayStation pad shows up as an Xbox controller, disable third-party input layers such as DS4Windows or Steam Input.
- Save and config location on Windows.
%APPDATA%\MarathonRecomp\. Saves are in thesavefolder, and settings are inconfig.toml. - Portable mode. Create an empty
portable.txtin the install folder to keep saves and config there. You're then responsible for backing them up. - Updating. Copy the new release files over your existing install. Saves and settings survive, and you don't need to reinstall.
- Rerunning the installer. Use the
--installlaunch argument. - Linux display backend. Use
--sdl-video-driver x11or--sdl-video-driver wayland. - Frame limiters and overlays. The README warns that external frame limiters or performance overlays may degrade performance or have other negative effects.
Claims I couldn't verify
The Broken Joysticks write-up says this release doesn't support frame rates above 60 fps. It also says high-frame-rate work and a built-in mod manager are planned. I found no confirmation of either in the README or release notes I reviewed, so treat them as unverified.
The same write-up quotes other outlets saying the ports were made without AI. The README is silent on that, so it isn't a project-certified fact.
Why PC users should care
For Windows users, the practical points are these.
- A 2006 console game runs natively on Windows 10 1909 or later, on modest hardware, including ARM64 Windows.
- You supply the game data, which keeps the project clear of redistribution problems. The code is GPL-3.0, and it ships no SEGA assets.
- As with other recomp projects, you must dump your own files, which is the main hurdle for casual players.
Is the game good? That's a separate review, and the 46 Metacritic score quoted in the coverage suggests you shouldn't expect miracles. As a preservation milestone, though, a native, configurable, deliberately faithful build is a solid result.
References
- Sonic '06 Is Finally Playable on PC — 20 Years Later - Broken Joysticks Broken Joysticks · 2026-11-18T18:08:08+00:00
- Marathon Recompiled Brings Sonic the Hedgehog (2006) to PC on Its 20th Anniversary sonic-city.net
- Marathon Recompiled quiverlauncher.com