BMS Companion 1.3.8 — WDP for Falcon BMS 4.38.1, EZBoards and WDP modes, live MFDs, weather generator, radio log

Download: https://github.com/Scorpion-41/Falcon-BMS-Companion/releases/tag/1.3.8

BMS Companion 1.3.8 adds a port of Weapon Delivery Planner for Falcon BMS 4.38.1, running on the PC, Android and in the browser. Also in this release:

• EZBoards mode and WDP mode for the Mission section;
• one mission picture on every map, limited to the threats the mission knows;
• live MFDs in an F-16 bezel;
• Dashboard pages and a Weather card;
• a weather generator based on WeatherGen;
• a Radio page and automatic taxi from BMS's debug log;
• carrier decks drawn from BMS's ship models;
• an Info box (coordinates, elevation, frequencies) on every airfield page;
• parking numbers as BMS Ground assigns them, and fixes.

---

The Planner is a port of Falcas's Weapon Delivery Planner (WDP) to Falcon BMS 4.38.1; its pages, attack geometry, ballistics and performance planning are his work. The weather model is Craig Andera's WeatherGen.

---

1. EZBoards mode and WDP mode

A switch at the top of the Mission section (and in Setup) selects the data source for every device.

• EZBoards mode (default): PRINT in BMS fills the Mission section, EZBoards makes the cockpit kneeboards, and the Planner is locked.
• WDP mode: open the flight from a save in the Planner, plan it, Save to DTC and press Populate from Planner. The Dashboard, Map, Taxi, Briefing, Comms and VR boards then show that flight; a printed briefing of the same flight is used as is, so both modes read the same. Cockpit kneeboards come from the Planner's Upd Kneeboard; EZBoards and Run HTML Briefing are paused.

Populate runs only when pressed and prompts if there are unsaved edits.

Each new mission starts clean. BMS keeps lines, PPTs, targets and nav offsets in the cartridge until they are overwritten. When a new mission begins (a PRINT of another flight, or another flight opened in the Planner), the PC removes the entries the Planner saved for an earlier flight, provided they are unchanged. A mode switch does the same and restores BMS's own kneeboard pages over the other mode's earlier ones.

2. WDP for Falcon BMS 4.38.1 — Mission → Planner

Every control is in WDP's original place; the data is BMS 4.38.1's own (airports, radios, HARM codes, PPT types, aircraft, stores, pylons and racks).

Order of work (also shown by Steps on the toolbar, with the current step marked):

1. In BMS: open the campaign or TE, pick your flight and seat, set the loadout.
2. In BMS: open the DTC, set what you want, SAVE; then save the campaign or TE.
3. In BMS: PRINT the briefing.
4. Open mission… → pick the save, your flight and seat (WDP's "Precision STPT?" question is asked; No is the default).
5. Plan: DataCard, DTC, Attack, Map.
6. Save to DTC.
7. In BMS: open the DTC again → LOAD → SAVE.
8. Populate from Planner.
9. Upd Kneeboard.
10. FLY, and LOAD on the DTE page in the cockpit.

For custom weather, generate it on the Weather tab and save it in BMS before step 3; later steps read what BMS has saved.

Pages:

• Briefing / DataCard / Coordination Card: filled from the printed briefing of the flight, or from the save (situation, intel, ROE and emergency texts worded as BMS words them). Weather is read from the save's own weather file. The card stays on the planned flight.
• Map (new): the cartridge as the HSD will show it (route, lines, PPT rings, bullseye, attack points), beside what the mission provides and the cartridge does not yet hold (tanker/AWACS tracks, threats, airfields), added with a tap. Includes an HSD preview and WDP's MAP tab tools: grid, bullseye rings, airfields and VORTACs, JSTARS, search radars, ships, position/elevation/variation readout, Measure, Auto PPT, Change Area and Save Map.
• DTC: all sixteen tabs, with From mission… on nine of them (tracks as HSD lines, spotted SAM sites as PPTs, steerpoints from airfields or targets, comms, TACAN/ILS, laser codes, HARM tables).
• Attack: Pop-up, HADB and TOSS in one tab with a rail to switch. TGT STPT selects the target and, in VIP mode, IP STPT the IP (VRP needs none). IP STPT at the VRP places a steerpoint at the VRP and plans the attack as VIP from it. Save to DTC on an attack page also fills the DataCard's Delivery section, so the card and the cartridge agree. The attack last changed is drawn the same way on every map (Planner Map, kneeboard, Mission map after Populate). Target elevation comes from BMS's height map; every ELEV can be typed.
• Performance: WDP's engine tables, any F-16 type, and a new Loadout window (grouped store list, search, Mirror, totals).
• ATO Targets: WDP's ATO Target List with latitude and longitude.

Save to DTC writes the cartridge directly, as WDP does, changing only the edited lines. Upd Kneeboard writes the cockpit kneeboard pages in BMS's own format: in WDP mode the DataCard on page 1 and the Coordination Card on page 2, plus optional briefing, weather, target list, route map, attack profile, ground charts or a picture file. Each page shows which tool wrote it.

Options → Settings, Get DTC File and Save DTC are where WDP has them, and every control has a tooltip. Planner files are kept in User\BMS Companion Planner inside the BMS folder, in WDP's formats.

How the Planner differs from Falcas's WDP 3.7.24

The same as WDP:

• Pages and controls laid out as in WDP.
• Attack geometry, ballistics and performance tables give WDP's results; every calculation is checked against WDP itself.
• Latitude and longitude as WDP prints them, which match BMS's own ACMI recordings and AIPs to within 2 m.

Corrected:

• BMS 4.38 weather files could not be read, so the card showed no weather.
• Some TE and training missions did not load.
• Precision steerpoints could be lost or shifted on save, and a campaign save cleared BMS's route in the mission file.
• ILS frequencies below 109.00 were altered; HARM codes were missing or wrong; IFF codes lost leading zeros.
• Offset aim points on steerpoints 24-25 were never read back, and a cartridge could carry VIP and VRP lines for one attack.
• The card's TGT in HUD did not follow the page's check; TOSS VIP bearings had north and east swapped; HADB and TOSS heights assumed a sea-level target.
• Pressure altitude had the wrong sign; F-16 variants named differently by BMS were not found on the Performance page.
• The ATO Target List printed no coordinates, and Korea TvT had none at all.

New in the Planner:

• Runs on the PC, on Android and in any current browser, through the PC that holds the saves and the cartridge.
• BMS 4.38.1 data throughout: airports, ILS, TACAN, frequencies, theaters, aircraft, weapons, pylons and racks.
• Open mission… and Pick a flight from any device, for every installed theater.
• Map page: HSD preview, items added to the cartridge as PPTs or lines with a tap, and intel without unspotted sites.
• From mission… on nine DTC tabs.
• Attack rail, IP STPT and IP STPT at the VRP; Save to DTC on an attack page also fills the DataCard.
• Loadout window on the Performance page.
• Upd Kneeboard keeps each page file's format, and accepts picture files.
• Populate from Planner sends the plan to the Mission section (WDP mode).
• Steps and the Guide; with a TE open, Save to DTC also writes the TE's mission file.

Phones and tablets: pages fit the screen and never scroll; text boxes are edited in a bar above the keyboard with Next and Done; double tap zooms.

3. One mission picture on every map

The Mission map, the VR map board and the Planner's Map page draw the same mission: route, tanker/AWACS tracks, PPT rings, the flight's airfields, bullseye and the mission's threats (the sites the briefing names, placed from the save). Sites the side has not spotted are never shown, including from the live feed. Hostile SAM rings use one red on every map. In EZBoards mode, route and tracks appear after PRINT rather than only in 3D.

Hostile contacts from the live feed are off by default on the map, the Dashboard, the AWACS page and the VR boards; Setup → Show hostile contacts (live) turns them on.

4. Live MFDs

• The actual MFD pictures from BMS in an F-16 bezel; the buttons and the BRT/GAIN rockers press BMS's own keys. Side by side or stacked, with a full-page view.
• Requires Export RTT Textures → Enable on the BMS Launcher's main page; the display states what is missing.
• If BMS runs as administrator and BMS Companion does not, Windows blocks the button presses; the card reports it. Run both with the same rights.
• There is no MFD VR board; in VR the cockpit's own displays are in view.

5. Radio page and automatic taxi

Requires BMS debug mode and Display Radio Subtitles (SETUP → SIMULATION).

• Radio page: every radio call of the session, grouped (ATC, AWACS, Tanker, My flight, Flights, Other), with sim time and search.
• Automatic taxi: the Taxi page and the Live taxi VR board follow Ground and Tower — the runway cleared to before departure, and the parking spot assigned after landing.
• Optional clean-up of old debug logs (Setup, off by default) to the Recycle Bin.

6. Weather generator (Mission → Weather)

A port of WeatherGen's model (MIT licence), matching WeatherGen cell for cell except for three corrected WeatherGen errors.

• Moving highs and lows, fronts, and wind that veers with height; override regions for storms; settings per theater.
• Save map adds an entry to BMS's Map Model list; Save series adds update maps from the mission's start time.
• To use a map in BMS: Weather → Map Model → BMSC <name> → MAPS AUTO UPDATE (on for a series) → SAVE WTH, then save the TE or campaign, before PRINT.
• All BMS theaters are supported. BMS's own maps are never changed.

7. Airfields and carriers

• Info box under the ground chart on every airfield page, in every theater: latitude and longitude as BMS shows them, elevation, and the field's frequencies. Tap a value to copy it.
• Carrier decks drawn from BMS's own 3D models (19 ships); with ACMI recording on, the jet is shown on the deck.
• Parking numbers match BMS Ground ("park 04"); spots show size and the alert cell as on the theaters' parking charts.

8. Other changes

• Dashboard: five pages and a Weather card; the previous layout becomes page 1.
• Reference: Airfields | Map | Threats | Arsenal with the theater picker.
• Checklists: Previous/Next, one Starting Engine checklist, and a complete warning and caution light index for the F-16 and F-15C.
• Smooth zoom on every map and chart; faster maps on Android.
• Graphics setting for older PCs (OpenGL or software rendering).

Fixed:

• Korea's tanker/AWACS tracks and friend/foe were read from the wrong file;
• tanker tracks appeared only in 3D;
• recon targets were drawn as part of the route, and the Taxi page could open on the wrong field;
• AWACS and tanker PPTs were drawn as small threat rings;
• the Traffic and Hostiles switches depended on each other;
• every US carrier in Korea was identified as the Carl Vinson;
• the Briefing could treat the package lead's flight as the player's;
• EZBoards on PRINT occasionally did not run;
• the Taxi page's cards were out of reach on a tablet held sideways;
• in the browser, one wheel step zoomed the map fully in, and some symbols showed as empty boxes.

Update: About → Download → Install. Existing settings are kept.

---

BMS Companion 1.3.7 — a real ground chart for every airfield in BMS, generated from the game's own files

TL;DR: My free Falcon BMS companion app just got a Taxi page: a proper airport ground chart for 1,840 airfields across all 19 theaters. Runways, every taxiway with its letter, hold shorts, the actual pavement, the buildings, and every parking spot with the number BMS gives it. Pick your spot and it gives you the taxi clearance and draws the route. It is all generated from Falcon BMS's own game files — There is also a new Config section that edits Falcon BMS's settings files from your tablet, and the charts are on your VR kneeboards too.

---

Download: https://github.com/Scorpion-41/Falcon-BMS-Companion/releases/tag/1.3.7

---

The Taxi page

What's on it

• Every runway, with its real heading, threshold markings and length
• Every taxiway, with the letter BMS signs it with on a yellow board where BMS puts its own sign
• Hold short points
• The actual asphalt — the full aprons, the dispersals, the turnarounds that loop from one runway end to the other
• Every building the sim places at the field, at its own position and heading: hardened shelters, hangars, fuel, towers, the walls around the ramps
• Every parking spot, with the number BMS gives it — and you can see which ones have a roof, because a shelter or a hangar is drawn as a bay you taxi into nose-first

How you use it

1. Open Mission → Taxi. If BMS is running it already knows where you are: your field, and the spot you spawned on.

2. Hit the RWY button for the runway in use. In a mission it's usually picked for you — BMS parks you on the half of the ramp nearest the active runway, so the spot you're sitting on tells the app which runway the field is working.

3. Tap your parking spot on the chart (or its number in the list).

4. Read the clearance:

   > Taxi to runway 26 via B, A, H. Hold short runway 26. > 1. Start on spot 39 — hardened shelter > 2. Taxi onto C — 540 ft > 3. Turn right, still on C — 3,375 ft > 4. Hold short of runway 26

   The route is drawn on the chart in blue, with the turn called at each junction.

5. Just landed? Hit Taxi in, pick the spot you were given, and it draws the way in from the runway.

Day or night chart, zoom with the wheel/pinch/buttons, and it all works with BMS closed — tap a spot from an armchair and you get the same clearance. The whole thing is in the app, so a phone or tablet with no BMS install still has all 1,840 fields.

---

On your VR kneeboards

Two new board kinds for OpenKneeboard:

• Live taxi — draws the field you are actually standing on, briefed or not, with your jet on it and whatever is ahead of you up the page, so the chart turns as you turn. Its pages are zoom steps, so the next-page / previous-page buttons you already have bound zoom the chart in and out — from the whole field down to a couple of stands either side. There's no mouse in VR, so a bound button is the only control there is.
• Ground chart — one page per runway end, to read before start-up or on the way in, with your position marked.

Both are dark by default with a Configure button for day/night and which way up. Charts are also turned to whatever angle fills the board, since a kneeboard is tall and thin and most airfields aren't.

---

Also new: Config

Falcon BMS keeps several hundred settings in a text file its own screens never show you. The new Config section lists all 219, says what each one does (in BMS's own words, read out of the stock config your version ships with), and writes only the ones you change — from your tablet, on the sofa, for the flight about to start.

It's off until you turn it on (Setup), and it won't do anything until you press Click to Back Up and Enable, which copies your Falcon BMS User.cfg into a BackUp folder beside it — once, and never overwritten. You get three profiles to switch between: profile 1 is a copy of what you already had, 2 and 3 start empty (which in a config file means everything at its default). Settings your file actually holds are listed first and marked; everything else is shown dim at its default, and changing one moves it up — which is exactly what happens in the file.

It never touches the block your BMS launcher writes at the end of the file, it never writes outside User/Config, and it never writes a file in place — the new one is written beside it and moved across, so a failed write can't leave you with half a config.

---

The rest of 1.3.7

• Setup is its own section now instead of a tab inside Mission — it's what you do once, before any mission, and a device that couldn't reach the PC used to have to open the very section that was empty because of it.
• The app is 52 MB smaller. The flat pictures of the ground/parking/end-of-runway charts from BMS's docs folder are gone; the app draws all three itself now. Instrument charts are untouched — every approach, SID and STAR plate is still there.
• Demo mode is gone, so no screen can quietly be showing a made-up mission.
• Kneeboards are generated when you press PRINT by default.

Fixed since 1.3.5: kneeboards-on-PRINT could only be switched on at the PC while every client's page said otherwise; the live map flickered down one edge on a VR board; map labels were a smudge on the Chart style (white text on near-white terrain); airfield symbols could hide behind a steerpoint ring; and other aircraft sat a small constant offset from your own, because the ACMI feed uses a reference of its own.

---

Video of old version.

Newest Update v1.3 (16/09/2026): https://github.com/Scorpion-41/Falcon-BMS-Companion/releases/tag/1.3

- The app runs smoothly but the video was recorder in 30fps.

- The first part Mission section requires pc brdige program to be running to stream live data to app.

- When in boards section (Generate Boards section) clicking Print in-game automatically populates the app and the in-game kneebaords with the new generated boards without having to alt tab or anything, it is a toggle option in bridge program (credits to EZBoards).

- You need to press "F" in-game for AWACS feed to start working, you can toggle showing hostiles data on/off.

- All other sections (which are basically an Encyclopedia/Guide for BMS) run without needing the pc bridge.

Reddit Post: https://www.reddit.com/r/falconbms/comments/1wgffog/release_falcon_bms_companion_app/

Forum: https://forum.falcon-bms.com/topic/33613/release-falcon-bms-companion-app

GitHub: https://github.com/Scorpion-41/Falcon-BMS-Companion

Update v1.3 (16/09/2026): https://github.com/Scorpion-41/Falcon-BMS-Companion/releases/tag/1.3

Hi everyone,

I'd like to share a free, open-source tool I've been building: Falcon BMS Companion, an Android app for phones and tablets with a small Windows bridge. The goal is simple: never alt-tab out of the sim. Frequencies, the alternate's ILS, the loadout, the comm ladder, threat ranges, kneeboard generation: all of it on the tablet next to your HOTAS.

The project has two parts:

1. Live Mission section. BMS Companion Bridge runs on the BMS PC. It reads your current mission and sends the raw data to the app over your local network. The app draws everything itself. There's no screen capture or video stream, so there's no frame-rate cost.
2. Offline reference. Aircraft, loadouts, the Threat Guide, airfields with charts, HOTAS, checklists, comms and a bullseye trainer. It's all extracted from the BMS 4.38 install and manuals, and needs no PC.

It's free, with no ads, no accounts and no internet connection needed. The bridge only listens on your LAN and never writes to the BMS folder.

Download and source: https://github.com/Scorpion-41/Falcon-BMS-Companion

---

Live Mission section (requires the PC bridge)

Map

• Ownship on the theater map with the flight plan, target steerpoints, PPT threat rings, markpoints and bullseye rings
• AWACS picture: friendly and hostile aircraft, helicopters, ships and missiles in flight, each with a speed vector, callsign and altitude. The source is BMS's built-in Tacview real-time telemetry server, so the Tacview program isn't needed.
• Tap a contact for BRAA from ownship, its bullseye position and aspect (HOT / FLANK / BEAM / DRAG)
• Tap a threat ring to identify it. Tap any point on the map to get its bullseye bearing and range.
• Departure, arrival and alternate airfields are marked. Tap one to open the airfield page with its charts.
• Follow mode and layer toggles (route, threats, traffic, hostiles, fields, labels)
• Tablet layout adds a side panel with ownship data, a Picture list of hostiles sorted by range, and the steerpoint list

Flight

• Altitude, KIAS / Mach, heading, ground speed, vertical speed, G / AOA
• Total, internal and external fuel, fuel flow and bingo. Chaff and flare counts.
• Ownship bullseye position, TACAN, UHF channel, Zulu time
• ALR-56M-style RWR scope with LAUNCH and LOCK indications and a plain-text emitter list
• DED replica

Briefing

Parsed from the briefing.txt written by the PRINT button:

• Mission, task, package, take-off, push time and TOT
• Departure, recovery and alternate airbases with TACAN, tower, ILS per runway and field elevation, one tap to the charts
• Flight plan with TOS, altitude and bullseye bearing/range for every steerpoint (tap to show it on the map)
• DTC targets, package and roster, loadout for each jet (each store links to its Arsenal page)
• Threats linked to the Threat Guide: a mention of "SA-6" opens the SA-6 entry
• Support (AWACS / tanker), weather, ROE, emergency procedures

Comms

• Comm ladder, grouped by agency, with the currently tuned UHF frequency highlighted
• DTC UHF/VHF presets, IFF codes and Link 16

Boards (EZBoards)

• A Generate kneeboards button on the tablet. The bridge runs EZBOARDS.BAT hidden (no console window over the sim), checks the result and sends back success or failure with the full log.
• Optional: run EZBoards automatically every time the briefing is printed
• The kneeboard content (package with TACANs, comm ladder, steerpoints with min fuel, targets, weather) is also shown natively in the app. It's read with EZBoards' own xbrief.exe, so it matches the in-cockpit boards.

Setup

• Automatic discovery of the bridge on the LAN (UDP broadcast), or a manual IP
• A status view shows what the bridge can see: BMS running, UI or 3D, briefing printed, DTC saved, AWACS feed, EZBoards
• Built-in setup guide and troubleshooting, plus a keep-screen-on option
• Demo mode (synthetic SEAD mission in Hellas with moving traffic) to try every screen without BMS running

---

Offline reference (no PC bridge needed)

Arsenal

• 323 flyable aircraft types from KTO and all installed add-on theater databases, with per-theater variants (loadouts differ between databases)
• Performance and specs: max speed, ceiling, corner speed, max G and AOA, internal fuel, weights, radar, RWR, countermeasures, flight model type
• Station-by-station loadouts with rack capacity, and a weapon × station matrix
• 518 weapons and stores with sim data (campaign range, blast radius, drag index, hit chance…) and the list of aircraft that carry each one

Threat Guide

• SAMs, AAA, radars, MANPADS, fighters, air-to-air missiles and ships, split into OPFOR and BLUEFOR
• For each entry: RWR symbols (ALR-56M and ALR-93), HARM ALIC codes, min/max range and altitude, radar and lock range, max speed and G, sensors, tactics and engagement-envelope diagrams
• Range comparison chart, air-to-ground weapons chart, countermeasure effectiveness scale, aircraft formations
• HARM & RWR section: ALIC tables, RWR symbols and modifiers, audio tones, HARM modes, threat table setups
• TacRef Encyclopedia: 1,346 entries (vehicles, ships, aircraft, munitions) from the tactical reference database

Airfields

• 519 unique airfields across the five theaters with their own terrain (Korea KTO, Balkans, Hellas, Israel, Falklands), covering 19 theater databases including the add-ons built on them
• Runways with ILS per runway end, TACAN, all frequencies (tower, ground, approach, ATIS, base ops, LSO), ATC patterns, IFR/VFR minima, nearest diverts, navaids
• 1,386 airport and parking charts, fullscreen with pinch-to-zoom
• Theater map with airfields, TACANs, navaids and towns. Search by name, ICAO, TACAN channel, ILS frequency or town.
• Flight and agency frequency lists from RadioMap.dat

Cockpit

• HOTAS illustrations for the F-16C/D (A-A and A-G stick and throttle, from the Dash-34) and the F-15C. Tap a numbered control to see every switch position with its function and key callback, filtered by master mode or sensor.
• Checklists for the F-16CM, F-16CJ and F-15C, normal and emergency, with tick-off and step search
• Comms & Brevity: 590 brevity words, a 935-term glossary, CAS / 9-line, ATC procedures, tanker and AWACS calls, IFF modes, AI wingman commands, NATO alphabet
• Calculators:
  • Fuel & bingo, endurance
  • Bearing and distance between airfields with ETE
  • Wind triangle (heading to fly, ground speed, crosswind and head/tail components)
  • Descent planner (start-descent distance, required VVI)
  • Turn performance (radius, rate, standard-rate bank, load factor)
  • TAS / Mach / CAS (ISA)
  • Unit conversions (hPa / inHg, lb JP-8 / gal / L)

Bullseye Trainer

A situational-awareness mini-game with five modes:

1. Plot the call: tap the position of an AWACS bullseye call
2. Call your bullseye: read ownship position off the HSD
3. BRAA from bullseye: convert a bullseye call into BRAA from ownship
4. Clock & reciprocal drill: clock positions, reciprocals and beam headings against the timer
5. Theater map: plot calls on real theater geography

There are three difficulty levels (Rookie, Wingman, Flight Lead). Higher levels add longer ranges, tighter tolerances, shorter timers, no ring labels and a heading-up display. Best scores are saved for each mode and level.

General

• Global search across aircraft, stores, threats, airfields, ICAO, TACAN, frequencies, brevity and HOTAS
• Favorites on any page
• Dark, high-contrast UI
• Phone layout with a bottom navigation bar; tablet layout with a navigation rail and split views

---

The PC bridge

• A single self-contained .exe: no installer, no .NET runtime required
• Setup guide with live checks on first launch: BMS found, firewall, app connected, briefing export settings, DTC saved, AWACS feed configuration, EZBoards and the .NET 8 runtime. Buttons pick folders, add the firewall rules, copy the cfg lines or open Falcon BMS User.cfg in Notepad. The guide never edits BMS files itself.
• Status window with BMS state, AWACS feed, last briefing print, last EZBoards run and the last app request
• Finds the BMS install from the registry and follows g_sBriefingsDirectory
• Optional firewall rules limited to the local subnet (TCP 47474, UDP 47475)
• Tacview port and password settings, custom app port, start minimized to the tray

Where the data comes from

Data	Source
Ownship, RWR, DED, steerpoints, PPTs, bullseye, theater	BMS shared memory (FalconSharedMemoryArea, …Area2, …AreaString)
Other aircraft (AWACS picture)	BMS built-in Tacview real-time telemetry (port 42674)
Briefing, package, loadout, comm ladder, weather	User\Briefings\briefing.txt (PRINT button)
Steerpoints before 3D, targets, PPTs, radio presets	User\Config\<callsign>.ini (DTC Save)
Kneeboard tables	EZBoards bin\xbrief.exe

The bridge only reads BMS data. The one thing it runs is EZBoards, and only on request; EZBoards then writes its kneeboard textures as usual.

---

Setup

Requirements: Android 8.0 or newer (phone or tablet) on the same LAN as the BMS PC. Windows with Falcon BMS 4.38. The .NET 8 runtime is only needed for EZBoards itself.

1. Run BMSCompanionBridge.exe on the BMS PC. Its setup guide opens on first launch. Allow it on private networks when Windows asks, or use the Allow through Windows Firewall button.

2. Install BMS-Companion.apk on the device (allow installing unknown apps), then go to Mission → Setup → Find bridge.

3. In the BMS Launcher, Config → General → Briefing: enable Briefing Output to File and disable HTML Briefings. In each mission, press PRINT on the Briefing screen and SAVE the DTC.

4. For the AWACS picture, add this to User\Config\Falcon BMS User.cfg:

    set g_bTacviewRealTime 1
    set g_bTacviewAcmi 1
   

   Then start ACMI recording in 3D (default key F). In multiplayer the host controls this with g_bMPTacviewRtAllowedByServer.

5. For kneeboards in the cockpit, the 3D pilot model must be enabled (Setup → Graphics → Pilot Model). EZBoards' own page and slot settings stay in its CONFIG_USER.BAT.

A full setup guide and troubleshooting table are in the repository (docs/SETUP.md).

---

Technical notes

• Bridge: C# / .NET 8 WinForms, no third-party packages. A minimal HTTP server sends compact JSON. The app polls about four times per second, and only while the Mission screen is open. The API is documented in docs/PROTOCOL.md.
• App: Kotlin, Jetpack Compose, Material 3. All reference data and charts are bundled in the APK (~64 MB).
• Reference data: a Node.js extractor reads the objects database, BmsRack.dat, TacRefDB, CampObjData, Stations+ILS, ATC files, runway geometry and the terrain heightmaps, and renders the theater maps. The Threat Guide, HOTAS, checklists and comms were transcribed from the BMS manuals.
• The repository includes a step-by-step checklist (docs/UPDATING.md) for regenerating the data and checking the shared memory layout when a new BMS version is released.
• The code was written with the help of Claude Code (an AI coding assistant) and tested against a real 4.38 install on an Android tablet and phone.

Known limitations

• Built and tested with BMS 4.38. Other versions may need the update checklist above.
• The AWACS picture shows whatever the telemetry stream contains, including hostiles. A toggle hides hostiles for anyone who prefers friendlies only.
• Add-on theaters that reuse a base theater's terrain are shown on that base map.

---

Credits

This is an unofficial fan project, not affiliated with Benchmark Sims. Falcon BMS, its data, documentation, TacRef pictures, HOTAS illustrations and airport charts belong to Benchmark Sims and the respective add-on theater teams.

Many thanks to the BMS team and the theater developers for their work, and for the documentation that made this possible.

Feedback, bug reports and feature requests are very welcome, If anything in the reference data looks wrong, please let me know which screen and entry it is.

---

Screenshots:

https://ibb.co/VWvpjftQ https://ibb.co/bg3VqBst https://ibb.co/nNpSqFRh https://ibb.co/Y4qVFprd https://ibb.co/j9gRTfmz https://ibb.co/HpXqVLMm https://ibb.co/V0PGKzDb https://ibb.co/DPrjfBdh https://ibb.co/4ZWKqZq8 https://ibb.co/Mkzyt3Cj https://ibb.co/4wLXqXFY https://ibb.co/9HzLwxwB https://ibb.co/Rq1WVcc https://ibb.co/JjddnWbL https://ibb.co/rKCw53gz https://ibb.co/XZJy6702 https://ibb.co/TBNXwT62 https://ibb.co/m5n1rZGd https://ibb.co/m58tkhW8 https://ibb.co/20Th7x1j

---

Important Notes:

• AI was heavily used to build this project, it was intended for my personal use only, mainly as a HARMS code reference app, but i kept adding on ideas untill I got to this and thought it would be nice to share.
• I'm new to GitHub, software building and sharing, so if i'm breaking any rules, license wise, or something please let me know.
• I want to make iOS version but I don't have iOS device to test. I may though build a Web version if there is interest in it (maybe for people who use multiple monitors), with AI it doesn't really take much effort.
• Anyone is free to use the code and build anything with it, if it's better than mine don't forget to share.