In the AirportsScanLog.txt I found this entry:

==> Not recognised airport C:\Users\robai\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\Community\inibuilds-airport-fact-cape-town-intl\Scenery\airport-inibuilds-fact-cape-town\inibuilds-scene\fact-scene-airport.bgl
C:\Users\robai\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\Community\inibuilds-airport-fact-cape-town-intl\manifest.json found
Non complying airport has ICAO 'FACT' in title 'FACT Cape Town International' of manifest

Try to find publisher in: C:\Users\robai\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\Community\inibuilds-airport-fact-cape-town-intl\Scenery\airport-inibuilds-fact-cape-town\inibuilds-scene\fact-scene-airport.bgl
publisher 'INIBUILDS' found
thirdparty INIBUILDS FACT does not exist

Edited October 9, 2025Oct 9 by kiek

4 hours ago, SayAgain said:

==> Not recognised airport C:\Users\robai\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\Community\inibuilds-airport-fact-cape-town-intl\Scenery\airport-inibuilds-fact-cape-town\inibuilds-scene\fact-scene-airport.bgl

That tells us that the .bgl file is not compliant with the MSFS 2024 coding standards. => PSXT is not able to generate an airport file.  There is also no MSFS 2020 version (yet) to link it to.

Is it really a 2024 version? Where did you buy it?

There is nothing I can do.

 

Edited October 9, 2025Oct 9 by kiek

4 hours ago, kiek said:

Is it really a 2024 version? Where did you buy it?

Just recent release on iniBuilds store here:

https://inibuilds.com/products/inibuilds-cape-town-fact-msfs-24?srsltid=AfmBOopELJiiwrRJ3EpMrGEiR9ZuvnnqAcv8_gb24QxO8k5oGLkWKGOM

As you can see, the claim is native MSFS 2024 (not even listed for 2020) from the ground up.

20 minutes ago, SayAgain said:

As you can see, the claim is native MSFS 2024 from the ground up.

Yes but they do not code the beginning of an airport record with 0056x so I'm lost.

Hope I can find more info about changes in the .bgl format in MSFS2024.

Edited October 9, 2025Oct 9 by kiek

5 minutes ago, kiek said:

Yes but they do not code the beginning of an airport record with 0056x so I'm lost.

I will point iniBuilds support to this thread for comment.

FYI, this is not the only entry in the AirportScanLog.txt file … I have many MSFS 2024 airports listed as “Not recognized”.

16 minutes ago, SayAgain said:

FYI, this is not the only entry in the AirportScanLog.txt file … I have many MSFS 2024 airports listed as “Not recognized”.

I know...

fixed in 12.4.0

Oh wow, thank you!  A nice treat.

Nico,

Hate to ask, but can you make the "scan for airports being disabled unless connected to sim" only apply to 2024? PSXT should NOT have to be connected to 2020 for airport scan. In the past every time PSXT was updated I would use AddonsLinker to enable all my addon airports and then run a quick scan with PSXT so when I next used MSFS2020 an airport scan wasn't necessary and PSXT would be ready to go instantly when it connect to the sim. I always scanned airports that way because before I start MSFS2020 to fly I disable all scenery that I won't be using during that session - 2020 starts significantly faster without all that superfluous scenery active.

16 hours ago, somiller said:

Hate to ask, but can you make the "scan for airports being disabled unless connected to sim" only apply to 2024? 

No, sorry — that’s not possible. Since PSXT uses SimConnect to retrieve data from your airports, a connection to MSFS is required.

This new method has several advantages over the old one.

If you select the airports for your flight using AddonLinker, the airport scan will not take very long, so what’s the issue?
Tip: before you close PSXT, tick the Scan for airports box. Then, when you start PSXT for your next flight, it will begin scanning automatically as soon as MSFS is connected.

Another option is to load all your airports once and let PSXT perform a full scan. After that, you won’t need to scan again unless you install new airports, or when PSXT forces a scan due to a special update (which is rare).

Well Nico that certainly is a unique approach to software function. Before I close PSXT at the end of one session I have to anticipate that I won't use the same airports for the next session and click the airport scan before I close PSXT; OR if I forget, when I run the next session I have to launch the sim, let PSXT connect to it and then check the scan box, then close PSXT and restart; OR I have activate all airports with addonslinker, start the sim and PSXT and let it scan all airports, which will all have to be rescanned when PSXT updates...or not, but I'll have no way of knowing whether an update requires a rescan or not, however in my experience with PSXT, it almost always rescans airports after update.

6 hours ago, kiek said:

Tip: before you close PSXT, tick the Scan for airports box. Then, when you start PSXT for your next flight, it will begin scanning automatically as soon as MSFS is connected.

Which is exactly the way I've been doing it for a looong time.

7 hours ago, kiek said:

Tip: before you close PSXT, tick the Scan for airports box. Then, when you start PSXT for your next flight, it will begin scanning automatically as soon as MSFS is connected.

Good tip.

Somewhat related, what are the odds we could get all the models used by AIG and make them work correctly with MFSF 2024?

The PSXT+LiveTraffic+AIG accuracy is frankly perfect … just the MSFS 2024 changes to LOD that has them all floating around the airport without wheels.  

I haven’t looked at the files for the models, but was thinking there must be a painless way to batch process them so as to fix the LOD issues with MSFS 2024 without requiring original model provider?  Public domain so no real rights issues I’m aware of and full credit would still be provided to original model provider.

Thoughts?

On 12/11/2025 at 1:49 PM, somiller said:

however in my experience with PSXT, it almost always rescans airports after update.

That use to be the case indeed, but since a few months that has changed. By default no airports scan after an update.

 

EDIT:

I could change the semantics of the checkbox into always scan at start up, or add a second check box with that always scan meaning.... What do you guys think?

Edited December 12, 2025Dec 12 by kiek