Hi,I've run into a strange problem that I haven't been able to figure out and have run out of ideas of how to proceed. I'm hoping someone here can provide a few pointers as to where to look next.The problem is that several of my default airports have disappeared. They appear in the airport selection list correctly and can be selected. However, when they are selected, the location is always set to what looks to be a default value of 89*30N 0*00E +100000. There seems to be a pattern to the airports that are missing: all of the airports I have tried in Germany and the UK are missing along with a number of others in Vietnam, Thailand and parts of Africa. No airports appear to be missing from the US, Canada, France, Spain, South America, the Philippines, Japan and so on. When I go to a set of coordinates where I know the airport is supposed to be, all of the scenery is there and appears to be correct, and all of the traffic I expect to at the airport is there. So the scenery and traffic doesn't appear to be affected.Here's what I have done so far to try to resolve the problem, without success:- searched for and temporarily removed all of the AFCADs that I can find. - disabled all add-on scenery. - confirmed that the airport coordinates are correct in the airports.txt file using TTools. They are.- removed all traffic BGLs (in case one contained a corrupt airport list).Does anyone have any further suggestions? The root cause of the problem seems to be that FS9 is not able to correctly map the airport ICAO code to a correct set of coordinates. All of the other data (scenery, traffic etc) seems to be fine. What files control how FS9 looks up a set of coordinates from an ICAO code?Thanks for any help.

Update: managed to resolve the problem. There was another scenery package called ZZZ_Corrected_AFCAD_Elevations buried at the bottom of the scenery library. This package was part of the excellent US Columbia River Gorge scenery add-on. Since the corrections contained in that BGL should have been limited to the Columbia River gorge area, I'm not sure how the could cause problems with airports on the other side of the world but, through a process of elimination, that does seem to be the case. It must be a convoluted interaction with some of the other add-ons I have installed.

Ohh you are lucky you fixed your problem!For me all the airports in Portugal & Spain have vanished :( I've tried everything and it wont work so now I just dont fly to/from those two countries.

>Update: managed to resolve the problem. There was another>scenery package called ZZZ_Corrected_AFCAD_Elevations buried>at the bottom of the scenery library. This package was part>of the excellent US Columbia River Gorge scenery add-on. >Since the corrections contained in that BGL should have been>limited to the Columbia River gorge area, I'm not sure how the>could cause problems with airports on the other side of the>world but, through a process of elimination, that does seem to>be the case. It must be a convoluted interaction with some of>the other add-ons I have installed.>It is not uncommon for some mesh/terrain/Afcad add-on files, especially those designed to correct a local error, to affect conditions in another part of the FS world great distances away. It depends upon how the original 'correction' was made sometimes, and has been demonstrated more than a few times.

Hi there,sorry about the issue with the ZZZ_Corrected_AFCAD_Elevations folder. It first came up soon after I published Columbia River Gorge and a work-around was provided in the following thread (the update to CRG, crg_upd1.zip, mentions that thread too): http://forums.avsim.net/dcboard.php?az=sho...topic_id=240404While it is true that sometimes files get uploaded that have a larger geographic extent than planned (as in "small airport flatten file levels the southern hemisphere") this wasn't the case here. I never tested the exact reason for this problem because there's an alternative available that we now know works more reliably but it has to do with the way FS updates its scenery library entries. When placing that extra folder near the bottom of the scenery library, on some user's systems FS doesn't update the index files of the regional (airport) data files as it should; that seems to cause the loss of the Goto Airport menu function. Anyway, I guess the lesson is that innovative solutions to tricky problems don't always have a 100% success rate x( My apologies for the inconvenience.Cheers, Holger

Do you have a scenery for LDDU on your computer?The original download includes a mistake in the exclude file which will make all taxiways and runways for airports from Dubrovnik to Morocco disappear.

Thanks for the info, Holger. No need to apologize, the amount of enjoyment I get from your enhancements more than makes up for the occasional quirk.