Skip to content

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? (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

TopicWhen to use
Performance & PlaybackStuttering, dropped frames, low FPS
Media & FilesMissing media, codec errors, sync issues
Network & ConnectivityUI not loading, OSC not working, NDI not found
Outputs & DisplaysBlank screens, wrong resolution, warp issues
AudioNo audio, dropout, routing problems
Crashes & RecoveryApplication 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\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 (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

Exaplay 3 User Documentation