SimHub per-game setup

The four mechanisms

UDP broadcast

The game sends telemetry packets to a port on a machine. This is the only mechanism that can cross a network, which makes it the reason console support exists at all.

• You must enable it in the game. It is off by default in every title that offers it, and it is called different things — "data out", "telemetry", "UDP output".
• You must point it at an address. 127.0.0.1 if the game is on the same PC, or your PC's IP if the game is on a console.
• Only one application can receive it. This is the big one. CrewChief, Track Titan and any second dash tool will contend for the same port, and whichever starts first wins. The fix is UDP forwarding.
• The firewall matters, because this is real network traffic.

Shared memory

The game publishes telemetry into a memory-mapped region and SimHub reads it directly. Fast, reliable, low overhead — and local only, which is why every shared-memory game is marked PC-only.

Administrator rights must match. Windows will not let a normal process read an elevated one's memory. If the game or its launcher runs as administrator, SimHub must too. It fails completely silently — no error, no warning — which makes it the hardest cause on this page to guess.

Any number of applications can read the same shared memory simultaneously, so these games never have the conflict problem that UDP games do.

A plugin SimHub installs into the game

For Euro Truck Simulator 2 and American Truck Simulator, SimHub installs a telemetry DLL into the game folder. The game loads it at startup and it publishes data SimHub can read.

• x64 only. The 32-bit builds are not supported.
• Verifying game files removes it. So does a major game update sometimes. If telemetry stops after either, reinstall the plugin.
• SimHub can install it for you — you do not need to place the file by hand.

Process memory reading

Used for Elite Dangerous, which provides no telemetry API. SimHub reads the game's memory directly using a map of pointers describing where each value lives.

This breaks with every game update. Patching the game moves things in memory, so the pointer map no longer points at the right values. It stays broken until the community-maintained pointers XML is refreshed. If Elite Dangerous stopped working immediately after an update, that is the reason and waiting is the fix.

It is the most fragile of the four by a wide margin, and it exists only because the alternative is no support at all.

The per-game gotchas, in one table

The specific thing each major title needs, collected. Full pages for the most-used titles are linked below.

The Forza Windows Store problem, specifically

Worth calling out because it is poorly documented and catches a lot of people.

Games installed from the Microsoft Store run inside an AppContainer, a sandbox that by default blocks loopback network connections — that is, a Store app talking to something else on the same PC. Since SimHub receives Forza's telemetry over UDP, and both are on the same machine, that block is exactly in the way.

1. Enable telemetry output in the game's settings, pointing at 127.0.0.1.
2. Allow SimHub through Windows Defender Firewall on both Private and Public profiles.
3. If it still does not work, the AppContainer loopback exemption is the remaining cause. The Steam version of the same game does not have this problem, which is a useful diagnostic — if the Steam build works and the Store build does not, you have found it.

A checklist for any game

1. Is it enabled in SimHub? Only ticked games are watched.
2. Which mechanism does it use? The table above. This determines everything else.
3. UDP: is telemetry output enabled in the game, pointed at the right address, and is anything else holding the port?
4. Shared memory: do administrator rights match between game and SimHub?
5. Plugin games: is the plugin installed, and has a game update or file verification removed it?
6. Still nothing? Try a different game. If that works, the problem is specific to the first one.

The full diagnostic is on game not detected.

Everything in this section

• iRacing Shared memory, and the one app.ini line that has to be enabled before any external tool sees anything.
• Assetto Corsa Shared memory, mods that corrupt it, and the administrator-rights mismatch that fails silently.
• Assetto Corsa Competizione The straightforward one — nothing to enable, no mod scene, PC only.
• Assetto Corsa EVO A title still in development, and why that means checking release notes rather than trusting a page.
• Le Mans Ultimate The rFactor 2 engine underneath, the NeoRed ecosystem, and haptics tuned for long stints.
• rFactor 2 Detailed tyre and suspension telemetry — one of the best sims to build a shaker profile in.
• F1 2012–2025 UDP on PC and console, off by default in every title, and only one app gets the stream.
• Gran Turismo 7 UDP ports 33739 and 33740 from a PS4 or PS5 — and it wants the console’s IP, not the PC’s.
• Forza Horizon 5 Data out, and the Windows Store AppContainer loopback block that stops it dead.
• Forza Motorsport The same Store problem, plus the packet format setting that produces wrong values rather than none.
• Automobilista 2 UDP protocol versions, and the launch parameter overlays need.
• Project Cars 2 The same Madness engine as AMS2, on PC and console.
• BeamNG.drive OutGauge — excellent surface haptics, from a deliberately limited protocol.
• Euro Truck Simulator 2 / ATS An installed plugin, x64 only, and why verifying game files breaks it.
• EA Sports WRC Rally wants a different dashboard and a different haptics profile — here is why.
• Dirt Rally 2.0 Telemetry enabled in a file rather than a menu, and a known car-names issue.
• Elite Dangerous Pointer maps, why it breaks after every patch, and what motion-only actually means.
• Microsoft Flight Simulator Fully supported — and why a racing haptics profile produces almost nothing in it.
• Every supported game The full official list, with the footnote symbols decoded.

Common questions

Sources

• SimHub — supported games
• SimHub wiki