Troubleshooting

The app will not open

• Windows SmartScreen: "Windows protected your PC". Click More info, then Run anyway. The installer is unsigned, which is what SmartScreen reacts to.
• macOS: "X-Dispatch cannot be opened" or "is damaged". Open System Settings > Privacy & Security, scroll to the bottom and click Open Anyway. Or in Terminal: xattr -rd com.apple.quarantine /Applications/X-Dispatch.app. You do this once per major version.
• Linux: nothing happens on double-click. Make the AppImage executable with chmod +x, or right-click > Properties > Allow executing. Some distributions need libfuse2 for AppImages.

X-Dispatch cannot read or write the X-Plane folder

• macOS asks for permission the first time the app reads an external drive or a protected folder. If you declined, grant it under System Settings > Privacy & Security > Files and Folders, then rescan.
• Windows: X-Plane under Program Files is protected. Run X-Dispatch as administrator (right-click > Run as administrator), or move X-Plane to a normal folder. Steam installs under Program Files (x86) have the same issue.
• X-Plane locks files while it runs. Close it before installing add-ons or saving scenery order.
• Network drives and cloud-synced folders are slow to scan and may block writes. Keep X-Plane on a local drive.

X-Plane will not launch or change flight

• X-Dispatch needs X-Plane 12.4 or newer. Older versions do not have the web API it uses. Update X-Plane first.
• "Windows blocked the launch": right-click X-Dispatch and choose Run as administrator, then try again.
• "Windows refused to start X-Plane even though X-Dispatch is already running as administrator": this is not a permissions problem. Antivirus or Controlled Folder Access is blocking X-Plane. Allow the X-Plane folder in it and try again.
• "X-Plane executable not found": the install path under Settings > X-Plane points at a folder that moved. Fix the path.
• "X-Plane did not accept the flight": X-Plane answered but refused the position or aircraft. Open Launch history in the logbook, copy the launch JSON and post it on Discord.
• If the connection drops mid-flight, X-Dispatch reconnects on its own. If it does not, restart X-Plane, then X-Dispatch.

Missing airports, old data, offline

• An airport is missing from the globe: it is not in your X-Plane install, the scenery was added while X-Dispatch was running (press Rescan files in the add-on manager), or a Layers panel filter hides it. Scenery added while the app was closed is picked up at the next startup on its own.
• Procedures or airways look wrong: check the AIRAC cycle under Settings > Nav Data. An expired cycle is flagged there. Update your Navigraph data or the X-Plane default data.
• A banner under the title bar says when you are offline. Weather, satellite clouds, VATSIM, SimBrief and updates need a connection. Airports, add-ons and planning on your own data do not.

SimBrief errors

• "SimBrief doesn't know this username or Pilot ID": check it under Settings > SimBrief and press Test.
• "No flight plan found": generate a flight on simbrief.com first, then Refresh.
• "Couldn't reach simbrief.com": you are offline, or SimBrief is down.
• Send to FMS wrote nothing, or says none of your targets match: the target folder does not exist, is not writable, or the target is for a different aircraft. Open it under Settings > SimBrief and check the folder.

Slow or heavy

• Turn off the approach light animation, ground weather and airfield lights under Settings > Graphics > Airport effects, then 3D terrain if it is still slow.
• The old tile-cache folder in the app data directory is no longer used and can be deleted to free up to 500 MB. Map tiles use the system cache now.
• X-Dispatch uses about 500 MB less memory since 2.8 because navigation data stays on disk, and less CPU while it sits behind X-Plane.
• If the app crashes twice in a row it offers to reload or quit. Report it afterwards; the crash is already in the log.

Command-line flags

A few flags for power users and scripts. They apply to that session only.

• macOS: X-Dispatch.app/Contents/MacOS/X-Dispatch --reset-cache. Windows: start /wait X-Dispatch.exe --reset-cache. Linux: ./X-Dispatch --reset-cache.
• A mistyped flag is logged with a suggestion and does not block startup.

Report an issue

WhereSettings > Support, Settings > X-Plane Logs, Discord.

1. 01

   Open Settings > Support > Report a Problem. Write what happened and, if you want an answer, your email. The report includes the app version, your operating system, the app state and your recent actions, so you do not have to collect anything.

2. 02

   For a problem with a launch, open the logbook, go to Launch history and copy the launch JSON of the one that went wrong. Paste it into the report or on Discord.

3. 03

   For something X-Plane reported, open Settings > X-Plane Logs, filter on errors, or press Open Log.txt for the raw file. Help > Open Logs Folder has X-Dispatch's own log.

4. 04

   For a quick back-and-forth, ask on Discord. Most things get answered the same day.

What makes a bug report fixable

• Crash reports are on by default and can be switched off under Settings > About > Privacy. A crash report has the stack trace and nothing about your flights.
• Anonymous usage data is off until you switch it on under Settings > Support. It never includes your IP address, file paths, companion app names, SimBrief ID or anything you type.