MSFS Blind Assist

Troubleshooting and FAQ

This is the guide for the preview build 10.0.1-pre.97, which has features the released version does not have yet. Read the guide for the released version.

Chapter 3 of 4 in Appendices of the MSFS Blind Assist user guide.

Most problems have a simple cause. Work through the matching section below. If nothing helps, collect your logs (see the last section) and ask on the MSFS Blind Assist Discord server.

BA Is Silent, or Speech Sounds Wrong

Hotkeys Do Nothing

BA Will Not Connect, or Uses the Wrong Aircraft

Cockpit Controls Do Not Respond (MobiFlight)

On several aircraft, including the FlyByWire A320neo and A380X, the Fenix A320, the Headwind A330, the TFDi MD-11 and the BlueBird 757-200 (and for a handful of switches on the HorizonSim 787-9), BA needs the free MobiFlight WASM module to operate switches and knobs. Without it, reading and announcements still work, but many controls do nothing.

If you hear “MobiFlight calculator path unavailable. Some cockpit controls may not respond.”, install or reinstall the module in your Community folder and restart the simulator (see What You Need). Only the FlyByWire A320neo and A380X, the Headwind A330, the TFDi MD-11 and the BlueBird 757-200 give that warning. The Fenix A320 and the HorizonSim 787-9 do not warn you, so if one of their switches never moves, check MobiFlight first.

PMDG: CDU Window or Readouts Are Empty

The PMDG 737 and 777 only share their data with other programs if their SDK broadcast is switched on in the aircraft’s options file. BA checks this when you pick the aircraft and, if the lines are missing, opens a window titled with the aircraft’s name and SDK setup.

Follow the window’s instructions with the simulator closed: PMDG rewrites the file when the simulator exits and can drop lines you added while it was running. The window and every step are described in The PMDG SDK Setup Check.

If BA says it could not find the options file at all, that is normal before you have loaded that PMDG aircraft once; PMDG creates the file the first time. Load the aircraft, then follow the steps.

Airport or Runway Not Found: the Navigation Database

BA’s airport, runway, taxiway and procedure features all read a navigation database built from your simulator’s own scenery. If it is missing or built for the wrong simulator, they fail.

See The Navigation Database for more.

A Taxi Route Will Not Calculate

Tones Play on the Wrong Device, or Not at All

  1. Open Settings and go to the Audio tab.
  2. In Guidance tone output device, choose where you want BA’s guidance tones (taxi, takeoff, hand fly, landing guidance and docking). This does not change where your screen reader speaks.
  3. Press Test Tone to hear a tone on the chosen device, and Stop Test to end it. The Status line shows which device is really in use.

If your chosen device is unplugged, the tones move to the Windows default device and come back when you plug it in; see Choosing where the tones play. “No audio device available for guidance tones.” means Windows has no working output at all, so every guidance tone is silent.

If a tone is on the right device but too quiet or too loud, each tone has its own volume setting; see the Tone Cheat Sheet.

Updates

Sim Performance

What it is

The Sim Performance window shows the same kind of figures a sighted pilot reads from the simulator’s own developer frame-rate display: how smoothly the simulator is running, and how hard it is working your computer. It is useful when you are tuning graphics settings or wondering whether the simulator is struggling.

How to use it

Open it from the File menu, Sim Performance. It opens whether or not the simulator is connected. It is a list with one value per row:

The list updates itself every second, so there is no refresh button. Arrow to the row you care about and stay there: that row is re-read whenever its value changes, while the others stay quiet. Press Escape or the Close button to close it.

The simulator’s internal per-thread timings, and its verdict about what is limiting performance, cannot be read from outside the simulator, so they are not shown.

Logs: What to Send When You Ask for Help

Press Windows+R, type %APPDATA%\MSFSBlindAssist\logs and press Enter. Zip that folder and send it with a short description: what you did, what you expected, what happened, and roughly what time. Logs and Getting Help has the full steps.

Tip: Send logs soon after the problem. Logs are rotated as they grow, so an old problem may have been written over.

Frequently Asked Questions

Do I need to see the screen at all? No. Everything BA does is designed for a screen reader and the keyboard. Some aircraft displays can only be read through BA’s optional AI display reading, which needs your own API key; see AI Display Reading and Scene Description.

Does BA fly the aircraft for me? No. BA gives you access to the aircraft’s own controls and tells you what is happening. The aircraft’s autopilot flies when you engage it; BA’s tones help you fly by hand when you choose to.

Does BA tell me when a runway is clear? Never. Its runway watch tells you what traffic it can see, as “no traffic seen”, because it cannot see everything ATC can. Only a clearance tells you a runway is yours.

Why does BA not announce my button presses? Your screen reader already does. If BA spoke too, you would hear everything twice. BA speaks when you type a value, when something goes wrong, and when something changes on its own.

Can I use BA with MSFS 2020 and MSFS 2024? Yes. Build the navigation database for each simulator you use.

My aircraft is not listed. Can I still use BA? Yes, for the general features: taxi guidance, ground traffic, weather, location, planning, teleport and many readouts. The panels and aircraft-specific windows are only available for the aircraft in the Aircraft menu.

Where do I get help? The MSFS Blind Assist Discord server, linked from the project’s home page, is where users and developers talk. Bring your logs.