mzzvxm/LARecomp

This is a targeted preservation and framerate project for one game, not a general emulator. It is worth attention if you already own Midnight Club: Los Angeles and want to run it natively on Windows with working high-frame-rate physics; it is not a way to play without the disc data.

The problem

You own an Xbox 360 racing game and want to play it on a modern PC without an emulator layer between the input and the hardware. Emulators run the PowerPC code through translation at runtime, and community framerate unlocks for this title have historically doubled simulation speed because the original code assumes a fixed 30 Hz timestep. LARecomp instead translates the default.xex PowerPC code into native C++ ahead of time, so the game compiles and runs directly on x86-64, with file I/O, GPU commands, audio and threading handled by the ReXGlue runtime. The result is a Windows build that boots to the menu, supports free roam, races and saves, and is intended to behave the same at 30, 60, 120 and 144 FPS.

What's different

The mechanism is static recompilation rather than interpretation: the game's default.xex is converted into C++ source that you compile with the ReXGlue SDK, and engine behavior is patched through [[midasm_hook]] entries in larecomp_config.toml. In practice this means the frame-rate fix is not a speed hack; the simulation is fed the real measured frame time, so physics, camera lag and suspension decay stay calibrated to the original console curve. The README also documents two engineering details that give the project its character: frame pacing improved by raising timer resolution and taking presentation off vsync, and a separate SDK vblank-loop underflow that caused framerate collapse after 7 to 30 minutes, addressed by a documented workaround until it is fixed upstream.

The trade-off is that this is a build-and-maintain project. You need the ReXGlue SDK, CMake, Clang and Ninja, plus your own extracted game data; the README explicitly rules out MSVC and warns that non-Release builds log at trace level unless REX_LOG_LEVEL is set to warn, which can cause stutter on its own. There is also one known rendering issue left: dithered alpha on shadows and foliage, whose cause is not fully pinned down.

Who should try it

A good fit is someone with a Windows x86-64 machine, a legal copy of the Complete Edition disc, and enough comfort with CMake and C++ to build from source and read the project instructions. The payoff is a native build with an in-game settings menu, save import from Xenia and RPCS3, custom MP3 radio, a mod loader and region-gated German and Italian translations.

A poor fit is someone who wants a drop-in playable download: the repository contains none of the game's disc data, so it is useless without the extracted default.xex and xarchive_*.rpf archives. Someone unwilling to keep up with the ReXGlue SDK dependency or the frame-rate workaround should also stay away, since the build is tied to SDK 0.10.0 and the vblank issue is only worked around, not eliminated.

Requirements and limitations

The setup is heavier than a typical game install: ReXGlue SDK 0.10.0, CMake 3.25+, Clang from LLVM or Visual Studio (not MSVC), Ninja, and your own extracted game data. The game-data folder must contain default.xex and the xarchive_*.rpf archives, and it is located via --game_data_root, the MCLA_GAME_DATA environment variable, or a search upward from the executable. Building is a two-command CMake preset flow, and the executable lands under out/build/win-amd64-relwithdebinfo/.

Ongoing upkeep matters here: the README ties the project to a specific SDK version, documents a workaround flag for the frame-rate collapse, and warns that trace logging must be turned down for smooth play. The dithered-alpha shadow and foliage issue is acknowledged as the only remaining rendering problem, with its cause unresolved. The project does not include the game, and no license is declared.

HotRepo's take

The project has 201 stars and was created on 2026-02-28; HotRepo's first recorded signal shows it at #3 on the C++ weekly board with +58 for the week ending 2026-10-25. With only a two-day sample and no daily-board history, persistence cannot be judged from these signals. Before investing build time, check the README's SDK version and the frame-rate workaround against your setup.