Live capture

EAC compatibility

Le Mans Ultimate’s anti-cheat (Easy Anti-Cheat) is sensitive to third-party processes that hook the game. The Companion does not hook, inject, or read game memory directly. It consumes the named shared-memory regions exposed by the Iron Wolf plugin — the same way the rFactor 2 community has done since 2013. On a stock LMU install, EAC has no signal that Companion is running.

That said, EAC is closed-source and rules can change. If you start getting kicked back to the launcher with the Companion open, take a screenshot of the EAC dialog and email support@lmu-portal.app. We track the false-positive log centrally and report up to Studio 397 + EAC.

Iron Wolf plugin

We do not vendor the plugin in this repo. The Companion installer ships a copy of rFactor2SharedMemoryMapPlugin64.dll from a pinned upstream commit and verifies its SHA-256 against the value baked into the installer before copying.

On Windows the install location is:

C:\Program Files (x86)\Steam\steamapps\common\Le Mans Ultimate\Bin64\Plugins\rFactor2SharedMemoryMapPlugin64.dll

The plugin is MIT-licensed (upstream source). The Companion never bundles a modified build.

Verifying the plugin SHA

If you suspect a bad copy on disk, compute the SHA-256 of the file and compare it to the value the Companion logs at startup (Settings → Live capture → Plugin SHA).

# Windows PowerShell
Get-FileHash -Algorithm SHA256 `
  "C:\Program Files (x86)\Steam\steamapps\common\Le Mans Ultimate\Bin64\Plugins\rFactor2SharedMemoryMapPlugin64.dll"

# macOS / Linux (rare — LMU is Windows-only, but devs sometimes copy the
# DLL across to inspect it)
shasum -a 256 rFactor2SharedMemoryMapPlugin64.dll

Pairing the Companion

1. Install the Companion from the link in /settings/integrations.
2. Launch it; click Pair this device.
3. The portal opens a one-time pairing page; confirm with the visible code.
4. Companion stores a refresh token in the OS keychain (Windows Credential Manager / macOS Keychain).
5. Click Install Iron Wolf plugin if prompted; restart LMU once.

Troubleshooting

Anti-virus blocks the installer

The MSI is Authenticode-signed; the macOS DMG is notarized. If your AV still flags it, capture the AV vendor + signature name and email us. Common false-positives are Windows Defender SmartScreen on the first day a new Companion version is published — click More info → Run anyway if the signer reads “Stintsmith”.

Plugin SHA mismatch

The Companion refuses to load a plugin with the wrong SHA. Delete the file at the install path above and click Reinstall plugin. If the recompute still fails, your installer is from a different release than the running Companion; update both to the latest version.

No live frames showing in the Tower

• Confirm Companion is running and shows Paired in the tray.
• Confirm the plugin file exists at the install path.
• Restart LMU after installing the plugin (the game only loads plugins at boot).
• Open the in-game console (F1) and look for “rFactor2SharedMemoryMap” — its absence means the plugin didn’t load.
• Inside Companion: Settings → Live capture → Run diagnostic prints the last shared-memory read time. If it’s >5 s old, the plugin isn’t writing — restart LMU.

Frames stop mid-session

The Companion drops frames if the WebSocket connection to the realtime service is unhealthy for >3 seconds; it reconnects with jittered exponential back-off. If the icon stays red, check that your network can reach realtime.lmu-portal.app:443. The Companion buffers up to 60 seconds of telemetry locally during re-connects and replays on resume.