Troubleshooting

Resolve common startup, plugin, and connection issues quickly.

Overview

Use this page to resolve startup, plugin, and telemetry issues in a deterministic order.

Follow these checks sequentially to avoid false fixes and to keep Home/HOS behavior predictable after recovery.

Estimated time: 5 minutes Focus: SDK/NET recovery Result: restored connection
Required

Validate DLL path and startup sequence before changing advanced settings

Required

Re-check SDK/NET state after entering cabin and moving briefly

Required

Confirm policy mode and active policy when HOS values look wrong

Recommended

Review Setup options (paths, Yard Move speed, mode toggles) for recurring issues

Optional

Generate support bundle before escalation for faster support turnaround

Top 3 checks first

  1. Confirm launch order: SimDuty first, ATS/ETS2 second.
  2. Confirm both DLL files are in the exact bin/win_x64/plugins folder of the active game.
  3. Enter cabin and move briefly so telemetry can initialize and update SDK/NET state.
Expected immediate result: both SDK and NET stabilize in OK after telemetry initialization.

Triage order

  1. Check SDK/NET indicators and confirm app/game launch order.
  2. Validate plugin DLL files and exact win_x64/plugins path.
  3. Enter cabin and move briefly to initialize full telemetry flow.
  4. If HOS/Home values still look wrong, validate policy mode and setup controls.
  5. If unresolved, gather diagnostics and escalate with reproducible evidence.

Plugin and SDK/NET recovery

  • SDK FAIL: verify scs-telemetry.dll in \bin\win_x64\plugins.
  • NET FAIL: verify simduty.dll in \bin\win_x64\plugins.
  • Confirm both DLL files are in the correct game directory.
  • Confirm the game is launched in x64 mode with matching plugin files.
  • Restart in this sequence: SimDuty first, then ATS/ETS2.
Expected state: after entering cabin and moving briefly, both SDK and NET remain in stable OK state.

No truck connection

  • Launch SimDuty before opening ATS/ETS2.
  • Enter the truck cabin to initialize telemetry reads.
  • Review permission, antivirus, and firewall restrictions.
  • If values stay stale, close both apps, verify DLLs again, then relaunch in recommended order.

Home/HOS/Setup cross-flow issues

Symptom: Home shows unexpected limits or timer behavior

  • Check: active policy mode (Auto/Manual) and current policy label in HOS.
  • Fix: adjust policy mode in Setup Guide, save changes, and restart SimDuty.

Symptom: Off Duty or Yard Move toggles behave unexpectedly

  • Check: vehicle stop state and Yard Move speed limit/auto-disable settings in Setup.
  • Fix: reduce maneuver speed, tune Yard Move settings, and re-validate controls in HOS.

Symptom: HOS Extension request is refused immediately

  • Check: requested extra time against remaining shift envelope.
  • Fix: request less time or rest first, then submit again with accurate context.

Path and reference

Primary references:

Validation checkpoint

  • SDK and NET indicators are stable in OK state during active cabin context.
  • Plugin DLL files are confirmed in correct x64 plugins directory.
  • Home and HOS values update after movement and match active policy behavior.
  • Yard Move and Off Duty controls behave as expected for stopped/moving contexts.
  • Any policy or setup change was saved and verified after restart.

Quick FAQ

  • Can I use it offline? Yes, for local operation.
  • Do I need to install .NET? No, current releases are self-contained.
  • Does it work in ETS2 and ATS? Yes, with correct plugins.

Escalation

Stop retrying and escalate when:

  • SDK/NET still fail after two full deterministic passes (order, path, cabin movement).
  • Paths are confirmed correct but status never changes across clean restarts.
  • Cross-flow values (Home/HOS) remain stale after connection appears restored.
Support package: share screenshots, plugin paths, launch order used, SDK/NET status, and generated support bundle when available.