Choose the right FlyByWire A32NX branch for MSFS: Stable for reliability, Development for newer fixes, with switching and troubleshooting advice.
Use the FlyByWire A32NX Stable version for normal Microsoft Flight Simulator flying; it is the tested, predictable branch and the best default for most simmers. Choose Development only when you need a specific new feature or fix, accept possible regressions, and are prepared to update often or switch back.
How do Stable and Development differ?
Stable is a tested release snapshot, while Development follows the aircraft's ongoing systems work more closely. Development receives changes sooner, but a change that fixes one system can introduce a fault elsewhere.
| Branch | Best for | Main trade-off |
|---|---|---|
| Stable | Routine flights, learning the aircraft, events and users who value consistency | New features and fixes arrive later |
| Development | Testing new functions or obtaining a specific fix not yet in Stable | Greater risk of regressions and changing behaviour |
Stable does not mean bug-free, and Development does not automatically mean better performance. If you cannot name the Development-only feature or fix you need, choose Stable.
When should I install the Development branch?
Install Development when its release information identifies a change that solves your particular problem or adds a function you intend to use. Common reasons include a simulator update affecting the Stable branch or a systems fix that has not yet reached a Stable release.
- Use it if you are comfortable diagnosing conflicts and changing branch again.
- Avoid it immediately before an organised flight, long-haul sector or training session where predictable behaviour matters.
- Expect procedures, displays or saved settings to behave differently after some updates.
- If the Installer offers an Experimental option, use that only when the project instructions specifically direct you to it; it is not the reliability choice.
The simulator package and the aircraft branch are separate choices. Follow our A32NX installation process for MSFS 2020 or the correct package procedure for MSFS 2024, then select Stable or Development. The FlyByWire Installer and Community-folder package are for PC; console editions cannot use that installation method.
Can I switch between Stable and Development?
You can switch branches through the FlyByWire Installer, but treat them as alternative builds of the same aircraft rather than two separate aircraft to combine manually.
- Close Microsoft Flight Simulator completely before changing the installed branch.
- Open the FlyByWire Installer and confirm that it is targeting the correct simulator installation.
- Select the A32NX branch you want and let the Installer manage the existing package.
- Check for duplicate copies left from an older manual installation or a different Community folder.
- Start a fresh flight and verify the aircraft before loading a saved scenario.
Do not copy Development files over Stable or merge their folders. Mixed or duplicated packages can produce missing cockpit screens, inconsistent systems and an aircraft that appears not to have updated.
What should I do if Development causes problems?
Update once through the Installer, test without aircraft-specific modifications, and return to Stable if the fault remains. Old cockpit, sound, cabin or systems modifications are more likely conflict sources than ordinary texture-only liveries.
A branch rollback is also a useful diagnostic step: if the same flight works in Stable but fails in Development, the active Development build or one of its add-on dependencies is the likely cause. If both branches fail, check the simulator package selection, Community-folder duplicates and unrelated add-ons before blaming the branch.