Learn how to repaint the Asobo A320neo in MSFS 2020, export DDS textures, build the livery package and fix missing or pink liveries.
To repaint the default Asobo Airbus A320neo in Microsoft Flight Simulator 2020, start with a paint kit or known-good blank livery package made specifically for that aircraft. Edit its exterior albedo textures, export them with the original DDS properties, preserve the package structure, regenerate layout.json, and install the finished package in Community.
Which A320neo package should you repaint?
Use a paint kit or livery template that explicitly names the default Asobo A320neo. The FlyByWire A32NX and iniBuilds A320neo V2 use different models, UV layouts and package references, so their repaints are not interchangeable.
| Aircraft | Will an Asobo repaint fit? | What to use |
|---|---|---|
| Default Asobo A320neo | Yes | Asobo-specific paint kit or blank livery |
| FlyByWire A32NX | No | A32NX-specific livery template |
| iniBuilds A320neo V2 | No | A320neo V2-specific paint kit |
Our compatibility notes for default, FlyByWire and V2 A320neo liveries explain how to identify the three versions. If the aircraft selector says A320neo V2, this is not the correct repaint target.
How do you create the A320neo repaint?
The safest method is to modify a blank Asobo-compatible livery package rather than build every configuration file from scratch.
- Create a separate working copy. Never edit files inside the simulator's
Officialcontent folder. Put the template in a development folder and give its package and aircraft folders unique names. - Open the layered paint kit. Use an image editor that preserves layers, transparency and the source image dimensions. Our full paint-kit and texture workflow covers UV maps, layer order and non-destructive editing.
- Paint the exterior albedo maps. These are commonly identified by
ALBDin their names. Keep panel lines, rivets, shading and ambient detail above or below the colour layers as directed by the kit. Engines, tail, fuselage, wings and winglets may occupy separate maps. - Check the UV seams. Logos crossing the nose, belly, doors or rear fuselage often need adjustment on more than one UV island. Do not assume the left and right sides share identical orientation; text may appear reversed if it is painted by mirroring the whole layer.
- Export without changing the texture specification. Retain the original pixel dimensions, DDS compression, alpha channel and mipmaps. If the template is an SDK source project, let its package build process convert the source images instead of replacing the compiled DDS files manually.
- Register the livery variant. In
aircraft.cfg, give the repaint a unique title and variation name. The texture identifier must match itstexture.[name]folder. Preserve the template's base-aircraft, model and texture fallback references. - Rebuild the package. Regenerate
layout.jsonafter adding, removing or changing files. An old layout can contain incorrect file sizes or paths even when the visible folder structure looks right. - Install and test it. Place the package root directly inside
Community, restart Microsoft Flight Simulator 2020 and select the new variation under the default A320neo.
Which files should an Asobo A320neo livery contain?
A finished Community package needs configuration and package metadata as well as the changed textures. A typical ready-to-install structure contains:
manifest.jsonfor the package identity and version informationlayout.jsonlisting the packaged filesSimObjects/Airplanes/[unique livery name]/aircraft.cfgtexture.[variation]/texture.cfgwith the stock-texture fallback- The modified DDS textures inside that texture folder
- An optional aircraft-selection thumbnail
Depending on how the template inherits the stock aircraft, it may also contain model-alias or base-container data. Keep that mechanism intact. A working default-A320neo repaint package can help illustrate the expected installation structure, but do not redistribute another author's artwork or files unless its licence permits reuse.
For a normal colour scheme, leave COMP and normal-map textures untouched. Changing packed material maps without understanding their channels can produce excessively shiny, dull or metallic surfaces. Preserve alpha channels even when they appear blank in the editor.
Why does the repaint not appear or show pink textures?
A missing livery usually indicates a package or configuration error, while pink or chequered surfaces point to a missing, unreadable or incorrectly referenced texture.
| Symptom | Likely cause | Fix |
|---|---|---|
| Livery absent from the selector | Extra folder level, duplicate aircraft title, wrong base aircraft or stale layout | Check the package root, use a unique title and regenerate layout.json |
| Pink or chequered surfaces | Missing DDS file, broken fallback or unsupported export settings | Restore the template's fallback and re-export using the original DDS properties |
| Aircraft is mostly white | Wrong texture folder name, incorrect texture identifier or repaint made for another A320 model | Match the folder to aircraft.cfg and confirm it targets the Asobo aircraft |
| Black or transparent sections | Alpha channel was removed or altered | Copy the source alpha channel back and export again |
| Logos are reversed or split | Mirrored or discontinuous UV mapping | Paint each UV section separately and inspect both sides in the simulator |
| Old artwork still appears | Duplicate package installed or simulator has not reloaded it | Remove older copies from Community and restart the simulator |
A mistake we see constantly is a ZIP creating Community/MyLivery/MyLivery/manifest.json. The folder containing manifest.json must be the package folder directly under Community. Use our Community-folder installation checks if the repaint works in the development folder but disappears after packaging.
How should you test the finished A320neo repaint?
Inspect the aircraft in daylight from both sides and at several viewing distances before distributing the package. Check the nose, door surrounds, fuselage joins, tail, engines, winglets and underside; these areas expose most UV alignment and mipmap problems.
Remove layered source files and unused exports from the distributable package, then regenerate its layout one final time. Include only the runtime files and modified livery textures needed by the simulator.
Can you repaint the Asobo A320neo on Xbox?
No, not as a loose user-made livery package. Repainting and installing files through the Community folder is a PC workflow; the Xbox version of Microsoft Flight Simulator 2020 does not expose that folder for sideloaded repaints.