OK here goes:
I'm using MSFS Premium Deluxe on Windows 11 Home and the tools I use for AI Traffic creation are ADE2020_Alpha_21 and AIFP34315, I also do a bit of manual aircraft.cfg editing with Notepad.
I use Airport Design Editor (ADE) for AFCAD editing because all of the default MSFS airports, airfields and airstrips have been created with a program or app which made all parking spaces as ramps, with a parking radius of 5m or 7m for GA Small up to 23m for GA Medium. It also created all taxiways as apron links and placed the nodes far too close together on curves, so there are broken taxi links everywhere and AI traffic simply stops or times out and disappears.
I use Don Grovestine's AIFP34315 because it's MSFS compatible and has plenty of built-in checks to warn you of any faults before you try to create a traffic.bgl. The only fault it found with the Typhoon package was that the aircraft have no parking radius defined, but it compiled the .bgl's perfectly well, after I'd made a few Notepad edits to the aircraft.cfg file:
MSFS needs some specific details to be present in the .cfg files for the AI engine to control the traffic correctly, the edits I made are as follows:
Each [fltsim.xx] section needs the two lines below to be added:
isAirTraffic = 1 ; airtraffic flag for variations
isUserSelectable = 0 ; flag off for non selectable planes
I also changed the parking type from MIL_COMBAT for testing purposes:
atc_parking_types=RAMP
The [general] section needs to be in default MSFS format like this:
[General]
atc_type = "$$:Eurofighter" <-- the $$: prefix forces the ATC engine to say Eurofighter
atc_model = "$$:Typhoon" <-- the $$: prefix forces the ATC engine to say Typhoon
Category = "airplane"
performance = ""
editable = 0
wip_indicator = 1
icao_type_designator = "EUFI" <-- all icao info MUST be correct for multiplayer model-matching
icao_manufacturer = "Eurofighter"
icao_model = "Typhoon"
icao_engine_type = "Jet"
icao_engine_count = 2
icao_WTC = "M"
icao_generic = 0 <-- icao generic value MUST be 0 for all AI traffic
I get the ICAO info from their website:
https://www.icao.int/publications/DOC86 ... earch.aspx
That's sufficient to get the models to show up in MSFS at least, but they would fly much better if the .cfg files were separated out in default MSFS format:
ai.cfg <-- contains important autopilot control PID's etc
aircraft.cfg
engines.cfg
flight_model.cfg
systems.cfg
target_performance.cfg <-- contains important reference climb, cruise, descent and approach speeds etc. for the AI engine
The only other thing is the MSFS folder and file format, along with the required layout.json and manifest.json files - without these nothing will show up in MSFS.
I use the freeware layout generator which is drag and drop, very quick and easy to use.
The typhoon package I created is in a main folder titled MAIW Typhoon.
The traffic bgl's are in folders named scenery/world/traffic.
The aircraft folders and files are in folders named SimObjects/Airplanes/Typhoon.
Sorry if you already knew all this, I'll be more than happy to give you any other info and help that I can.