Set up FlyByWire SimBridge in MSFS, connect the A32NX or A380X, and fix firewall, network, blank-screen and version problems.
Install SimBridge from the FlyByWire Installer, launch it on the same Windows PC as Microsoft Flight Simulator, permit it through Windows Firewall, then load a supported FlyByWire aircraft. SimBridge should detect the aircraft automatically; use its displayed local-network address to open services such as the remote MCDU on another device.
Set up SimBridge step by step
The reliable method is to install both the aircraft and SimBridge through the FlyByWire Installer, then run SimBridge alongside the simulator.
- Confirm the FlyByWire aircraft is installed. SimBridge works with supported FlyByWire aircraft such as the A32NX and A380X, not the stock Microsoft Airbus. If necessary, follow our A32NX installation procedure for MSFS 2020 or the corresponding aircraft-package steps for MSFS 2024.
- Close old SimBridge instances. For a first installation or update, close Microsoft Flight Simulator and check that SimBridge is not still running in the notification area or Task Manager.
- Install SimBridge separately. Open the FlyByWire Installer, select SimBridge and use its install or update control. SimBridge is a Windows companion application; do not extract or copy it into the
Communityfolder. - Launch SimBridge. Start it from the installer, its shortcut or the Windows Start menu and leave it running. The application should report that its local service is ready and display the address used by browser-based interfaces.
- Allow private-network access. When Windows Firewall asks, permit SimBridge on your trusted private network. Public-network access is unnecessary for a normal home setup.
- Start MSFS and load the correct aircraft. Enter a flight with the FlyByWire variant and wait until the cockpit has finished loading. No aircraft IP address normally needs to be entered for a same-PC installation.
- Test the connection. Open the local address shown by SimBridge. If testing an MCDU display, supply electrical power to the aircraft first; a powered-off cockpit can produce a correctly connected but blank remote screen.
Keep the aircraft and SimBridge updated through the same installer. A mistake we see constantly is retaining an old manual aircraft package alongside the installer-managed copy, leaving duplicate packages in Community.
What does SimBridge do, and is it required?
SimBridge is an external service used by FlyByWire features that need to communicate beyond the virtual cockpit, including browser-based remote interfaces. Ordinary cockpit flying does not require it, and it is not the same thing as SimBrief.
It is also separate from the tablet mounted in the cockpit. Our flyPad EFB controls and configuration notes cover that interface and its normal aircraft workflow.
How do I connect a tablet or phone to SimBridge?
The tablet or phone must be on the same local network as the Windows PC running SimBridge. Use the PC's local IPv4 address and the port displayed by SimBridge; use the exact http:// address it provides rather than an internet search.
localhost works only on the sim PC. On a tablet, localhost means the tablet itself, which is why copying the PC's localhost address to another device fails. Our remote MCDU network setup explains the correct local and cross-device addresses in detail.
- Keep both devices on the same home LAN; guest Wi-Fi often blocks communication between devices.
- Temporarily disconnect a VPN if it causes SimBridge to advertise the wrong network adapter.
- Do not configure router port forwarding. SimBridge should remain available only on your local network.
- If the PC has Ethernet, Wi-Fi and virtual adapters, use the IPv4 address belonging to the network shared with the tablet.
Why is SimBridge not connecting to the aircraft?
First establish where the connection stops: aircraft to SimBridge, or browser device to SimBridge. That distinction avoids changing firewall settings when the actual problem is the wrong aircraft package.
| Symptom | Likely cause | Fix |
|---|---|---|
| SimBridge runs but detects no aircraft | The stock Airbus is loaded, the flight is still loading or the aircraft package is outdated | Load the FlyByWire variant, wait for the cockpit to initialise, then update both products through the installer |
| The address fails on the sim PC | SimBridge is not running, another copy is still open or its listening port is unavailable | Close every SimBridge process, relaunch one copy and use the newly displayed address |
| It works on the PC but not on a tablet | Firewall blocking, guest-network isolation, VPN routing or the wrong IPv4 address | Allow SimBridge on the trusted private network and use the address of the adapter shared by both devices |
| The remote page opens but remains blank | The aircraft is unpowered or has lost its SimBridge connection | Power the aircraft, confirm SimBridge still sees it and refresh the browser page |
| It stopped working after an update | Stale SimBridge files, an outdated aircraft build or duplicate add-on packages | Update both components, remove duplicate FlyByWire installations and restart SimBridge and MSFS |
Do not solve a firewall problem by disabling Windows Firewall completely. On a trusted home network, make the Windows network profile and SimBridge's private-network permission agree, then restart the application.
Does SimBridge work with MSFS 2024 and consoles?
SimBridge can be used with supported FlyByWire aircraft on Windows PC installations of MSFS 2020 or MSFS 2024. It is a Windows executable and cannot be installed inside the Xbox or PlayStation versions of Microsoft Flight Simulator.
A phone, tablet or second computer can act as the browser client, but the Windows PC running MSFS remains the SimBridge host. Running the browser elsewhere does not remove that PC requirement.