RenanQueiroz/mcla-recomp v0.3.15

on GitHub

A release after v0.3.14. 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

• Setup and the launcher now ignore the git settings already on your PC (#71, #32). A leftover or broken Git for Windows install no longer stops "Getting the source".

Everything else is as in v0.3.14.

Not tested

Tried on one PC (Ryzen 7 9800X3D, RTX 5080, Windows 11): a new install, the update from v0.3.14 (the launcher too), the setup's and the launcher's git on a made-up broken git config (a system, a user and an XDG config that name a certificate file which is not there), which still reached GitHub, and a start into free roam without a crash. The broken config was made for the test; the fix was not tried on the PC of a player who had the error. A proxy or certificate file that is set only in a git config file is no longer used by the setup. Not tried here: an AMD card, Linux, the PS5 build. Please tell us how it went in the issues.

Installing or updating

Already have a v0.3 release? Open the launcher and press Update and rebuild when it shows An update is available. Updating from v0.3.13 or earlier was not tried for this release.

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.15, built from commit 4a459f62e88a8a9ca09db5683246d434211ce517 by https://github.com/RenanQueiroz/mcla-recomp/actions/runs/43698191994.

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 in release.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 75 patches (digest 7bb14d86c7e0), built with llvm-mingw 20250709, and FSR's two runtimes (FidelityFX eee08db1, 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).
• game in release.json holds 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 (4a459f62), so that the tag is made on the commit this was built from. The tag must point at 4a459f62e88a8a9ca09db5683246d434211ce517, which release.json names; the launcher's installer checks that.