Skip to content

Creating a Debug Report

When troubleshooting issues with DR Sim Manager, a debug report provides all the information needed to diagnose problems. The report collects system details, application settings, and recent log entries into a single file that you can share with support.


  1. Go to the Settings tab.
  2. Scroll down to the General section.
  3. Click Create Debug Report.
  4. Choose a location to save the report file (e.g., your Desktop).
  5. The report is saved as a .txt file with a timestamp in the filename (e.g., DRSM_debug_report_20260419_143022.txt).

The debug report contains the following sections:

  • Operating system version
  • Application version and license status (trial or licensed)
  • CPU model and architecture
  • Total and available system memory
  • Graphics card model(s) installed in the system
  • A complete snapshot of all application settings (from the Settings tab)
  • This includes gain values, safety thresholds, theme, shortcuts, remote control settings, and all other options
  • All configured output devices (type, connection details, axis mapping)
  • The same data visible on the Outputs tab
  • All configured simulator components (type, dimensions, travel limits)
  • The same data visible on the Sim Config tab
  • The currently active motion profile and its cue settings
  • All cue parameters (gain, smoothing, limits, etc.)
  • Complete contents of all recent log files
  • Log files are included from newest to oldest
  • Each log file is limited to approximately 50 KB to keep the report manageable
  • Older entries are truncated if a log file is very large

Log files are stored alongside the application configuration at:

%localappdata%\DRSimManager\

Log files use a date-based naming pattern: app_YYYY-MM-DD.log. A new log file is created each day. Previous days’ log files are retained for reference.

You can also access the log folder quickly by right-clicking inside DR Sim Manager and selecting Open Log.

Each log entry includes:

  • Timestamp — When the event occurred
  • Level — The severity level (DEBUG, INFO, WARNING, ERROR, CRITICAL)
  • Component — Which part of the application generated the message
  • Message — A description of the event

By default, log verbosity is set to INFO, which captures normal operations, warnings, and errors. For more detailed diagnostics:

  1. Go to Settings > General.
  2. Change Log Verbosity to DEBUG.
  3. Reproduce the issue you’re troubleshooting.
  4. Generate the debug report.

DEBUG level includes:

  • Safety filter activations with exact acceleration values
  • Telemetry data flow details
  • Configuration changes
  • Connection events for outputs and remote control
  • Detailed timing information

  1. Generate the debug report as described above.
  2. Join the DR Sim Manager Discord server.
  3. Open a support thread or post in the support channel.
  4. Attach the debug report file to your message along with a description of the issue.
  5. Include:
    • What you were doing when the issue occurred.
    • Which game and profile you were using.
    • Whether the issue is reproducible.
    • Any error messages you saw on screen.