I suffer from intermittent CTD's and have of course been searching for the cause.I have learned that duplicate AFCAD files are a "bad thing".From the various search programs, I know I have one duplicate. I know why it's there (to add scenery to a lower level AFCAD) and would like it to stay, but not if it's going to cause CTD's.The duplicate AFCAD has no runways, taxiways, parking etc, is at a higher level (40) than the AFCAD which defines these items (38)I can position my aircraft at that airport, taxi around, take-off and depart without problem.However, it does seem to me that my CTD's occur when approaching that location - but at c 150 miles away it can't be certain to be the cause.Is it possible to be able to initilise your position at an airport and depart from it and yet have a duplicate AFCAD cause a CTD when approaching it?

It does not have to be a duplicate AFCAD, it could just be a bad tile. I'd suggest you run your files through FlightSim Manager (freeware) first.Good luck.

There is a free program called ScanAFD which scans for duplicate AFCAD files. Sometimes it is not obvious, it will scan all subfolders etc, and finds them where you least expect.

>Is it possible to be able to initilize your >position at an airport and depart from it >and yet have a duplicate AFCAD cause a >CTD when approaching it? YES! FS9 uses 2 different software codes for departure vs arrival. It is not the duplicate AFCAD that actually causes a CTD but the fact that embedded in the 2 different AFCAD's are duplicate Start Locations (2 or more) for each end of a runway. That is first and foremost but FS9 does not like 2 different runways with the same number or number/letter.A Start Location at the beginning of each runway is used for many parts of the FS9 coding including the end segment of the Approach when on a FP. It is not used for departure except in some cases it can be the beginning of the great circle FP route.>From the various search programs, I know I have >one duplicate. I know why it's there >to add scenery to a lower level AFCAD) >and would like it to stay, but not if it's >going to cause CTD's.This is a common mistake that scenery designers make when adding scenery to a airport. It will not cause a CTD.It is not adding scenery to a lower level AFCAD but a airport header was used prior to adding scenery to the bgl file.The AFCAD program (or any other utility) does not use the file name to determine duplicate AFCAD's. Nested inside the APnnnnnnnn.bgl is what we refer to as the airport header. ExampleThe first xml line is used for the "GO TO" menu list in FS9 but is also used for other areas of the coding.If this info is placed into any type scenery bgl then AFCAD and other duplicate utilities see the header and thinks there are additional AFCAD airports. Be very careful when removing what appears to be duplicate AFCAD's because you might lose airport scenery if the designer placed the header in one of his bgl's.>However, it does seem to me that my CTD's >occur when approaching that location >but at 150 miles away it can't be certain to be the cause.You need to be more precise when determiming the distance from the airport if that is in fact the problem. At 150 miles from a airport you can be sure if the CTD occurs it is not the airport you think it is. The CTD must occur within 85NM/108SM radius from the reference LAT/LON spot of the airport when on the approach. Too many reasons why to explain fully. Also there can be many additional airports within that 108SM radius that can cause a CTD.This post only addresses (2 or more Start Locations) a portion of why you can get a CTD when approaching a airport. There are many many reasons including the aircarft/panel you are flying at that time.Always use a MSN FS9 default user Airplane and a default database airport when trying to find what causes the CTD.hope this helps

What I'd do, is get a copy of Flightsim Manager V 2.8.5 which is free. Run the diagnostics included, and it may find one or many errors in aircraft or scenery, and when you correct them, your CTD may vanish. After copying my FS folder from my old computer to the new, and reinstalling the FS... nothing I did would even get it to load. Since running this program diagnostics, my problem disappeared. Found duplicate sceneries, missing guages, incorrect alias' etc...

Unfortunately have done that without finding anything significant...But thanks anyway

This is excellent advice.The only thing I might add is, sometimes a scenery designer, because of the tools they use, might need to have two different files with Airport headers. For instance, AFCAD does not handle taxiway signs, so the taxiway signs may be placed using a program like SceneGenX, leaving two files with Airport headers. This does not cause CTD's (as long as there are no duplicate runways/start locations, etc. as noted above.). And a program like ScanAFD may tell you to remove one of these files I believe (I don't use it myself).Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)

The best way to find the CTD is unfortunately quite tedious. What I do is turn off 1 scenery at time until the CTD goes away. Problem is, it might also be combinations of scenery causing the problem. When you find the problem scenery, you may want to try disabling files in the scenery directory until the CTD goes away.You can try to use some intelligence as you do this, like concentrating on scenery in the area of the CTD, etc. But you never know, it could be anywhere.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)