About
Battle: Los Angeles is a 2011 first-person shooter developed by Saber Interactive (via its Live Action Studios division) and published by Konami as a downloadable tie-in to the 2011 alien-invasion film of the same name. Released on the same day as the movie for Windows, Xbox 360, and PlayStation 3, it casts the player as a Marine fighting extraterrestrial forces across a short, linear campaign. It was a low-budget, console-focused release that received unfavorable reviews from critics, who criticized its brevity and generic shooting. It is notable today mainly as a delisted licensed movie tie-in that is no longer sold.
Identity
Launch
- Binary
- BattleLA.exe
- Needs files
- none beyond the binary
Proton
- Version
- GE-Proton
- Winetricks
- —
- ProtonDB
- ProtonDB Pending not enough reports yet
⚙ Setup notes
Game: 2011 Saber Interactive / Konami movie tie-in FPS (short, budget console port; appid 61220). Main binary is BattleLA.exe (in the game's bin folder).
Proton: Force-install a recent Proton via the game's Compatibility tab; GE-Proton is the safest starting point. There is no Games for Windows Live on this title, so no login/DRM wrapper to fight — the binary boots toward the menu directly.
DRM (StarForce): Per PCGamingWiki the PC release ships StarForce disc-style copy protection, which installs a kernel-mode driver and is the real compatibility risk here. StarForce's own SFUPDATE driver utility is the documented Windows-side fix on the native machine; under Proton the driver is the usual culprit if the game refuses to start, so this is the first thing to suspect rather than any GFWL fix. Treat as needs-test — confirm it actually launches under Proton before trusting it.
Display: If you hit a D3D11 black screen on first launch, try the launch option PROTON_NO_D3D11=1 %command%.
Controller: Being a 360-era port it has native XInput gamepad support, so the Deck controller should be recognized once the game is running; otherwise apply a Steam Input gamepad layout.
The one thing to know
Supply your own copy: Delisted from Steam since Dec 2016 (film license expired) — owned-library only, not for sale.
DRM (StarForce): The real Deck hurdle is StarForce copy protection (per PCGamingWiki), a kernel-mode disc-protection driver — not Games for Windows Live, which this title does not use. StarForce v5 needs a manual driver update via StarForce's SFUPDATE utility even on plain Windows 10/11, so under Proton it is the most likely reason the game would fail to start. No verified Proton workaround on record — this is the main reason to treat as needs-test.
Display: If you get a black screen at launch, try PROTON_NO_D3D11=1 %command%.
Status: ProtonDB has effectively no reports for appid 61220 (tier pending). Bootability under Proton is unconfirmed pending the StarForce question — needs-test. Short, budget title.
Controller: Native XInput controller support, so the Deck pad should work once the game runs; if not, apply a Steam Input gamepad layout.
Community guides
Write-ups and threads from people who got this (or a similar) game running. deckport links to them — it doesn't reproduce them.
Get the artwork
deckport never hosts game images. Open this game on SteamGridDB, pick
the cover / hero / logo / icon you like, and drop them into the
game folder under .deckport-art/ before you push it to the
Deck. The importer files them under the right names automatically.
Run it on your Deck
Two files: the one-time importer (deckport.py) in your
Deck's home folder, and this game's install helper. Copy the game
into ~/Games and run the helper with Steam closed — it
writes the recipe (binary, launch options, Proton version)
and registers the shortcut with artwork.