# Troubleshooting Overview

This section helps you diagnose and resolve the most common issues in Exaplay 3.

## Quick Diagnostic Checklist

Before diving into specific topics, run through this checklist:

* [ ] Is the engine running? (Check the system tray icon.)
* [ ] Is the web UI connected? (Green dot in header = connected.)
* [ ] Is media loading without errors? (Red badges on clips = missing files.)
* [ ] Is the DiagnosticsPanel showing acceptable FPS / CPU / RAM? (Open via header toolbar.)
* [ ] Are all output displays detected? (Config → Outputs — no "No display" warnings.)
* [ ] Is the project saved? (`Ctrl+S`)

## Troubleshooting Guides

| Topic                                                        | When to use                                    |
| ------------------------------------------------------------ | ---------------------------------------------- |
| [Performance & Playback](/v3/troubleshooting/performance.md) | Stuttering, dropped frames, low FPS            |
| [Media & Files](/v3/troubleshooting/media.md)                | Missing media, codec errors, sync issues       |
| [Network & Connectivity](/v3/troubleshooting/network.md)     | UI not loading, OSC not working, NDI not found |
| [Outputs & Displays](/v3/troubleshooting/outputs.md)         | Blank screens, wrong resolution, warp issues   |
| [Audio](/v3/troubleshooting/audio-troubleshooting.md)        | No audio, dropout, routing problems            |
| [Crashes & Recovery](/v3/troubleshooting/crashes.md)         | Application crashes, auto-heal, watchdog       |

## Getting More Information

### Engine Log

The engine writes a detailed log to:

```
Documents\Exaplay3\logs\exaplay3.log
```

Enable verbose logging with the `-log` startup flag for more detail.

### Auto-Heal State

The last known playback state is at:

```
Documents\Exaplay3\autoheal_state.json
```

### Browser Console

For web UI issues, open browser DevTools (`F12`) → Console tab to see JavaScript errors.

### Effects Server Log

The Node.js effects server writes to the console. If running from command line:

```bash
node server.js 2>&1 | tee effects-server.log
```

## Contacting Support

When reporting an issue, include:

1. Exaplay 3 version number (visible in the About page or burger menu)
2. Windows version and GPU driver version
3. A description of the steps to reproduce the issue
4. The relevant section of `exaplay3.log`
5. A screenshot of the DiagnosticsPanel if the issue is performance-related


---

# 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.exaplay.one/v3/troubleshooting/index.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.