What is it about?
On April 03, FlyByWire Simulations released a new version of their A32NX mod. With this new version, the A32NX aircraft becomes a "stand-alone" independent aircraft. With this, all released A320neo Liveries will not work anymore with the A32NX mod. However, they will work again after a quick conversion. The A32NX update has currently only been released for the development branch, but will also be released for the stable build in a few days. So most users will not be able to use the default A320neo Liveries for A32NX anymore as they used to do. The update is coming within a few days, and after this update, there might be even more updates regarding the model and textures of the A32NX, requiring creators to update their liveries for compatibility.
What does that exactly mean?
This means: Liveries that are compatible for the default A320neo by Microsoft will no longer be compatible for A32NX. Liveries compatible for A32NX will no longer be compatible for the default A320neo. Creators can create versions of their liveries for both aircraft, but these must be separately uploaded. There are still a lot of people who do not use the A32NX mod, so they will keep using the default A320neo Liveries.
What do I have to do?
If Creators want their liveries to be compatible with the new versions of the A32NX mod, they need to convert and update them. Fortunately, no texture changes are necessary (yet), just some adjustments in the JSON files and folder structures. To do that, follow this tutorial by changing a few entries.
What is next?
Flightsim.to has created a FBW A32NX category. We ask all creators to upload their A32NX compatible files to this category. If you are in the process of converting your liveries, please do not change or delete your already existing and uploaded liveries. Leave them untouched, but upload another, compatible version to the right category. If you are in the process of creating new liveries and if you have created a version of your livery that works for both the default A320neo and the A32NX, please upload these versions separately - twice, once in each category! Do not upload them both in one category. Separate them cleanly.
- Category A320neo: Please use this category only for liveries compatible with the A320neo by Asobo / Microsoft. In this category, you will only find default A320neo liveries.
- Category FBW A32NX: Please use this category only for liveries compatible with the A32NX by FlyByWire. In this category, you will only find A32NX liveries.
Why have we done it this way?
We decided to choose this way because, according to FlyByWire communications, there will most likely be more changes to the A32NX model in the future. It is possible that the textures and the model of the aircraft will change fundamentally, so that it has nothing to do with the A320neo from Asobo anymore. That's why it's important that we keep this strictly separate. A32NX is now an independent, standalone aircraft just like any other.
What if I have compatible versions of my livery for both aircrafts?
Please upload these versions separately - twice, once in each category! Do not upload them both in one category. Separate them cleanly. Upload the version for the A320neo in the A320neo category and then upload your version for the A32NX in the A32NX category. Do not mix them up. Do not upload both versions into one file.
If you decide to update your livery to meet the new A32NX folder structure, please do not delete your already launched default A320neo livery from Flightsim.to. There might be still people who enjoy flying the default A320neo. You can have both versions online - there is no need to delete your A320neo livery after having converted it to A32NX.