Hi,
Has something changed in how an airport Tower and Ground frequencies are specified?
At KASH, a Class D towered airport in Nashua, NH, everything is fine in 2020, both the default and the airport package I created to replace the default properly have a Tower at 133.2 and Ground at 121.8, ATIS at 125.1, and supports ground services and have their approach procedures.
In default 2024, KASH no longer has it’s Tower, though it does have a traffic frequency at 133.2, and it’s missing it’s approach and departure procedures, at least as far as the charts are concerned, both LODI and FAA.
When 2020 was released, it suffered a similar problem (no procedures), but it did have its Tower, and the procedures were eventually added about a year later.
So I imported my airport scenery into 2024 (available at flightsim.to KASH), and, while all of the features of the airport are there (the taxiway lights are missing their stalks, though), it doesn’t have the Tower still. In the 2020 airport definition, I did delete the frequencies and added them back in. In fact, since it was originally missing its navdata, I added it in manually. When it was eventually fixed, I removed my navdata from the package. (Hmm, I’ll have to check if I uploaded that version to flightsim.to, I think I did, but it is what I’m using to test)
So, my question is, what’s stopping the Tower and Ground from showing up in 2024 with my 2020 compiled airport added?
I haven’t recompiled the airport yet with the 2024 SDK. Any idea if it will work then, or is there some overarching 2024 ATC thing that’s blocking these smaller airports from having their correct data?
I did see another similar report for another airport, KRDM, over at the forums in the bug reports.
I’ll update the post when I have a chance to recompile the airport with the 2024 SDK.
In the meantime, will the navdata eventually be fixed to include these smaller airports again? Or is this the result of moving to LODI and FS will no longer have the navdata for smaller airports like this?