Troubleshooting

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? (Vio, the orb in the header, reports a lost engine; the Offline screen appears when the engine is gone.)
• [ ] Is media loading without errors? (Red badges on clips = missing files.)
• [ ] Is the Performance Diagnostics panel showing acceptable FPS / CPU / RAM? (Open via header toolbar.)
• [ ] Are all outputs detected and assigned? (STAGE tab with nothing selected — no screen in the Overview reads "No output yet".)
• [ ] Is the project saved? (Ctrl+S)

Troubleshooting Guides

Topic	When to use
Performance & Playback	Stuttering, dropped frames, low FPS
Media & Files	Missing media, codec errors, sync issues
Network & Connectivity	UI not loading, OSC not working, NDI not found
Outputs	Blank screens, wrong resolution, warp issues
Audio	No audio, dropout, routing problems
Crashes & Recovery	Application crashes, auto-heal, watchdog

Getting More Information

Engine Log

The engine writes a log for every start, named after the start time:

Documents\Exaplay3\logs\exaplay3_<date>T<time>.log

Logging is always on; no startup flag is needed.

Auto-Heal State

The last known playback state is at:

Documents\Exaplay3\logs\autoheal\autoheal_state.json

Browser Console

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

Contacting Support

When reporting an issue, include:

1. Exaplay 3 version number (☰ → About)
2. Windows version and GPU driver version
3. A description of the steps to reproduce the issue
4. The relevant section of the engine log (Documents\Exaplay3\logs\)
5. A screenshot of the Performance Diagnostics panel if the issue is performance-related