As time with FS9 moves on, CTD complaints seem to be becoming more prevalent and they can be a source of major frustration. Some don

Hi Nigel.I located a similar error in an Antilles scenery from the Library. It turned out the GPS crash was due to mislocated start positions in one AFCAD2 file. The really bad thing is that the crashes occured far from the airfield, and there were several AFCAD2 files. It was quite a puzzle.I suspect these types of crashes are more common than is generally talked about. There are hundreds of AFCAD2 airfields in the public domain, and most probably dozens of crash scenarios associated with them.Most simmers have a bad habit of dumping all their BGLs into the ADDON scenery folder, and that makes intelligent isolation of the defective BGL almost impossible.And, of course, Microsoft gets blamed for them. :(In the above example of the Antilles scenery, that error should have never been released, as a thorough beta period would have shown the crash. But, I understand the sense of urgency to release the scenery, and mistakes do happen... and at the time, scenery designers were not aware this type of problem even existed.Dick

Hello DickWith regards to the AFCAD file bgl's, where is the best place to put them? I only have about 4 such files (that I created myself) and they reside in a separate folder within the addon scenery folder. I do get CTD's, but not very often and in any case I had them before I tinkered with AFCAD.Colin

Hi Colin.As long as the separate folder can be easily deactivated via the Scenery Library, you're fine.The detective work gets much harder as more files are dumped into default folders or the generic "fs9addonscenery" folder. I've read we can have 1000 separate project folders in the Library... that should be enough so that we don't have to combine or mix new projects added on to to sim. By keeping them separate, we can usually track down the offending BGL.Beyond rogue AFCAD2 files, CTDs have also been caused by addon textures! FS9 is very unforgiving about the types of textures our sceneries use. DXT1- miped or 8-bit-mipped are safe formats for terrain... I'm not sure about all the variations considered safe for objects.And, of course, landclass BGLS that are twinned to a "texture" folder will cause a memory leak and eventual crash of the computer.I'm sure we can manage to have other addon scenery, modules, aircraft or gauges ( or their textures ) that will crash the sim. FS9 does seem a bit touchy. But note the word "addon".There are seasonal CTDs with the default scenery, and these have been discussed in full in other posts. I don't know of any other crashes caused by the default setup.By keeping our addons organised, we can easily isolate and track down CTDs, with help from the Scenery Library. We should also write down the gauge, aircraft, and module addons, logging when they were added, and where. In fact, keeping a written log of all our FS9 activity wouldn't be a bad idea... whether we are flying or tinkering with the sim.Dick

Dick...I've noticed that if you do a xml at an airport, like add windsocks or a fuelrepair area, if the airport data is included in the xml file, those will cause a CTD by having dual information of the airport.This is what you DON'T want to include unless you are doing a new airport:To include that in the xml document is to court a sure CTD.Joe W.