A fix release for v0.3.1: updating an existing install works again. The launcher builds Midnight Club: Los Angeles Complete Edition (Xbox 360, USA/Europe, title 545407F8) from your own disc image; no game data is in any of the files below.
What changed
- Updating to v0.3.1 failed at step 5/6 with has been modified since the precompiled header (#23). The new SDK was unpacked with old file dates, so the build reused a leftover file from v0.3.0. The build now rebuilds it. Stuck on a failed v0.3.1 update? Just press Update and rebuild: no files to delete.
Everything else is as in v0.3.1.
Not tested
Tried on one PC (Ryzen 7 9800X3D, RTX 5080, Windows 11): a v0.3.0 install updated to this release, an install stuck on a failed v0.3.1 update, and a new install. Please tell us how it went in the issues.
Installing or updating
Already have v0.3.0 or v0.3.1? Open the launcher and press Update and rebuild when it shows An update is available.
New install: download MCLA-Setup.exe and run it. It is unsigned, so Windows SmartScreen may stop it: click More info, then Run anyway. The setup wizard then builds the game from your .iso; it needs the internet and about 10 GB of disk.
Files
Release v0.3.2, built from commit a033476d62663f2e428c6fee7bdd40aa1eed0466 by https://github.com/RenanQueiroz/mcla-recomp/actions/runs/40971360728.
| Asset | Size | SHA-256 |
|---|---|---|
MCLA-Setup.exe
| 58.6 MB | 304d499a8707f425c0f6d34450a888a29ff8decb0e5190b8f2ef99d2a9a4df60
|
MCLA-Launcher-v0.3.2-win-x64.zip
| 70.4 MB | 0c36632f55a058be88875c6da8eb48cdc6211ebba06c56c0733088ee0d422bd0
|
rexglue-sdk-f5337cdc-a0a4c7b93481-llvm-mingw-20250709.zip
| 28.1 MB | a7919acab220a2f6b787ddc9caa6ec61276412383fdf7ad4cdd325030beda0a2
|
rexglue-sdk-source-f5337cdc-a0a4c7b93481.tar.xz
| 73.3 MB | 0906ba2ac0c699bbeeafaa8a47bb2eeb9922b7b763bc51b37b71b61384269898
|
release.json
| 8.1 KB | 6103b429f22c44814dffa23247760f62ce10eeae8cbf8ffea7ce209fdf9b1133
|
NOTICES.txt
| 32.2 KB | 9413b41014ed901a4133650019fad896fc6a63d1c156bbda40e2d6e75f880f9c
|
SHA256SUMS
| the sums of the six above |
release.json is what the launcher's installer reads; NOTICES.txt has the licences and notices of everything in the assets. Every asset has a build-provenance attestation (gh attestation verify <file> -R RenanQueiroz/mcla-recomp).
- MCLA-Setup.exe: the one file a player downloads. Run it: it installs the launcher for the current user (no administrator rights asked for) in
%LOCALAPPDATA%\Programs\MCLA, makes a Start menu and a desktop shortcut and starts it; the launcher's setup wizard then builds the game from the player's own disc image. Unsigned, so Windows SmartScreen may warn (the README says how to go on). The launcher updates itself by downloading this asset (SHA-256 inrelease.json) and running it with--update. - Launcher zip: the same launcher folder as a zip, for anyone who wants it without the installer: unzip and run
MclaLauncher.exe; .NET and the Windows App SDK are inside. Unsigned. - SDK bundle: the ReXGlue SDK (f5337cdc) with the fork's 71 patches (digest
a0a4c7b93481), built with llvm-mingw 20250709, and FSR's two runtimes (FidelityFXeee08db1, built with the C runtime linked in, so no Visual C++ Redistributable is needed).scripts/make_pc.ps1 -Toolchain mingw -SdkBundle <this zip> -SdkBundleSha256 <the hash>uses it. - Source archive: the corresponding source of the bundle's GPL and LGPL parts (the SDK tree at the pinned commits with the patches applied, and the fork at this commit).
gameinrelease.jsonholds the fingerprints of the supported game (names, sizes and SHA-256 of its files: no content) for the launcher's setup wizard.- No game data is in any asset. The game is built on the player's PC, from their own disc.
When publishing: leave the Target as it is (a033476d), so that the tag is made on the commit this was built from. The tag must point at a033476d62663f2e428c6fee7bdd40aa1eed0466, which release.json names; the launcher's installer checks that.