This is an unofficial, independently developed tool and is not affiliated with, endorsed, or supported by Skirmish Mode Games or the BeyondATC team.

All credit for BeyondATC itself goes to its own developer — Skirmish Mode Games — this app just gives it a second screen.

Support for this app does not come from BeyondATC. Please don't ask about it in BeyondATC's Discord or through any of their other channels — for help, bugs, or questions about this app specifically, use flightsim.to (or wherever you downloaded it) instead.

BeyondATC can update and/or change their app at any time without this app in mind, and a change on their end can break this app until it's updated to match. If that happens, please be patient while it gets fixed, if that is possible.

• Listen port:
  The number at the end of the plain address your devices connect to (default 8080). Only worth changing if something else on your PC is already using that number — the app will tell you if so.
• https (on/off) + port:
  The secure address described above, and its own number (default 8081, one higher than the listen port). Leave this on unless you have a specific reason to turn it off — turning it off disables "Keep screen awake" on connected devices.
• BeyondATC → On this PC / Another PC:
  Almost everyone leaves this on "On this PC" — it means BeyondATC and MSFS are running on the same machine as this bridge. Only switch to "Another PC" (and fill in its address) if you run BeyondATC on a separate networked computer from the one running this app — see the note below.
• Start minimized:
  Opens straight to the background with no window popping up — useful if you always want it running without seeing it.
• Minimize to tray:
  When on, clicking Minimize tucks the window into the Windows notification area (near the clock) instead of the taskbar. The bridge keeps running either way; click its icon there to bring the window back. Exit always closes it fully, regardless of this setting.
• Auto-start bridge on launch:
  Starts serving devices the moment the app opens, with no need to click Start. On by default.
• Firewall:
  See below.

Changing a setting that affects how devices connect (the ports, or where BeyondATC is) restarts the bridge automatically after you save, so anything already connected reconnects on the new address within a second or two.

Running the bridge on a different PC from BeyondATC

Example: you install this app on a second PC or laptop instead of your gaming PC, and set BeyondATC's location to "Another PC" pointing at the gaming PC's IP address. This works, but there's one extra step it needs that running everything on one PC doesn't: BeyondATC itself, on the gaming PC, has to be allowed through Windows Firewall there too, so it can accept the bridge's connection coming in from across your network.

This is separate from the Firewall button described below — that one only opens the door to this app, on whichever PC it's installed on. It has no way to reach across and open a rule on a different machine. On the gaming PC, you'll need to add an inbound rule for BeyondATC's own program through Windows Defender Firewall's settings (or allow it if Windows already prompted for it and you dismissed the prompt). Without that, the bridge on your second PC won't be able to reach BeyondATC even though everything else is configured correctly.

NOTE:

• The airport map and the taxi route won't appear in this setup. They're the one thing that doesn't travel across the network. Everything else here
  reaches you through BeyondATC, which is happy to talk over Wi-Fi — but the airport layout is read from the simulator itself, and that connection only
  works on the machine MSFS is actually running on.
• So on a second PC you still get the ATC log, frequencies, D-ATIS, the action buttons, the moving map, the traffic and the trail. You just won't
  get taxiways, stand names or the taxi route drawn. Nothing will tell you why — the airport simply won't be there. If you want those, run the bridge
  on your gaming PC instead.

Letting devices through Windows Firewall

Windows blocks other devices from reaching this app until you explicitly allow it. The Settings → Firewall row shows whether that's already been done, and one button — "Allow devices through" — does it for you. Windows will ask for administrator permission once; after that, it never asks again.

The permission it adds is deliberately narrow: only this program, only the two ports it's actually using, only on networks Windows considers Private (like your home Wi-Fi), and only from other devices on your own network — not the wider internet.

If your Wi-Fi is marked "Public" in Windows, this rule won't apply and devices still won't be able to connect. Go to Windows' network settings and switch that connection to Private.

BeyondATC itself has no password or login of any kind, so this also matters the other way around: don't open these ports up any wider than your own home network, since anything that can reach BeyondATC can also retune your radio.

Different network connections ("Other network adapters")

Most PCs only have one real network connection at a time — your Wi-Fi or Ethernet — and this app automatically finds and promotes that one as "Use this one." You shouldn't need to think about this section at all.

Occasionally a PC has more than one active network connection: Wi-Fi and Ethernet both plugged in, a VPN, or virtual adapters created by other software (a VM, Hyper-V, etc.). In that case, an "Other network adapters" section appears with the extra addresses listed, collapsed by default. This exists purely as a fallback for the rare case where the automatically chosen address turns out to be the wrong one for your setup — if the promoted address works (it almost always does), you'll never need to open it.

• A device can't reach the page at all. Check both devices are on the same Wi-Fi network, that Settings → Firewall shows the rule as present, and that your Wi-Fi is set to Private in Windows (see above). A VPN active on either device can also block a local network like this — try disconnecting it.
• The page loads but says it isn't connected to BeyondATC. Make sure MSFS and BeyondATC are both actually running, and that Settings → BeyondATC is pointed at the right PC.
• "Keep screen awake" is greyed out on my phone. You're on the plain (http://) address rather than the secure one. Use the promoted https:// link and accept the one-time certificate warning.
• The window won't open, or closes immediately. This app needs the Microsoft Edge WebView2 Runtime, which is already present on almost all Windows 10 and 11 PCs (it ships with Edge). If it's genuinely missing, Microsoft's Evergreen WebView2 Runtime installer will fix it — a quick web search for "WebView2 Runtime download" from Microsoft will find it.