Skip to content

Game Telemetry Not Connecting

If DR Sim Manager isn’t receiving data from your game, work through this guide step by step.


Ask yourself these questions in order:

  1. Is the correct game selected? → Check the source dropdown on the main tab
  2. Is the game actually running and in a session? → Many games only send telemetry once you’re on track / in the cockpit
  3. Is telemetry enabled in the game? → Some games require manual setup
  4. Is motion started? → You need to click Start Motion before DR Sim Manager processes incoming data
  5. Is there a firewall or permissions issue? → Windows may be blocking the connection

Make sure the game is enabled in your Source List:

  1. Go to the Settings tab.
  2. Click Edit next to Source List.
  3. Find your game and make sure it is not hidden.

If your game doesn’t appear in the source list at all, it may not be supported. Check the Sources page for the full list of supported games.

On the main tab, make sure the correct game source is selected from the dropdown. DR Sim Manager needs to know which game to listen for.

Many games require additional setup before they send telemetry data. Check the Sources page for your specific game — most have step-by-step instructions for enabling telemetry output.

Common requirements include:

  • Enabling a telemetry option in the game’s settings menu
  • Installing a plugin or mod into the game’s folder
  • Configuring an output port or IP address in the game
  • Running a setup script or copying files to specific directories

If your game requires a DR Sim Manager plugin (like DCS World, X-Plane, or rFactor 2), make sure the plugin version matches your DR Sim Manager version. After updating DR Sim Manager, you may need to reinstall the plugin:

  1. Check your game’s source page in the docs for the latest plugin installation instructions.
  2. If the source has a gear icon on its banner in DR Sim Manager, click it to open the setup instructions.
  3. Reinstall the plugin following the provided steps.
  4. Restart the game after reinstalling.

Step 4: Verify the Game Is Running and In-Session

Section titled “Step 4: Verify the Game Is Running and In-Session”

Some games only start sending telemetry once you’re in an active session:

  • Racing games: You need to be on track, not in the menu or garage.
  • Flight sims: You need to be in the cockpit with an active flight, not in the mission editor or loading screen.
  • Truck simulators: You need to be driving, not in the main menu.

If the game is running but you’re still in a menu, wait until you’re in an active gameplay session before troubleshooting further.

For games that send telemetry over UDP (network), your firewall may be blocking the connection. Most racing games (F1, Forza, Dirt Rally, WRC, etc.) and some flight sims use UDP.

  1. Open Windows SecurityFirewall & network protectionAllow an app through firewall.
  2. Click Change settings (requires admin rights).
  3. Look for DR Sim Manager in the list. If it’s there, make sure both Private and Public are checked.
  4. If it’s not listed, click Allow another app…, browse to the DR Sim Manager executable, and add it.

If you use a third-party firewall (Norton, Kaspersky, Bitdefender, etc.), you’ll need to create a rule to allow DR Sim Manager to receive UDP traffic on the port your game uses. Check your game’s source page for the specific port number.

If another application is already listening on the same UDP port that your game uses, DR Sim Manager won’t receive the data. Common conflicts include:

  • Other motion software (SimTools, FlyPT Mover, etc.) listening on the same port
  • Multiple instances of DR Sim Manager running
  • Game overlay tools or telemetry apps using the same port

Close any conflicting applications and try again.

Some games use shared memory (memory-mapped files) instead of UDP to provide telemetry. These include X-Plane, Assetto Corsa, Falcon BMS, rFactor 2, and others.

Common shared memory issues:

  • Admin vs. non-admin mismatch: If the game runs as Administrator but DR Sim Manager does not (or vice versa), shared memory access may be blocked. Try running both at the same privilege level. We recommend running neither as Administrator unless the game specifically requires it.
  • Game not writing to shared memory: Some games need a plugin installed to write shared memory data. Check the game’s source page for plugin requirements.
  • Antivirus interference: Some antivirus software may block shared memory access between applications. Add both DR Sim Manager and the game as exclusions.

Open the Source Data dock to confirm whether telemetry is being received:

  1. Go to Settings → User Interface → Show UI Docks → Source Data.
  2. The dock shows all telemetry fields and their current values.
  3. Play your game and check if the values update.

How to interpret the results:

What You See What It Means Next Step
Values are changing as you play Telemetry is working — the issue is elsewhere Check your profile, sim config, and output
All values show 0 or are static No telemetry is being received Re-check steps 1–6 above
Some values change but others are always 0 The game may not provide all telemetry fields This is normal — not all games expose all data
Values update but seem wrong (e.g., acceleration shows huge numbers) Telemetry may need game-specific configuration Check the game’s source page for setup details

  • Plugin must be installed to the correct DCS installation (Stable vs. Open Beta).
  • If you have multiple DCS installations, make sure the plugin is in the right one.
  • Port must match between DCS and DR Sim Manager. Click the gear icon on the DCS source banner to verify.
  • Requires a plugin installed in the Resources/plugins/ folder.
  • The plugin creates a shared memory mapping. If X-Plane runs as admin and DR Sim Manager doesn’t, the mapping may not be accessible.

Assetto Corsa / Assetto Corsa Competizione

Section titled “Assetto Corsa / Assetto Corsa Competizione”
  • Assetto Corsa uses shared memory — it should work without additional setup.
  • Assetto Corsa Competizione uses a different shared memory format. Make sure you select the correct game in DR Sim Manager.
  • In-game telemetry must be enabled: go to the game’s Settings → Telemetry and enable UDP output.
  • Default port is typically 20777. Make sure DR Sim Manager is configured to listen on the same port.
  • Enable “Data Out” in the game’s HUD settings.
  • Set the Data Out IP to 127.0.0.1 (localhost) and the port to match DR Sim Manager.
  • Uses shared memory. Should work automatically when iRacing is running and DR Sim Manager has the correct source selected.

Euro Truck Simulator 2 / American Truck Simulator

Section titled “Euro Truck Simulator 2 / American Truck Simulator”
  • Requires the SCS Telemetry SDK plugin to be installed in the game’s plugins folder.

If you’ve worked through all the steps above and telemetry still isn’t connecting:

  1. Check the Debug Log — Open the Debug Log dock and set Log Verbosity to DEBUG in Settings. Look for error messages related to your game source.
  2. Restart everything — Close DR Sim Manager and the game completely, then relaunch DR Sim Manager first, followed by the game.
  3. Try a different game — If possible, test with a different supported game to determine whether the issue is game-specific or a general configuration problem.
  4. Join Discord — The Departed Reality Discord community is a great place to get help from other users and the development team.