I actually uninstall 747 and 787 from my content manager anyway since I don’t fly them at all. I tried setting them as AI traffic, and that was a bad idea, the whole traffic was showing 747 and it was a lag fest since they all render the full cockpit and instruments due to the 747 and the 787 doesn’t have any AI traffic model with them. That’s why I forced the sim to use the Asobo A320 to be the generic traffic, and disable everything else. And the default A320 liveries that it came with are all replaced by the alliance liveries that I have.
I actually use 8K-16K resolutions for all my A320s, including the isAirTraffic stuff. And I set them up so both the A32NX and the Asobo A320 all share the same livery texture files to save space and prevent duplicates and redundancy.
So basically, the 8K-16K liveries that I downloaded will be put into the Asobo A320 with all the model references to the default A320. The isAirTraffic also reference these same livery textures. Then in my A32NX livery, I barely have any livery texture files in there save for the SELCAL plate, and the Coffee Cups (so that the different coffee cups can be applied to different liveries so it’s easy to switch liveries around and the coffee cups will follow). Then I set the texture.cfg file in the A32NX texture folder to point to the livery files located in the Asobo A320 textures folder.
So essentially,
Default Asobo A320 Flyable ----|
Default Asobo A320 AI Traffic—|------> All pulling from the same livery texture files.
FlyByWire A32NX------------------|
You can see how it looks like on my airports:
