Battlefield: Bad Company Finally Has a PC Port, 18 Years After Its Console Only Launch

Battlefield fans, the time has come. The one Battlefield game that never made it to PC is finally playable on Windows, and you do not need an emulator to run it. A fan project has rebuilt the original Battlefield: Bad Company as a native PC port, complete with mouse and keyboard support, a proper launcher, and fixes for the graphics bugs that shipped on Xbox 360.
Bad Company launched in 2008 as a console exclusive, and it stayed that way for 18 years. Its sequel, Bad Company 2, came to PC in 2010 and became a classic. The original never followed. Now a static recompilation project has changed that. DSOGaming reports that the unofficial port is available to download now, and it is built the hard way: the game code is recompiled from your own Xbox 360 copy, not wrapped in an emulator.
If you have waited nearly two decades to play Preston Marlowe and the B-Company crew with a mouse in your hand, here is everything the port adds, what you need to run it, and the catches you should know about first.
What Is the Battlefield: Bad Company PC Port?
The project is called the Battlefield: Bad Company Recomp Project, and it comes from developer erutoruru on GitHub. It is a static recompilation of the Xbox 360 version of the game, built with the ReXGlue SDK. That is the same approach behind many of the best fan ports of the last few years: instead of emulating the console, the project translates the game’s original code into a native Windows program.
The result is a real PC game. It ships with its own launcher, full mouse and keyboard support, adjustable field of view, and a set of graphics fixes for problems that were baked into the Xbox 360 release. The repository went public on November 1, 2026, and the project already has two releases published.
One thing to be clear about up front: the download contains no game files and no game code. You need your own copy of the Xbox 360 version, extracted from a disc or ISO you own, and the installer generates the game code from your copy of default.xex on your own PC. That is how these recompilation projects stay on the right side of the line, and it is also why the first install takes a while.
Why Bad Company Never Came to PC
Battlefield: Bad Company was DICE’s first game on the Frostbite engine, and it was built for consoles from the ground up. The campaign follows US Army private Preston Marlowe and his squad of misfits, B-Company, as they chase a stash of mercenary gold across a fictional war in Eastern Europe. The tone was lighter than other Battlefield games, the squad banter carried the story, and the fully destructible environments were the real star. You could knock down walls, collapse buildings on enemies, and reshape the battlefield in ways no PC shooter had done before.
It reviewed well and sold well, but EA never brought it to PC. The sequel arrived on PC two years later and got all the attention, while the original stayed locked to Xbox 360 and PlayStation 3. For PC players, that meant the first chapter of the Bad Company story was simply missing. Eighteen years later, the fan port finally closes that gap.
This is part of a much bigger wave of fan ports. The same recompilation scene has already brought us native PC versions of games like the Zelda: Ocarina of Time remake and the Gran Turismo 3 enhanced port, and Bad Company is the latest console exclusive to get the treatment.
| Detail | Battlefield: Bad Company PC Port |
|---|---|
| Game | Battlefield: Bad Company (Xbox 360, 2008) |
| Project | Battlefield: Bad Company Recomp Project by erutoruru |
| Method | Static recompilation with the ReXGlue SDK (native port, not emulation) |
| Status | Available to download now (November 2026) |
| Supported version | Xbox 360 USA version only (Title ID 454107F9) |
| Requirements | Windows 10/11 64-bit, DirectX 12 capable GPU, about 20 GB free space for the build |
| Game files | Not included. You need your own Xbox 360 copy (disc or ISO) |
Mouse, Keyboard, and Launcher Features
The biggest change is also the most obvious one: proper mouse look. The port adds direct mouse look without the screen shake or jitter that controller aiming had on console, and mouse controls work with vehicle weapons too. Their movement has been smoothed out, and you can set separate mouse sensitivity for aiming, scopes, and vehicle weapons.
Controls get a full PC treatment:
- Custom key bindings, with sprint on Shift and crouch on Ctrl by default
- Weapon selection with number keys 1 to 5, including the grenade launcher and knife
- Picked up weapons, such as the RPG, are recognized and selectable
- On screen button prompts for Xbox, PlayStation, and keyboard and mouse
- Adjustable tank turret traverse speed and vehicle weapon aim speed
The launcher is where most of the settings live. It is built in Go with a WebView2 interface, and it lets you set resolution, monitor, fullscreen mode, VSync, and shadow distance before you play. Field of view can be set anywhere from 55 to 120 degrees, and you can change the size of your weapon on screen. The launcher also has a page for achievements and online services, and its interface is available in English and Turkish.
Small detail, big difference: the field of view and weapon size changes are applied to the level files themselves, and the launcher backs up the originals to an assets backup folder first. That is the kind of care you expect from a project built by people who actually play the game.
Graphics Fixes for the Xbox 360 Original
The port does not just add PC controls. It also fixes several graphics problems from the Xbox 360 version:
- Blue smoke particles are now drawn at full screen resolution instead of a reduced buffer
- White explosions get an HDR color scale fix, so their bright colors render correctly
- Black smoke and sharp terrain spikes are fixed by forcing shadows to use a single slice
- Shadow distance is capped at 200 meters, because longer distances overflow the game’s original Xbox render budgets
That last point is worth understanding. The terrain spike bug is not a flaw in the port. It is a limit of the original game’s rendering code, and the launcher deliberately refuses to offer shadow distances above 200 meters so the bug never appears. The project fixes what it can and guards against what it cannot, which is exactly the right call for a first release.
How to Install the Bad Company PC Port
Getting the port running takes a few more steps than a normal game install, because your PC has to build the game from your own copy. The launcher handles most of it, but set aside some time for the first run:
- Download the latest ZIP from the Battlefield: Bad Company Recomp Project GitHub page and extract it to a folder, for example C:\BadCompany.
- Put the files extracted from your Xbox 360 game disc or ISO into the assets folder, so that assets\default.xex and the assets\dist files exist.
- Run BadCompanyLauncher.exe.
- Press “Install game (once)”. The launcher installs the missing build tools with winget (Visual Studio Build Tools C++, LLVM, CMake, and Ninja), downloads the ReXGlue SDK, generates the game code from your default.xex, and compiles bfbc.exe. This takes 15 to 40 minutes depending on your connection and CPU, and it is only done once.
- When the build finishes, adjust your settings in the launcher and press PLAY.
One hard limit: only the USA version of the Xbox 360 game is supported. Other regional versions will not work, because the project’s code hooks match the USA default.xex exactly. If your copy is from another region, the installer will not be able to build the game.
Known Issues and Limits
This is an early release, and the project is honest about what does not work yet. Loading another save from the in game menu can occasionally crash, so restarting the game is the safer option when you want to switch saves. Shadow distances above 200 meters are not offered at all, for the terrain spike reason above.
The other limits are the ones that come with the method. You need a DirectX 12 capable GPU, Windows 10 or 11 64-bit, the Edge WebView2 runtime (already preinstalled on Windows 11), and about 20 GB of free space for the build. And again, the USA Xbox 360 version is the only supported one.
None of that should put you off. A first release of a static recompilation that already has a working launcher, full mouse support, and graphics fixes is a strong start, and the project is public and open, so fixes can land quickly.
What It Means for PC Players
Bad Company matters because it is the missing first chapter. Bad Company 2 is the one most PC players remember, but the original set up the squad, the humor, and the destructible world that made the sequel work. Playing it now, natively on PC, is the closest thing to an official port we are ever likely to get. EA has shown no interest in bringing the 2008 original to PC, and the Frostbite engine it launched on has moved through many versions since.
It also shows how far the recompilation scene has come. A few years ago, a project like this would have been a curiosity. Now it is a pattern: a small team, a public repository, a launcher that does the heavy lifting, and a console exclusive running natively on Windows within weeks of the project going public. If you play Battlefield on PC today, the Battlefield 6 secure boot fix is the guide you need for the modern game. This port is the one for the history books.
Verdict
All in all, this is the port Battlefield fans have asked for since 2008. Mouse and keyboard support done properly, a launcher with the settings PC players expect, real fixes for the Xbox 360 graphics bugs, and a build process that turns your own copy of the game into a native Windows executable. The USA only restriction and the 15 to 40 minute first build are real catches, but they are small next to finally playing the original Bad Company on PC. If you own the Xbox 360 version, this one is worth your evening.
Source: DSOGaming and the Battlefield: Bad Company Recomp Project on GitHub.









