First Run Guide

Install SimDuty correctly, enable telemetry, and validate your first operational session.

Overview

Use this guide to prepare your ATS/ETS2 environment for a reliable first run.

SimDuty runs in the background and captures telemetry directly from the game engine without manual data entry.

Platform scope: this page is the primary Windows-first flow. If you use Linux/Proton, follow the dedicated Linux Setup (Proton) guide.

Estimated time: 4 minutes Target result: SDK OK + NET OK Required: ATS/ETS2 (x64)
Required

Install plugin DLLs in the correct win_x64/plugins folder

Required

Launch sequence: SimDuty first, then ATS/ETS2, then enter cabin

Required

Validate SDK/NET status before starting real trips

Recommended

Approve plugin prompts on first game launch

Optional

Pre-check antivirus exceptions to avoid DLL false positives

Step 1: Download and extract the app

  1. Join our official Discord: discord.gg/NATM3BEzbe.
  2. Open the #downloads channel and get the latest SimDuty release package.
  3. Extract the `.zip` file to a fixed folder on your computer.
Expected state: SimDuty files are extracted to a permanent folder and can be opened without moving paths later.

Step 2: Install telemetry files

  1. Open the `dll` folder inside your extracted SimDuty files.
  2. Copy `simduty.dll` and `scs-telemetry.dll`.
  3. Paste both files into your game `plugins` folder.
  4. If the `plugins` folder does not exist, create it manually.
  5. If the game asks permission for plugins on first launch, allow it.

Path reference:

  • ATS: \American Truck Simulator\bin\win_x64\plugins
  • ETS2: \Euro Truck Simulator 2\bin\win_x64\plugins

Requirement: use 64-bit game launch options.

Windows Explorer showing DLL files inside the simulator plugins folder
Expected folder structure after copying `simduty.dll` and `scs-telemetry.dll`.
Expected state: both DLL files are visible in the correct `win_x64/plugins` folder and plugin approval is allowed on first game launch.

Step 3: Launch SimDuty and validate connectivity

  1. Open SimDuty before starting the game.
  2. Launch ATS or ETS2 in 64-bit mode.
  3. Enter the truck cabin and drive briefly to initialize telemetry data flow.
SDK and NET indicators in normal connected state
Validate this state before operation: both SDK and NET stay in OK after entering cabin and moving briefly.
SDK and NET indicators in yellow failure state
Validate failure pattern: if either indicator remains yellow, stop and re-check DLL path and launch order.
  • SDK OK: Telemetry connected.
  • SDK FAIL: Telemetry unavailable (check scs-telemetry.dll).
  • NET OK: SimDuty channel connected.
  • NET FAIL: SimDuty channel unavailable (check simduty.dll).

Signal reference:

  • SDK OK: game telemetry is available and updating.
  • SDK FAIL: check scs-telemetry.dll, plugin path, and game startup mode.
  • NET OK: SimDuty communication channel is active.
  • NET FAIL: check simduty.dll and restart sequence.

Common wrong launch order:

  • Wrong: game first -> SimDuty later -> no cabin initialization check.
  • Correct: SimDuty first -> game second (x64) -> enter cabin -> move briefly -> verify SDK/NET.
If SDK/NET remain yellow or blinking, close both applications, verify DLL placement, then relaunch in this order: SimDuty first, game second.
Expected state: after entering cabin and moving briefly, both SDK and NET remain in OK state.

Custom Jobs prerequisite (offline profile)

Before using Dispatch Offer, Dispatch Active, or SimDuty Loads, prepare an offline save profile to avoid cloud sync context conflicts.

Required guide: complete Offline Save Setup (ATS/ETS2) before running Custom Jobs in Economy.
Base Save rule: when you start Custom Jobs, choose a numeric save slot folder that contains game.sii. Follow Economy - How to choose Base Save.

Linux (Proton) path

If you are running ATS/ETS2 on Linux, use the dedicated Linux guide for Proton prefix setup, DLL overrides, and .NET runtime steps.

Use this guide: Linux Setup (Proton) (community workflow by StupidDog).

Validation checkpoint

  • Windows 10/11 x64
  • ATS/ETS2 installed
  • Game fatigue disabled
  • SimDuty opened before game launch
  • SDK and NET in OK state after entering the cabin

Quick support

Symptom: status does not change or SDK/NET lights stay yellow.

Likely cause: wrong DLL folder, antivirus block, or plugin approval missing.

  • SDK FAIL: verify scs-telemetry.dll in \bin\win_x64\plugins.
  • NET FAIL: verify simduty.dll in \bin\win_x64\plugins.
  • Close both game and SimDuty.
  • Copy both DLL files again to the target plugins folder.
  • Check whether antivirus or Windows blocked the DLL files.
  • If the app does not launch, install .NET Desktop Runtime (x64) and VC++ 2015-2022 (x64), then restart Windows.
  • If you are on Linux/Proton, follow Linux Setup (Proton) for prefix and runtime configuration.
  • If modules appear missing after first startup, confirm App Edition in Setup Guide (Lite vs Full).
  • If tabs are not visible on small layouts, confirm display mode and check the More menu.
If still failing: continue to Setup Guide for root/path validation and support bundle tools, then share diagnostics in Discord support.