On this page, you will find all the necessary resources, links, and documentation you might need to work with and on the A32NX code.
The main GitHub repository for the A32NX aircraft is:
The Development version of the FlyByWire A32NX is done in the master branch. Whenever something is merged into the master branch, an automatic build process builds the newest Development version and uploads it to our CDN, so users can download the latest Development version via the FlyByWire Installer.
The Stable version is a snapshot (in git terms, a Tag) of the development branch.
The experimental version is built in the branch experimental. It is regularly manually updated with the latest commits from the master branch, but its focus is on the development of special larger features like the custom fly-by-wire and autopilot system or the custom flight management system (cFMS).
While the development on the master branch (Development version) follows a very strict development, review and QA process, the development in the experimental branch is less strict and developers can relatively freely commit changes. This is why the Experimental version has a higher risk of bugs and issues and is only meant for testing and not supported on Discord.
The FlyByWire project has other repositories for subprojects like api, msfs-rs, installer, website, docs, etc. Find them here.
Support from the FlyByWire Team on Discord
To get additional information and support, please make sure you join our Discord. There are various channels dedicated to supporting developers (in fact, most channels).
First get yourself the "programmer" role in #roles.
The most general channel for getting help for development is #dev-support.
There are many other channels for specific systems or subprojects. If you are working on the flyPad EFB for example, the #efb channel would be an important channel for collaborating and support.
Our tech stack includes the following:
- Systems development for aircraft uses Rust and the
- Front-end web or desktop app development uses the same technologies outlined above
- Server-side development uses
nest.jsfor the API and
MySQLfor the database backend
Knowledge of all items on this list is obviously not necessary, but this can hopefully give you a better insight into what your skills can fit into.
A number of tools make development in Microsoft Flight Simulator easier.
- WebUI-DevKit - In-game development overlay for html-ui content. Provides fast reload, console output, and more!
- devtools-backend-refurb - Chrome DevTools server targeting Coherent GT. Gives you DevTools for html-ui content. WARNING: This is still a work in progress, and tends to be very finicky.
- P3D XML Gauge Reference - still applies to FS2020.