Dragon Age: Origins Is Being Recompiled Into a Native Windows Build

By Indie Kings | October 20, 2026

Updated October 20, 2026: A project called Dragon Age: Origins Recompiled is turning the Xbox 360 version of BioWare's RPG into a native x86-64 Windows program through static recompilation. Its latest build, v0.10.0-dev.3, was published on October 16, 2026, with safer saves, a smoother frame rate and a set of console-accurate kernel fixes. The repository contains no game code or data: the installer builds the game on the user's PC from their own Xbox 360 disc image.

The one-sentence version: this is not an emulator wrapper around a running Xbox 360, it is a translator that converts the console's PowerPC code into C++ once, then compiles a native Windows program that can use modern GPUs and displays.

Image credit: BioWare and Electronic Arts, via the Dragon Age: Origins Steam listing.

What static recompilation means

An emulator reads console instructions and translates them while the game runs. A static recompiler reads the game's executable ahead of time, translates the PowerPC code into C++, and then compiles that C++ into a native program. The result still needs the game's original assets, but the CPU-side code no longer runs through an emulator's instruction loop.

That difference is why the project can offer things an emulator struggles to add cleanly: a Direct3D 12 renderer, arbitrary frame rates, modern upscalers, HDR output and native input. The renderer is based on Xenia's, according to the README, but the game logic is recompiled rather than interpreted. The project calls the result a static recompilation of the Xbox 360 version into a native x86-64 Windows program.

This is the same broad approach that has appeared in other recent community projects, including native recompilations of older console games. It is not a generic emulator and it is not a source port. The original game code is translated, and the original assets are read from the user's disc image.

What the project adds

The feature list is unusually long for a project this young. It starts with rendering at up to 4K and higher, with FSR 1 or CAS scaling of the whole image. Temporal upscaling is available through AMD FSR 4 on RDNA 4 cards, FSR 3.1, Intel XeSS-SR or NVIDIA DLSS 4.5 on RTX cards, with the NVIDIA path marked experimental. The project generates motion vectors for the game's 3D scenes, which also drive optional motion blur and FSR 3.1 frame generation.

The frame rate is unlocked. The original game is locked to 30 fps; the recompilation offers 60 fps, up to 240 fps or an unlimited mode marked experimental. It also adds AMD Radeon Anti-Lag 2 on AMD GPUs and NVIDIA Reflex on NVIDIA GPUs, with Reflex marked experimental. HDR output is supported, and the High HDR quality path keeps the image in 16-bit scRGB all the way to the display.

There are quality-of-life features that have nothing to do with frame rate. Field of view can be set separately for gameplay and conversations. SDL3 input adds DualSense and other controller support. A launcher handles settings, mods and code patches, and the game's own Options menu gets a Graphics tab. Photo mode adds a free camera with a paused world, field of view, roll, aspect ratios from 32:9 to 9:16 and composition grids, saving PNGs to a folder in Pictures.

The project also exposes BioWare's own debug scripts through a cheats menu. Those scripts were left in the game and cover immortality, skill checks, gold and experience. That is a preservation feature as much as a cheat menu: it makes the shipped developer tooling reachable without a separate trainer.

Source: Dragon Age: Origins Recompiled README, fetched October 20, 2026.

The disc requirement and the legal line

The repository does not include the game. It needs an ISO image of the Xbox 360 disc for Dragon Age: Origins, title ID 454108C0. The supported release is the English, Italian and Spanish edition, media ID 186A1115, which is also disc 1 of that edition's Ultimate Edition. The French and German discs are different releases and are not supported.

The installer checks the disc before it builds anything. It extracts the image, translates the game's code to C++ on the user's computer and compiles the program. The README says the repository contains no game code or data, and the release notes repeat that the download is only the installer and tools. The game's language is chosen in the launcher, with English, Italian or Spanish available from that disc.

The DLC is handled separately. Awakening, Leliana's Song, The Darkspawn Chronicles, The Golems of Amgarrak and Witch Hunt need Title Update 6 or 7. The user has to supply the title update package and the DLC packages from a console or their own backup. The installer checks the title update against the supported media ID, extracts it and rebuilds the game's code from the updated executable. The packages themselves are left as they are.

That boundary is the important legal point. The project is not distributing Dragon Age: Origins, its DLC or a prebuilt game. It is distributing an installer and recompilation toolchain that operates on files the user already owns. Whether that is legal in a given country is a question for the user and their local law, not something the README settles.

What changed in v0.10.0-dev.3

The October 16 build is a development release on the way to v0.10.0, not a stable release. The project says users who would rather wait should stay on v0.9.0, whose launcher does not offer dev releases. For anyone already on v0.10.0-dev.1 or dev.2, the launcher offers the update itself.

The headline change is save safety. Saving over a save no longer risks the old one: the old save is set aside first, kept as a backup once the new one is written, and restored if the new save cannot be made. If there is not enough room to keep both, the game refuses to save and shows a message. The game itself shows nothing when a save fails, according to the release notes, so that message is doing real work. Closing the window while the game is writing a save now waits for the write to finish, up to 10 seconds.

The frame rate work is more technical. The release says the game's writes to memory the GPU has cached now cost about 190 access faults a second instead of about 1,500 in a test scene. With vsync on, the GPU's per-frame wait for the vertical blank no longer oversleeps by up to 2 ms. In a test scene that dipped to about 50 fps before, the build now holds 60 fps. Those are the project's own measurements, not independent benchmarks, and they describe one test scene rather than the whole game.

The release also adds a set of kernel fixes from a review of how the console behaves. Threads that end holding a lock release it to waiting threads instead of leaving them blocked. A damaged sound frame skips ahead instead of silencing that sound permanently. The sound and vblank timers run at higher priority so they stay on time under load. There are fixes to timers, waits, the on-screen keyboard's completion and the music player's queries.

Finally, the game's executable is checked against the supported disc before it is patched or read. That is a safety check for the installer, not a copy protection scheme: it prevents the tool from trying to recompile an unsupported executable and producing a broken build.

Frame rate, upscaling and HDR

The performance story has two layers. The first is the recompiled CPU code and the kernel fixes, which remove overhead that the original console game did not have to deal with on a modern PC. The second is the renderer and upscalers, which let the game run at higher resolutions and frame rates than the 2009 release allowed.

FSR 4 is limited to AMD RDNA 4 cards, which in practice means the Radeon RX 9000 series. FSR 3.1 runs more widely. XeSS-SR and DLSS 4.5 are also available, with the NVIDIA path experimental because the project has not tested it on an NVIDIA GPU. The README says Streamline only starts on an NVIDIA GPU, and the game's Graphics tab says so when DLSS is selected. If Streamline cannot start, the log explains why.

Frame generation is available through FSR 3.1, with a caveat that matters: the project says it inserts a frame between each two and only shows real frames on a display that cannot keep up. That is not the same as a free doubling of the frame rate, and it is not a reason to ignore the base frame rate.

HDR is implemented at the renderer level. On an HDR display, the 3D scenes are rendered in HDR, the game's tonemapping is redone without compressing highlights, and the image is upscaled in HDR. The High HDR quality setting keeps the signal in 16-bit scRGB to the display. That is more ambitious than a simple post-process HDR filter, and it is the kind of thing a native renderer can do that an emulator wrapper usually cannot.

Neural rendering is experimental and limited to AMD RDNA 4. It uses lmxxf's open-source port of DLSS 5's neural rendering, built into the recompilation, but the network weights are NVIDIA's and are not included. The user has to download lmxxf's package and point the launcher at it. The README measures about 7 ms of GPU time per frame for the 900-line network and 9.5 ms for the 1080-line network on an RX 9070 XT. A frame rate guard fades the network out when the GPU cannot hold the frame rate and back in when there is room.

Windows first, Linux through Wine or Proton

The recompiled program is a Windows executable. On Linux, the README says to run it with Wine or Proton. For Steam, the user adds it as a non-Steam game and forces a Proton version, because Proton includes vkd3d-proton for Direct3D 12. For Wine, the user installs vkd3d-proton into the prefix and runs the included script.

Linux support is explicitly untested. The program needs Wine's support for placeholder memory views, VirtualAlloc2 and MapViewOfFile3, plus Direct3D 12 through vkd3d-proton. FSR 4 needs AMD's Windows driver and is unlikely to work under Proton, so Linux users should choose FSR 3.1. That is a significant caveat: the project is a Windows-first release, and the Linux path is a compatibility route rather than a supported native build.

The installer itself can run from source on Linux with Python 3.10 or newer, Tkinter, git and a C++ standard library. The README gives package commands for Debian/Ubuntu, Fedora and Arch. That build path produces the same Windows executable; it does not turn the game into a Linux binary.

Mods, DLC and the debug cheats

The launcher includes a mods page with file overrides and a converter for PC mods. That is a practical decision: the Xbox 360 version has its own file layout, and existing PC mods were built for a different package. A converter lets some of that work carry over without pretending every PC mod is compatible.

DLC installation is handled by dropping the packages on the launcher or pointing it at a folder. The packages must be in the read-only LIVE or PIRS format that Xbox Live delivered. The launcher's Downloadable Content page shows which DLC and title update are installed and whether the game can use them. A title update dropped into the folder is installed too, with version 7 replacing 6.

The cheats menu is a preservation feature with sharp edges. It exposes the developers' own debug scripts, including immortality, skill checks, gold and experience. Some scripts can break quests or story fights, and the README warns about that. It is not a curated trainer; it is the game's own tooling, including the parts that can put the story into a state it was not meant to reach.

The limits worth knowing

The first limit is the disc. There is no download that includes the game, and the supported edition is specific. A different regional disc will not pass the installer's check. The second is the build time: about 25 GB of disk space, 8 GB for the game and the rest for tools and the build, with the first build taking 30 to 60 minutes depending on the CPU. A faster CPU helps, but this is not an instant install.

The third is the development status. v0.10.0-dev.3 is a dev release, and the project says it can have bugs. The stable v0.9.0 is the safer choice for anyone who does not want to test new builds. The fourth is the Linux caveat: Wine or Proton can run the Windows executable, but the project has not tested Linux support and FSR 4 is unlikely to work there.

The fifth is the nature of the project. It is a community recompilation, not an official BioWare or EA release. It is not affiliated with EA, BioWare or Microsoft. The code is MIT licensed except for Xenia's BSD-licensed components, and the downloaded dependencies keep their own licenses. The neural rendering weights are NVIDIA's and are not redistributed. Users should read the license and the installer's dependency list before running it.

Source: Dragon Age: Origins Recompiled README, fetched October 20, 2026.

Our take

The interesting part is not that Dragon Age: Origins can run at 60 fps. It is that a static recompilation can add a modern renderer, HDR, upscaling and native input without asking BioWare to touch the original code. That is a different kind of preservation from an emulator: the game's logic is translated once, and the presentation layer is rebuilt around it.

The disc requirement keeps the project on the right side of the usual preservation argument. It does not ship the game, and it does not ship a prebuilt executable that contains the game. It ships a tool that turns the user's own disc into a native program. That does not answer every legal question, but it is a coherent boundary.

The project is still early. A dev release with save-safety fixes and kernel work is not the same as a finished port, and the Linux path is untested. The feature list is impressive, but the right way to read it is as a roadmap of what the renderer can do, not a promise that every feature works in every scene. Anyone with the supported disc and a Windows PC has a genuinely interesting build to test. Anyone without it should wait for the stable release and more reports.

FAQ

What is Dragon Age: Origins Recompiled?
It is a community project that statically recompiles the Xbox 360 version of Dragon Age: Origins into a native x86-64 Windows program with a Direct3D 12 renderer. It is not an emulator and it does not include the game.

Do I need the original game?
Yes. You need an ISO image of the Xbox 360 disc, title ID 454108C0, specifically the English, Italian and Spanish edition with media ID 186A1115. The French and German discs are not supported.

Is this the same as an emulator?
No. An emulator translates console instructions while the game runs. A static recompiler translates the game's executable to C++ ahead of time and compiles it into a native program. The original assets still come from the disc.

What is new in v0.10.0-dev.3?
The October 16, 2026 dev build adds safer save handling, a frame rate improvement, kernel fixes for locks, sound and timers, and a check that the game executable matches the supported disc. It is a development release, not the stable v0.9.0.

Does it run on Linux or Steam Deck?
Only through Wine or Proton, and the project says Linux support is untested. It needs Wine's placeholder memory view support and vkd3d-proton. FSR 4 needs AMD's Windows driver and is unlikely to work under Proton, so Linux users should use FSR 3.1.

Does it include the DLC?
No. You need your own DLC packages and Title Update 6 or 7 for Awakening, Leliana's Song, The Darkspawn Chronicles, The Golems of Amgarrak and Witch Hunt. The installer extracts them from the packages you supply.

Bottom Line

Dragon Age: Origins Recompiled is a community static recompilation that turns the Xbox 360 version of the RPG into a native x86-64 Windows program with a Direct3D 12 renderer, up to 4K rendering, 60 fps and higher frame rates, FSR 4, FSR 3.1, XeSS-SR, experimental DLSS 4.5, HDR, mods and the game's own debug scripts. Its latest build, v0.10.0-dev.3, was published on October 16, 2026, with safer saves and a smoother frame rate. It requires the user's own Xbox 360 disc image, specifically the English, Italian and Spanish edition, and it does not include any game code or data. Linux is an untested Wine or Proton path, not a native build.

Sources

• Dragon Age: Origins Recompiled repository and README: 96dot/Dragon-Age-Origins-Recomp
• v0.10.0-dev.3 release notes, published October 16, 2026: v0.10.0-dev.3
• Dragon Age: Origins Ultimate Edition on Steam, for the key art and store listing: Steam listing

Related: ssrecomp: Pokémon SoulSilver in Native C++, and Claude Wrote Nearly All of It | PlatinumSharp Is Not an Emulator: Pokémon Platinum's Own Code Runs as C#