MSFS Blind Assist

Getting Started

Chapter 2 of 2 in Part 1: Getting Started of the MSFS Blind Assist user guide.

What You Need

Note: On the FlyByWire A320neo, the FlyByWire A380X, the Headwind A330-900neo, the TFDi MD-11 and the BlueBird 757-200, if the module is missing, BA tells you a short while after connecting: “MobiFlight calculator path unavailable. Some cockpit controls may not respond.” If you hear that, install or reinstall the module and restart the simulator. The Fenix A320 and the HorizonSim 787-9 do not give this warning, so on those check the module yourself if a control never responds.

Some features also need their own free accounts or keys, such as SimBrief for flight plans or an AI provider key for reading cockpit displays aloud. You do not need any of these to start; each is explained in its own chapter.

Installing

BA has no installer. It comes as a zip file that you extract to a folder of your choice.

  1. Download BA from the project’s GitHub page. There are two builds:
    • The stable release, named MSFSBA.zip. This is the one most pilots should use.
    • The preview build, named MSFSBA-preview.zip. It is rebuilt every time a change is finished, so it has the newest work. Every change is reviewed and tested before it gets there, but it has had far less flying time than a release, so bugs are more likely.
  2. Extract the zip to a folder you will remember, for example a folder called MSFS Blind Assist in your Documents. Avoid extracting it inside the simulator’s own folders.
  3. Open the folder and run MSFSBlindAssist.exe.

To update by hand later, close BA and extract the new zip over the same folder. Most of the time you will not need to: BA can update itself (see Updates).

Inside the folder you will also find a folder called HotkeyGuides, holding the hotkey list for every aircraft as plain text files, and a Guides folder holding a separate manual for the FlyByWire A380X.

Only one copy of BA can run at a time. If you start it twice, you hear a message box saying “MSFS Blind Assist is already running. Only one instance can run at a time.”

Where BA keeps your files

Everything BA stores about you lives in one folder: %APPDATA%\MSFSBlindAssist. You can open it by pressing Windows+R, typing %APPDATA%\MSFSBlindAssist and pressing Enter. Inside it are:

Because your settings live there and not in the program folder, updating or reinstalling BA never loses them.

Your First Launch

When BA starts, it opens its main window. After about two seconds you hear “Initializing, please wait”, and BA begins looking for the simulator. You can start BA before or after the simulator; it keeps trying until it finds it.

On the very first launch, and on every launch while something is missing, BA may open one or two setup windows before anything else. They appear one at a time, never stacked on top of each other.

The Set up MSFS Blind Assist window

This window opens when BA is missing data it needs:

Focus lands on a read-only text box headed What is missing, which lists only what is missing. It begins “Some data MSFS Blind Assist needs is not set up yet.” For the navigation database it says that it is not built, that building takes 2 to 5 minutes, and that for MSFS 2024 the simulator must be running at the main menu. For location data it tells you the current state, such as how much disk space the download needs.

The buttons are:

BA never remembers that you dismissed this window: it comes back on every launch until the data is there. If you would rather it did not, turn off Check for missing data when the app starts on the Updates tab of the Settings window.

Tip: While a location data download started from this window is still running, BA skips that launch’s automatic update check. An update would restart the app and cancel your download. It checks again next time.

The location data and its options are covered in Location Info and Nearest City.

The PMDG SDK Setup Check

This applies only if you fly the PMDG 737 or the PMDG 777.

What it is

PMDG aircraft share their cockpit information with outside programs through a feature PMDG call the SDK data broadcast. It is switched off unless a few lines are present in the aircraft’s options file. Without those lines, BA’s CDU window and many cockpit readouts for the PMDG stay empty.

BA checks this for you whenever you choose the PMDG 737 or 777 from the Aircraft menu, and when you start BA with one of them already selected. If any installed variant (for example the 737-800, or the 777-300ER) is missing the lines, a window opens titled PMDG 737 SDK setup or PMDG 777 SDK setup.

BA never changes PMDG’s files itself. The window tells you exactly what to do.

How to use it

Focus lands on the Instructions box, which your screen reader reads. Below it are:

The steps the window gives are:

  1. Close Microsoft Flight Simulator first. PMDG rewrites this file when the simulator exits and can drop lines added while it runs.
  2. For each file in the list, select it, press Open folder, then press Enter on the selected file to open it (usually in Notepad).
  3. If the file already has an [SDK] section, replace it with the lines; otherwise paste them at the end. Keep only one [SDK] section.
  4. Save the file and start the simulator.

If BA cannot find an options file at all, the instructions explain that PMDG creates it the first time you load that aircraft in the simulator. Load the aircraft once, then pick it again from BA’s Aircraft menu (or restart BA) and the window will list where the file is.

Like the startup data window, this one appears every time while anything is missing.

What it is

BA keeps its own database of airports, runways, taxiways, gates, navaids and instrument procedures, built from the scenery and navigation data installed in your simulator. Taxi guidance, the landing exit planner, teleporting to runways and gates, the flight planning window, approach guidance and airport lookups all read from it. Without it, those features cannot work.

There is a separate database for each simulator: one for MSFS 2020 and one for MSFS 2024. BA automatically uses the one that matches the simulator it is connected to, so if you fly both, build both.

The database is built by a tool included with BA, called navdatareader (written by Alexander Barthel, the author of Little Navmap).

When to build it

How to build it

Open the window from the File menu, Nav Database. You can also reach it from the Set up MSFS Blind Assist window’s Build navigation database button.

The window contains:

The two simulators are built differently, and this matters:

To build:

  1. Close or start the simulator as described above.
  2. Press the build button for your simulator. A confirmation message box reminds you of the requirement and says the build takes 2 to 5 minutes. Choose Yes.
  3. A progress window opens, titled for example Building FS2020 Database, with a progress bar, a status line and a Cancel button. Leave it to finish. If you press Cancel, BA asks “Are you sure you want to cancel the database build?”
  4. When it finishes, BA speaks the result, for example “FS2020 database built successfully”, and shows it in a message box titled Build Complete. If the result includes a warning, BA reads the warning in full: it matters.
  5. Press Close to return to the main window. BA then says something like “Database settings saved. Using FS2020 - 41,804 airports”.

If the build fails or is cancelled, a message box titled Build Not Completed explains why.

If your simulator has Navigraph’s navigation data installed, the database includes it, and the status line says “Navigraph data available”. Otherwise it says “No navigraph, using Microsoft’s Native nav data”. Nothing else changes: every feature simply reads the one database, whichever data it holds. If you install or update Navigraph’s data, rebuild the database so BA sees it.

The Database Mismatch Warning

Sometimes the simulator you are running and the database BA is using do not match — most often because you have only built the database for the other simulator. When you use a feature that depends on accurate airport positions (teleporting to a runway or gate, choosing a destination runway, or importing a SayIntentions taxi route), BA stops and opens a window titled Database Mismatch Warning. It says, for example, “Warning: You are running Flight Simulator 2024 but have FS2020 database selected. This may provide incorrect runway coordinates and airport data. Would you like to switch to FS2024 database now?”

If something goes wrong

Connecting to the Simulator

BA connects to the simulator on its own. You do not press a connect button.

  1. Start the simulator and load a flight. You can do this before or after starting BA.
  2. While BA is looking, its main window’s status line reads Waiting for simulator, and BA tries again every few seconds.
  3. Once the flight is loaded and BA has identified the aircraft, you hear “Connected to” followed by the aircraft’s title from the simulator, and its airline and flight number or its registration if the simulator has them. Then BA says which BA profile is active, for example “FlyByWire A320neo Profile and panels active”. The status line shows the same text.

For about five seconds after connecting, BA holds back its automatic announcements. This stops it from reading out every light and system state at once when you connect to an aircraft that is already set up. Hotkeys you press still speak straight away.

If you press a hotkey before BA has finished connecting, you hear “Not connected to simulator, please wait”.

If the simulator closes or the connection drops, BA says “Disconnected from simulator” and goes back to looking for it. When you load a flight again, it reconnects by itself.

Choosing Your Aircraft

BA has a separate profile for each aircraft it supports: its own panels, hotkeys and announcements. BA does not switch profiles for you when you load a different aircraft in the simulator. Choose the matching profile from the Aircraft menu. BA remembers your choice and uses it the next time it starts. The first time you run BA, the FlyByWire A320neo is selected.

The Aircraft menu lists the ten supported aircraft, in this order:

  1. FlyByWire Airbus A320neo
  2. FlyByWire Airbus A380X
  3. Headwind Airbus A330-900neo
  4. Fenix A320 CEO
  5. PMDG Boeing 737 (the 737-600, -700, -800 and -900)
  6. PMDG Boeing 777
  7. HorizonSim Boeing 787-9
  8. iFly Boeing 737 MAX8
  9. TFDi Design MD-11
  10. BlueBird 757-200

To open the menu, press Alt, then use Right Arrow to reach Aircraft and Down Arrow to move through the list; the current aircraft is marked as checked. Press Enter on the one you are flying. You hear “Switched to” and the aircraft name, and the main window’s Sections list fills with that aircraft’s sections.

Note: If the profile you choose does not match the aircraft loaded in the simulator, panels and hotkeys will not work properly. Always pick the profile for the aircraft you actually loaded.

Each aircraft has its own chapter in Part 8: see Airbus Aircraft and Boeing Aircraft and the MD-11.

The Main Window

The main window is where you operate the aircraft’s panels. Take a few minutes to learn it before your first flight; everything else builds on it.

Layout

From top to bottom and left to right, the window contains:

The window title is normally MSFS Blind Assist. On some aircraft it also shows the current flight phase.

Moving around

The Tab key moves from the Sections list, to the Panels list, to the first control in the panel, and on through the controls. Shift+Tab goes back. Three shortcuts jump directly, as long as the main window has the focus and you are not in Input mode:

Key What it does
Ctrl+1 Focus the Sections list
Ctrl+2 Focus the Panels list
Ctrl+3 Focus the Status Display of the current panel (and fill it if it is empty)
F5 Refresh the current panel’s Status Display without moving away from where you are

A typical way to operate something:

  1. Press Ctrl+1, and arrow up or down to the section, for example Overhead.
  2. Press Tab (or Ctrl+2) to reach the Panels list, and arrow to the panel, for example Lights.
  3. Press Tab to move into the controls, and keep pressing Tab to reach the control you want.
  4. Change it (see below). Your screen reader tells you the new value.

If there is no Status Display on the panel you are in, Ctrl+3 says “No status display on this panel.”

The kinds of controls you will meet

Each control in a panel has a label ending in a colon, followed by the control itself. You will meet these types:

The Status Display

Many panels end with a Status Display: a read-only list (its screen reader name is Status display, updates live (F5 to refresh now)) that shows live readings for that panel, one per row — for example voltages, pressures, temperatures, quantities, or the pages of a system display. Below it is a Refresh button.

On the Airbus aircraft in particular, Status Displays are where you read much of what a sighted pilot reads off the cockpit screens.

When the simulator is not connected

You can browse sections, panels and controls before BA connects, but controls have no live values yet and changing them has no effect. Values appear once BA connects.

Output Mode and Input Mode

This is the most important idea in BA, and the one that beginners most often find confusing at first. Read this section slowly, and try each step as you go.

Why there are two modes

BA’s hotkeys have to work while the simulator has the focus, and the simulator itself uses almost every key on the keyboard. If BA permanently took over keys such as A, S or H, you could no longer use them in the simulator. So BA owns only two keys all the time: the two square bracket keys. Pressing one of them puts BA into a mode for a moment, during which the other keys mean BA commands. After one command, the mode ends and your keyboard goes back to normal.

A simple way to remember it: Output is information coming out of the aircraft to you; Input is you putting something into the aircraft.

How to use a mode

  1. Press ] (for Output) or [ (for Input). You hear “output” or “input”.
  2. Press the command key or key combination, for example A, Shift+H or Ctrl+T.
  3. BA carries out the command, and the mode ends by itself.

For example, to hear your altitude: press ], hear “output”, then press A. In this guide that is written “Output A”; “Input Shift+R” means press [, then Shift+R.

Cancelling a mode

If you pressed a bracket key by mistake, or changed your mind:

The mode does not time out. It stays on until you give it a command, cancel it, or press Escape. If you press a key that is not a command in that mode, nothing happens and the mode stays on, so if you are not sure whether you are still in a mode, press the bracket key again: if you hear “cancelled”, you were.

While you are in one mode, the other bracket key does nothing. Cancel the first mode before entering the other.

Warning: While a mode is active, BA has taken over its command keys across the whole computer. If you then try to type in the simulator or another program, those letters will trigger BA commands instead. If keys seem to stop working, a mode is probably still active: press the bracket key you last used to cancel it.

Keys that work without a mode

A few keys are not part of either mode:

Suspending hotkeys

If another program needs the bracket keys — for example while you type a chat message to ATC — open the File menu and choose Suspend Hotkeys. BA says “Hotkeys suspended” and stops listening to the brackets entirely. Choose it again to turn hotkeys back on; you hear “Hotkeys resumed”. If BA cannot take the keys back because another program is now using them, it warns you: “Warning: failed to re-register hotkeys. Another application may be using the bracket keys.”

Different aircraft, different keys

The two modes are the same on every aircraft, and many keys are shared. Output A, S and H read altitude, indicated airspeed and heading on every supported aircraft. But each aircraft also has its own keys for its own systems, and the same key can do different things on different aircraft. The Hotkey List (next section) always shows the keys for the profile you have selected.

Note: BA listens for the keys Windows calls the bracket keys on a US or UK keyboard (the two keys to the right of P). On some other keyboard layouts Windows gives those codes to different physical keys. If pressing your bracket keys never turns a mode on, try the two keys to the right of P, or ask for help on the Discord.

The Hotkey List

What it is

The Hotkey List shows every hotkey for your current aircraft profile, grouped into categories, with Output mode keys and Input mode keys clearly separated. It is the quickest way to find a key while you are learning.

How to use it

  1. Open the File menu and choose Hotkey List.
  2. The window opens with focus on the Search box (named Search by category or keyword). Type a word such as fuel, autopilot, taxi or heading, and the list below shows only the matching entries. You can also arrow through the box to pick a category; the first choice, All Categories, shows everything.
  3. Press Enter in the Search box to jump into the list itself.
  4. Shift+Tab back to the Show box (named Show Hotkey Mode) to show All hotkeys, only Output hotkeys, or only Input hotkeys.
  5. Read the list with the arrow keys. It is a read-only text box, so you can also use your screen reader’s normal reading commands.
  6. Press Ctrl+F at any time to return to the Search box, and press OK or Escape to close the window.

If nothing matches, the list says so, for example No hotkeys match “fuel” in input hotkeys., which tells you to try the other mode.

The same lists are in the HotkeyGuides folder inside BA’s program folder, as text files you can open in any editor, and the full set for every aircraft is reproduced at the end of this guide in the Hotkey Reference.

The Menus

BA’s menu bar has four menus. Press Alt to reach it, then use the arrow keys.

The File menu

The Aircraft menu

Lists the ten supported aircraft, with the current one checked. See Choosing Your Aircraft.

The Extras menu

Holds tools that work alongside the simulator. It currently has one item, Volanta…, which opens a text view of Volanta’s live map: Volanta users and network pilots around you, your friends, and online ATC. You can also open it with Output Shift+O. It is described in Volanta.

The Help menu

The Settings Window

Open the Settings window from the File menu, Settings…. It holds nearly every option in BA, organised into tabs. Each tab is explained in full in the chapter for its feature; this section gives you the map.

How to use it

The tabs

Tab What it covers
Announcements Whether BA speaks through your screen reader or through Windows speech, and general announcement options: the nearest-city auto-announce, seconds in time readouts, GSX tooltips, 1,000-foot crossings.
Weather ActiveSky integration, the automatic weather, turbulence, icing and SIGMET/AIRMET announcements, and outside-temperature units.
VATSIM Announcing VATSIM activity from vPilot.
GeoNames Downloading the offline location data used by Output C and Location Info, and the distance ranges and units it uses.
SimBrief Your SimBrief username, for loading flight plans.
AI Your AI provider (Gemini or Claude), its key and model, for reading cockpit displays and describing scenery and routes.
Audio Which sound device BA’s guidance tones play through.
Hand Fly Hand-flying feedback, visual guidance tones, Takeoff Assist and the rollout centreline tone.
Taxi Guidance The taxi steering tone, taxi callouts, distance units, docking guidance, online taxiway names, airport buildings, and SayIntentions taxi import.
First Officer The First Officer’s automation (gear, flaps, autopilot, landing lights, altimeters, seat belt signs, center fuel pumps), the PMDG 737 GPWS test type, and whether flows speak each step.
Updates Release or preview builds, automatic update checks, the startup data check, and the version you are running.

The Announcements tab, including the screen reader or Windows speech choice, is described in Announcement Settings.

Updates

What it is

BA can find, download and install new versions for you from GitHub, without you visiting the website.

How it works

When Check for updates automatically when the app starts is on (it is on by default), BA checks once, just after its main window appears. The check never delays startup and is completely silent when there is nothing new, or when it cannot reach the internet. If an update is available, BA says, for example, “Update available: version 8.1.0”, and opens the update window. It does this on every launch while an update is waiting; turn the check box off if you would rather check by yourself.

To check at any time, choose Update Application from the File menu. BA says “Checking for updates…“. If you are up to date, it tells you, for example “You are running the latest version (8.0.0).” If the check fails, it tells you why.

The Update Available window

The window, titled Update Available, shows:

Press Update Now to download the update. The status line shows the download’s progress, then “Download complete. Ready to install.” BA says “Launching updater. Application will close and restart.”, closes, installs the update into the same folder, and starts again. Your settings and databases are not touched.

Release builds and preview builds

On the Updates tab of the Settings window, under Which builds should MSFS Blind Assist offer?, you can choose:

To go back from a preview to the release, set the channel back to Release builds, then choose Update Application from the File menu. BA offers the current release even though its version number is lower than your preview. The window is then titled Return to Release Build, says so plainly, and its button reads Install Release.

Note: A newer build can store settings an older build does not know about. If you go back to an older build, those particular options are reset to their defaults; everything else is kept.

The Updates tab also shows Version you are running, the exact version and build. Include it whenever you report a problem.

Logs and Getting Help

Logs

BA writes diagnostic logs as it runs. They do not affect how it flies, but they are what lets the developers understand a problem you report. All logs are in one folder:

%APPDATA%\MSFSBlindAssist\logs

To open it, press Windows+R, type %APPDATA%\MSFSBlindAssist\logs and press Enter. The main log is debug.log. Others cover particular features, for example startup.log (replaced on every launch), taxi_guidance.log, taxi_router.log, landing_exit.log, takeoff_assist.log, ground_traffic.log, gsx.log and sayintentions.log. Logs are kept to a sensible size automatically, with older entries rotated away.

Reporting a problem

When something does not work as this guide describes:

  1. Note what you did, what you expected, and what happened instead — including what BA said.
  2. Note your BA version and build. It is on the Updates tab of the Settings window and in Help, About, for example v8.0.1-pre.7 (build 4f7e7ba). The build part names the exact code you were running.
  3. Note the aircraft and the simulator (2020 or 2024), and the airport if it is a ground problem.
  4. Collect the logs folder. The easiest way is to zip the whole %APPDATA%\MSFSBlindAssist folder, which contains your settings and logs together. If that is too large because of the databases, zip just the logs folder.
  5. Share it with the BA community on the project’s Discord server, or on the project’s GitHub page.

Before reporting, it is worth checking Troubleshooting and FAQ in the appendices, and the “If something goes wrong” part of the feature’s own section.

Getting help

The BA community meets on Discord, where you can ask questions, get help setting up, and talk with other blind pilots. The invitation link is in the README on the project’s GitHub page. The Glossary explains aviation and BA terms you may meet in this guide.

Your First Ten Minutes

If you want to try BA straight away, follow these steps. Each links to the section with more detail.

  1. Install the .NET 10 Desktop Runtime and, if your aircraft needs it, the MobiFlight WASM module. See What You Need.
  2. Extract BA and run MSFSBlindAssist.exe. See Installing.
  3. If the Set up MSFS Blind Assist window opens, start the location data download, then build the navigation database for your simulator. Remember: close MSFS 2020 before building its database; have MSFS 2024 running at its main menu before building its database. See The Navigation Database.
  4. Start the simulator and load a flight, parked at a gate, in an aircraft BA supports.
  5. In BA, open the Aircraft menu and choose that aircraft. You hear “Switched to” and its name.
  6. Wait for “Connected to” and “Profile and panels active”.
  7. Press ], hear “output”, then press A. BA reads your altitude. Try Output H for heading and Output S for airspeed.
  8. Switch to BA’s window (Alt+Tab), press Ctrl+1, and arrow through the Sections list. Tab into the Panels list and then into a panel’s controls to explore. Press Ctrl+3 to jump to a panel’s Status Display.
  9. Open File, Hotkey List, and search for something you want to do.
  10. Press Output Shift+C to open the First Officer, if your aircraft has one. Press Ctrl+Tab to move between its Flows and Checklists tabs, and Escape to close it. See The First Officer and Checklists.

When you are comfortable with those, read Core Concepts to learn what BA announces and what its tones mean, then follow the guide through Planning Your Flight and on to the ground.