3rd party airports compatibility list - BATC

Discussion Hub Airports
, , , ,
1

My intention is to create a 3rd party airport integrity and compatibility list, mainly with BATC and/or other functions such as traffic injection. It is also a source of info to airport developers to check if their airport actually works and interacts in the sim as it should and of course anybody that is considering to purchase an airport add-on.

I fly exclusively to 3rd party airports and have purchased hundreds of them through the internal MSFS Marketplace.

I have used BATC in the Experimental/Supporter version since it was released and have come to the realisation, that many issues I experience are due to bad or incomplete airport data - airports that are look great visually may have bad layout design on the backend be lacking necessary runway -, taxiway, runway exit -, hold short bar - , wrong or no frequency information and missing or wrong approach facility data - which result in dysfunctional behaviour such as frequency incongruence, bad vectoring data or AI traffic behaving strangely. Some airports work well and others do not work at all as it seems.

Unfortunately I have not kept a record over this long time, of which really a lot of my purchased airports had some kind issues, because I blamed BATC - some of it was but as it relies heavily on the data it reads from the sim itself, it also depends on how well an airport layout has been designed and completed by its developer.

As airports are relatively high price investments, I think devs should pay as much attention to the non-visual aspects that are not apparent as to their visible appeal. I think it is also a standard, we as paying customers can expect from pay-ware developers.

I will post airports in this thread, where I have run into such issues as I go from now on and I invite and welcome you to do the same in this thread. As airports are updated and corrected - this should also be mentioned.

Of course old or broken scenery indexes can also always cause issues too - a thing to always keep in mind and something Asobo should clean in the background imho.

Format should be:

Airport ICAO, Name, Developer Name, airport native or 2020 compatibility flag, then a small report of experienced issues or flag it as OK, if no issues were found.

1 Like
2

I will be adding airport and BATC findings as I go:

EDDW 1.2. - FSDG - N(ative) - wrong frequencies.

EDAZ 1.2. - Aviation-Sim-Design - N - taxiways not defined - BATC: currently not compatible

EDDG 1.0.5. - M’M Simulations - FS2020 - AI traffic approaching from wrong direction and then dropping on the runway. BATC: No handover to tower.

FYWB 1.2.0 - FSDG - FS2020 - no taxiways defined, BATC: Airspace delegation handovers by incorrect.

FYWH 1.0.2. FSDG - FS2020 - taxiway incongruence - AI traffic and taxi issues. BATC: Airspace delegations, handovers incorrect.

KTEB 2.0.3. - Dreamflight - N - AI traffic disappears after landing, taxi on own discretion

VABB 0.1.0 - MSK Productions - AI traffic issues.

VIDP 1.0.0.- Feelthere - FS2020 - AI traffic disappears after landing

3

For MSFS 2024 users, I’ve created a Discord server with over one hundred revised default airports (and counting) that are designed to work with all the 3rd party ATC apps. They are freeware. Taxiway lettering and the taxi network geometry are up to date when compared to real world airports. Runways, parking spaces and ground markings are also correct. For the ATC apps that need airline codes for parking, they are also up to date. If a terminal building is missing, it was added using generic MS scenery objects. These updates utilize exiting MS default buildings and are devoid of eye candy so they are lighter weight than other versions. Here’s the link:

1 Like
4

Any activity in the air is down to either BATC or the default sim engine. By BATC’s own admission, many of the flaws we thought were attributable to the airport devs turned out to be BATC issues. I believe BATC are going through airports to correct procedures, etc. but it’s a very long and time-consuming process.

It’s currently very difficult to determine whether the airport is at fault, or BATC. The fact that it could in some cases be both further compaounds the problem.