# 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.

***

## Generating a Debug Report

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`).

{% hint style="info" %}
Generate the debug report **while the issue is occurring** or immediately after. This ensures the most relevant log entries are captured.
{% endhint %}

***

## What's Included in the Report

The debug report contains the following sections:

### System Information

* Operating system version
* Application version and license status (trial or licensed)
* CPU model and architecture
* Total and available system memory

### GPU Information

* Graphics card model(s) installed in the system

### Current Settings

* 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

### Output Configuration

* All configured output devices (type, connection details, axis mapping)
* The same data visible on the Outputs tab

### Simulation Configuration

* All configured simulator components (type, dimensions, travel limits)
* The same data visible on the Sim Config tab

### Profile Configuration

* The currently active motion profile and its cue settings
* All cue parameters (gain, smoothing, limits, etc.)

### Application Logs

* 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

{% hint style="info" %}
No passwords, license keys, or personal data are included in the debug report. Passwords are stored as hashed values and appear as hash strings in the settings dump.
{% endhint %}

***

## Log Files

### Log File Location

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**.

### Log File Format

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

### Increasing Log Verbosity

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

{% hint style="warning" %}
Running at DEBUG verbosity generates significantly more log data. Set it back to **INFO** after troubleshooting to avoid unnecessary log growth.
{% endhint %}

***

## Sending the Report to Support

1. Generate the debug report as described above.
2. Join the [DR Sim Manager Discord server](https://discord.gg/skn2HzpbQy).
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.

{% hint style="info" %}
The more context you provide alongside the debug report, the faster support can diagnose the issue. Screenshots or short video clips of the problem are also helpful.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.departedreality.com/dr-sim-manager/advanced/debug-report.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.