How do I install and use FlyByWire SimBridge in MSFS?
Install and run FlyByWire SimBridge in MSFS, connect its remote MCDU on a tablet, and fix aircraft detection, firewall and network faults.
Install SimBridge from the FlyByWire Installer on the same Windows PC as Microsoft Flight Simulator, allow private-network access, and launch it before loading a supported A32NX or A380X. Leave it running; the aircraft connects automatically. Use the address SimBridge displays for browser tools such as the remote MCDU.
What is FlyByWire SimBridge?
SimBridge is a separate Windows companion application that exchanges data between supported FlyByWire aircraft and external features. These can include the remote MCDU and, where required by the aircraft build, terrain, route-file or other external-interface functions.
It is not the aircraft installer, the in-cockpit flyPad or SimBrief, and it is not required merely to load and fly the aircraft. Our flyPad EFB controls and configuration notes cover that separate cockpit interface.
SimBridge runs as an application rather than an add-on inside the Community folder. It supports the FlyByWire A32NX and A380X, not the stock Microsoft Airbus aircraft.
How do I install and set up SimBridge?
- Install the correct aircraft package. Use the FlyByWire Installer and select the package intended for your simulator. For the A32NX, follow our simulator-specific installation checks for MSFS 2020 or package-selection guidance for MSFS 2024. A380X users can check the correct A380X installation and simulator profile. Do not mix 2020 and 2024 packages or Community folders.
- Close MSFS and old SimBridge instances. Before installing or updating, exit the simulator and ensure SimBridge is not still open in the notification area or Task Manager.
- Install SimBridge separately. Select SimBridge in the FlyByWire Installer and use its install or update control. Do not copy its program files into
Community. - Launch SimBridge. Start it from the Installer, Windows Start menu or its shortcut. Leave it running and wait for the local service and browser address to appear.
- Allow private-network access. If Windows Firewall prompts you, permit SimBridge on your trusted private network. Public-network access is unnecessary for an ordinary home setup.
- Load the FlyByWire aircraft. Start Microsoft Flight Simulator, enter a flight with the A32NX or A380X and wait for the cockpit to initialise. No aircraft IP address or account pairing is normally required.
- Test the required feature. Open the address displayed by SimBridge. If testing the MCDU, power the aircraft first; an unpowered cockpit can produce a connected but blank remote display.
Starting SimBridge before loading the aircraft gives the cleanest connection sequence. If you start it later and detection stalls, reload the flight after both applications are running. Keep the aircraft and SimBridge updated through the same Installer, and remove unintended manual or duplicate aircraft packages from Community.
How do I use the SimBridge MCDU on a tablet?
Run SimBridge on the simulator PC, then use a browser on the phone, tablet or second computer. The browser device cannot replace the Windows host.
- On the simulator PC, open the local address presented by SimBridge.
- On another device, use the simulator PC's LAN IPv4 address and the port displayed by SimBridge, including the specified
http://address. - Keep both devices on the same home network. Guest Wi-Fi and wireless client isolation commonly block communication between local devices.
- Do not use
localhoston a tablet: it refers to the tablet itself, not the PC running SimBridge. - If the PC has Ethernet, Wi-Fi or virtual network adapters, choose the IPv4 address belonging to the network shared with the browser device.
- Disconnect a VPN temporarily if SimBridge advertises the wrong adapter. Router port forwarding is neither required nor advisable.
Why is SimBridge not connecting?
First determine whether the failure is between the aircraft and SimBridge or between SimBridge and the browser device. That prevents unnecessary firewall changes when the real fault is an incorrect aircraft package.
| Symptom | Likely cause | Fix |
|---|---|---|
| The aircraft is missing from MSFS | Wrong simulator package, Community folder or a package conflict | Correct the aircraft installation first. SimBridge cannot detect an aircraft that MSFS has not loaded. |
| SimBridge detects no aircraft | The stock Airbus is loaded, the cockpit is still initialising, or the aircraft and SimBridge builds do not match | Load the FlyByWire variant, update both components through the Installer and restart them. |
| The address fails on the simulator PC | SimBridge is not running, another instance remains open or its port is unavailable | Close every SimBridge process, launch one fresh instance and use the new address it displays. |
| It works on the PC but not on a tablet | The wrong IPv4 address, localhost, firewall blocking, guest-network isolation or VPN routing | Use the shared network adapter's address and allow SimBridge on the trusted private network. |
| The remote MCDU is blank | The cockpit is unpowered, the wrong aircraft is loaded or the connection was interrupted | Power the supported aircraft, confirm SimBridge still detects it and refresh the browser. |
| It stopped working after an update | Stale processes, duplicate aircraft packages or mismatched components | Close both applications, update them in the Installer, remove duplicates, then start SimBridge before MSFS. |
Do not disable Windows Firewall completely. Test the address on the simulator PC first; if it works locally but not on another device, the aircraft connection is sound and the fault lies with the LAN address, Wi-Fi isolation, VPN or private-network firewall permission.
Does SimBridge work with MSFS 2024 and consoles?
SimBridge works with supported FlyByWire aircraft on Windows PC installations of MSFS 2020 and MSFS 2024. It is a Windows executable and cannot be installed on Xbox or PlayStation, where FlyByWire's PC aircraft packages are also unavailable. A mobile device can display the browser interface, but the Windows simulator PC must remain the SimBridge host.