May I ask him to add a feature within "Customize Airport Positions" to allow us customers to manually select an AFCAD if the program chooses incorrectly
There's already an option, explained in the manual, which is the airport_visibility_XXXX = n command ( 0 to exclude ), so you don't have to manually select the right AFCAD but, instead, you exclude the ones that shouldn't be used.
I still (along with everybody else) would like to know WHY at this time time problem crops up?
Maybe it's just the result of the program now correctly picking AFCADs that it might have been missed before. But then you will have to exclude them, if they are using the fictional ICAO method to depict smaller airports inside or very close the main one.