FlyByWire Simulations is the name of the group of volunteer developers working on the A320NX addon for MSFS. For those familiar with X-Plane, they are making a more detailed version of the default plane for free, comparable with how ZIBO does it. The A32NX is a open-source project. Anyone can contribute their two cents.
Last month, a new concept of livestreams has been introduced by FlyByWire Simulations. Titled as “In the Hangar”, the core development team, together with the founder of the project, is answering frequently asked questions about the aircraft development and its future. Three days ago, about a month after the first livestream, a second episode of “In the Hangar” has been streamed live on both Twitch and Youtube profiles of FlyByWire Simulations.
If you want to read through our summary of the previous livestream, feel free to do so by clicking here.
Q: Will the aircraft even become a standalone product?
It did not take long to answer the question with making it clear that it is currently planned to make the aircraft a standalone product isolated from the default model provided by Asobo Studios and Microsoft.
However, as of right now, the A320NX shares many textures and code with the default model. Until the shared parts are replaced, it is not possible to release the aircraft as a standalone product due to possible licensing issues.
Q: Will there be TCAS implemented in the aircraft?
Yes. It was even said on the stream that this function is mostly done and when released should be compatible with most network clients that are being used to connect to networks such as VATSIM or IVAO. No further examples were mentioned.
Q: How do you prevent malicious content appearing in the aircraft?
FlyByWire uses Quality Assurance Program for these purpouses. Quality Assurance Program members test every single small modificatoin that should be implemented. If the modification passes that phase, it forwards to other testers, not from the program, who test the features again and provide the necessary feedback.
Q: Any plans on more passenger seat views?
Developers have shared interest in adding more views in the cabin. However, it is not as easy as many could think. Microsoft Flight Simulator uses modelling from either a third or first-person point of view.
In order to add a proper cabin model, a first-person view would be required, however, making that would cause the addon unusable due to the low performance. This could be fixed by making the cabin in a third-person view, however, that would make the cabin visible only when using certain views.
Developers are still looking into this issue.
Q: What is the status of the EFB?
As of the time of the stream, from the modelling side point of view, the model only needs to be recreated to low-poly for better performance and implemented to the aircraft. It was said, that this could theoretically take 1-2 days after the importer/exporter is done if the developer would focus solely on this for the period. After that, programmers will continue from there.
Q: External fuel planner?
It is planned, however, the developers need to focus now on the fuel systems, and then it will be implemented either to the MCDU or EFB.
Q: Are you planning to add details to the spoilers?
As well as with the cabin, it is planned, but the performance hit is the issue. Developers would be very keen on adding more details throughout the aircraft, but that would get you “1 FPS”. Just right now, the developers are focusing on improving the most visible parts of the aircraft that will not affect the performance much.
Q: How close to the real MCDU will be the one in the addon?
The MCDU is very complicated. It is the brain of the aircraft. FlyByWire Simulations is cooperating with numerous real pilots of the aircraft as well as using Honeywell manuals. One feature at a time, there are many fine details. It will take some time until the updated MCDU is in the aircraft, but the progress is coming along. The most-difficult page to implement will be the FPLN page. However, we were reassured, that we can expect extreme realism.
The code for navigation, waypoints, and everything in the default aircraft is coming from FS9 which is an older platform, and therefore it is harder to work with.
It was mentioned, that both an MCDU and an EFB will happen, but the developers just need the time to work on them. Everything in the aircraft is based on computers about which there is not much information available.
An interesting feature that is coming to the aircraft is, that pilots will be able to send messages to other FlyByWire pilots through the MCDU. A preview of that can be found below in a gallery.
Q: Will proper SID/STARs be featured in the aircraft?
This is a base-game issue rather than the addon issue.
Q: Is tray table coming to the cockpit?
It’s not useful, but fun and something that FlyByWire looks forward to implementing. The developers are unclear why would someone need it. A suggestion on the use of it has also been mentioned on the stream by the member of the core development team, that it could be used as a place where to put the printouts.
Generally, FlyByWire is looking forward implementing small details to the addon such as coffee mugs, key chains, etc.
Q: Is shared cockpit coming to the aircraft?
As well as many other features, a shared cockpit system is possible and the developers are more than capable of doing this. While only tweaking is required to make it work, the problem is with the displays matching correctly. It was, however, not made clear, if this feature is coming to the aircraft in the future.
Q: Variations?
A part of the stream has focused on a discussion about different variations of the aircraft. The thing that led the developers to that was the question if BRK FAN will be ever implemented to the aircraft.
BRK FAN, in the real aircraft, is a piece of optional equipment. FlyByWire has speculated, that there could be different aircraft variants, for example, with heads-up displays, or previously mentioned BRK FAN. The aircraft would only need to be reloaded each time the user wants to change the variant.
It is possible, but unclear whether this feature is coming to the aircraft anytime soon.
Q: Are you in contact with Asobo?
Yes, FlyByWire is in contact with Asobo Studios.
Asobo likes the aircraft modification, and it was even mentioned, that their CEO likes every single Tweet from the team. The problem is, that Asobo can’t touch the aircraft without Airbus’ approval as it is their licensed product. A partnership would, however, only offer FlyByWire the ability to put the aircraft to the Marketplace.
Q: Autolanding and HOLD function?
There is one developer currently working on a functioning HOLD function, however, there is a lot of uncertainty about it. It is coming, but the release date is unknown. It’s just a matter of time to properly rework the MCDU.
Autoland function will be possible, and is most likely coming, after the custom autopilot system update. As of right now, the aircraft can autoland based on the default systems, but that does not work very well and is not accurate.
Q: A32NX Optimization?
FlyByWire is now trying to delete as many repetetive code as possible to optimize the aircraft. This should bring a good improvement of the aircraft performance. Less optimization will be on the texturing/modelling side as everything that gets to be added will result in a performance hit.
4K textures are currently implemented only in the cockpit and did not cause a performance hit, surprisingly. DirectX12 might solve this issue, but only time will tell.
Q: What are you looking forward to implementing?
FlyByWire developers have answered, that they are looking forward to implementing the reworked MCDU, new engine sounds, CFDS mode, the EFB, and small details around the aircraft.
Below is a video showcasing the new Leap A1 sounds that can be played. We can even hear the callouts being present in the aircraft.
Cockpit Door Camera 
CFDS Mode
There will be more livestreams like this in the future and we’ll cover them too. You can watch the entire stream again here.
Disclaimer: The media featured in the article were not shared within the stream, but a few hours after it through the FlyByWire social networks.
