Has anyone knowledge of AFCAD 2 files causing crashes to desktop (CTD)?It seems that both occurrences of the onset of continuous CTDs came after I had tinkered with another author's AFCAD2 file. When I say "tinkering," I mean adding, subtracting, or re-labeling gates.After FS9 running fine for a few months, CTDs began after AFCAD 2 installs at KSEA, KPDX. AFCAD 2 modified airport KRNO suddenly seemed to cause a CTD when it never used to.After a total uninstall and reinstall, I'm slowly re-installing AI aircraft methodically to find the source of the CTDs. CTDs and ERROR on Loading messages seem to happen after an AFCAD file is installed or modified by me.I don't know. That's all the evidence I've seen so far.Thanks. Looking forward to the "patch." If it doesn't solve my problem, I'll just have to go back to FS2K2, which ran rock-solid on my system with many add-ons.Cheers!Rick (MKE)

Rick,it happened to me as well. I was making/modifying some AFCAD2 files and suddenly, strange CTD's began. I got rid of them by removing all AFCAD2 files and then moving them back until I found the faulty ones. I believe the cause were unspecified runway surfaces, or other empty fields. I can't be sure, but once I went through the offending files, being sure that everything was correct, I never had a CTD again. Having said all that AFCAD2 showed no errors whatsoever in the offending files. Hope this helps you a bit. Check for any empty fields in your AFCAD2 files, fill them in and see what happens.Regards,Jurehttp://www.globecargo.org/images/VAA_Captain.jpg

Also check for duplicate Afcad2 files for the same airports. There is a great little utility in the library called ScanAfd. It will search your fs directory and show any multiple afcad files for the same airport. Any time you get a CTD centered around an airport, try removing the afcad2 and any 3rd party sceneries as well. These things can get caused by lots of different factors, but when they are consistent around a particular area, the scenery is the first place to look.

Craig. Thanks. But so far, I'm not using any 3rd party sceneries other than AFCAD 2 files. I assume you're saying some 3rd party airport scenery files contain a seperate AFCAD file that would interfere with a stand-alone AFCAD file?Rick

Jure!Thanks for the response. I sense there is hope now to solve the CTD problem.What is "an empty field?" What is "an unspecified runway?"I have noticed that default KSLC has taxiways clean of any texture deviation. But when I installed AFCAD 2 files of KSLC, each one from a different author, there were tan texture triangles at some taxiway intersections when it should all be the white concrete textures.Strange indeed!After altering, editing and reshaping others' AFCAD files in FS2K2, it seems AFCAD 2 has some unwanted effects on FS9.Rick (KMKE)

>Craig. Thanks. But so far, I'm not using any 3rd party>sceneries other than AFCAD 2 files. >I assume you're saying some 3rd party airport scenery files>contain a seperate AFCAD file that would interfere with a>stand-alone AFCAD file?>Rick Possibly, but 3rd party scenery can cause crashes as well on their own. I purchased a payware airport not too long ago, and the game would crash at the exact same spot when taking off from the airport. They soon put out a patch which fixed the problem. These crashes can be a major pain to track down, as there can be many causes.

Rick,"empty surface" or "empty field", as I call it (English is not my native language, I am afraid :) ) is when you click, for example, on a taxiway, any taxiway and in the window that opens, you first see:Designator: Taxi ALink Type: TaxiwaySurface : Asphaltand so on...If any of these fields are blank, choose a value for it. In my case, I had the "Surface" field left blank. Same with runway properties. The second block from the top on the left is named "Runway data". Be sure that "Surface" is not blank. As I said, I cannot be 100% sure that this was the culprit, but after going through all the AFCAD's that were causing CTD's (most of them modified originals from a payware package and a few of my own for that same package), I got rid of the CTD's. Again, AFCAD's own fault finder reported NO errors, but FS apparently felt different. :)Jurehttp://www.globecargo.org/images/VAA_Captain.jpg

Check all your addon sceneries for that area. Look for an AF2 file in the scenery. You have a duplicate AF2 file ( 2 files for the same airport at different locations). I would just look in the scenery folders for one. ScanAFD is a good program but it doesn't scan all folders in FS9. If you turn up nothing, do a search for *AF2*.* in the FS9 folder. That should turn it up if the scenery author hasn't renamed the file with out the AF2. In that case.... Just disable the scenerys 1 by 1 untill you find it. Don't forget to thank the author for doing that.Joe W.

That makes sense, Jure. I'll check for that.I noticed when taxiing around KSLC, the surface textures showed concrete, but there were dirt chunks and dust coming off the aircraft wheels, and the aircraft seemed to bobble when in the VC view.And by the way, your terminology is fine despite English being a secondary language for you. I am not as familiar with AFCAD as I should be, and "field" is a common term in computer "programese."Thanks for the help!! This issue just might be the solution to this very vexing problem for me.I'll keep all up to date on my progressRick (KMKE)