August 30, 200421 yr I've been running FS9 now for about 3 months. Added AFCAD 2 and TTools, and do some tinkering with my own AFCAD. Run Windows XP Home. I've not had a problem with it, nor with FS2K2 crashing to desktop.There was a rare occurence in 2K2 when the sim would lock-up and crash, but not like this.Duration of flight doesn't seem to be a factor. Monitor suddenly goes dark. After about 10 seconds, I'm bounced back to desktop.This has happened on last 3 consecutive flights out of SEA with default King Air.I've added nothing to the game to alter it. This happened out of nowhere.My thought is the video card is faltering. Would this make sense to an expert out there?System: P4A Northwood. Intel MOBO. 512mg RAM. Ti200 G-Force 64mg video card whose cooling fan seems a bit noisy lately. Although I may be hallucinating too.Thanks for any advice or thoughts!!I'll start searching AVSIM data base for posts regarding this event in the meantimeRick
August 30, 200421 yr No answer, just thought i'd add that I have yet to complete a flight from PANC to KOAK without getting a CTD around the Vancouver area.
August 30, 200421 yr Rick,Had the same thing happen to me about 8 months ago. Turned out the fan, which WAS intermittently noisy, was failing. Finally quit all together, and the card was fried bfore I realized it was gone. I was not flying out of SEA. One way to check, next time it happens, pull off the side panel, see if the fan is turning and/or the card is hot--but be careful, you could get a bad burn if you just slap your fingers on it.Hey, with only a 64mb card, good excuse to replace it with one that has 128 or even 256. Worked for me!!! :-)Paul
August 30, 200421 yr These statements:"...Added AFCAD 2 and TTools, and do some tinkering with my own AFCAD"and"I've added nothing to the game to alter it."seem to contradict each other.Several things are possible. CTD's are always a risk when you deviate from the default AFCAD and traffic files--sometimes things go south. You may get a CTD in a place hundreds of miles from where your mods were made. First step if you've changed these files, is to restore the defaults and see if you can repeat yhe crash.Next, there is a widely published "seasonal CTD" issue and fix posted in the forums. You could be victim of that--just search the forums on keyword "seasonal CTD" and you may get an answer. The seasonal CTD is a known issue.To improve your FS9 experience, I also suggest you search for the "Autogen bug". Sooner or later you'll run into that as well.-John
August 30, 200421 yr Thanks for all the posta, folks. Seems there is a sub-forum for these types of questions, so next time I'll go there.When I said I have added nothing to the game, I should've qualified that I meant sub-programs, large land-class mesh files or other large scenery files. Other than AI aircraft, AFCAD and TTools, nothing else. I've never had a problem with those items causing CTD anyway. I should've clarified that. Sorry.So I guess the cooling fan-video card issue is real. It is a GOOD EXCUSE to go buy a newer, larger one!!Thanks everyone.Rick
August 31, 200421 yr Look for a AF2 file that is not in the Addon Sceneryscenery folder. If you have one of the AFCADS that correct the elevation of an airport in the FS9sceneryworldscenery folder, this is your problem. rename the ones in this folder and see if this is the problem. I had the same thing.Joe W.
August 31, 200421 yr Hi Rick!Your problem displays the symptoms of either a bad AFCAD2 file or a bad landclass file. It is most likely one of these two. If I had to guess, you probably installed some landclass file for the area around Vancouver and the sim is not liking it.If this is not the case, check for any AFCAD's you have installed that lay within 100nm of the Vancouver area. Bad AFCAD files have been known for throwing CTD's as far as 100nm from the culprit airport.Good Luck!Sincerely,Dennis D. Mullert Sincerely, Dennis D. Müllert System Specs: MoBo: MSI MAG X870 Tomahawk WiFi ATX AM5. CPU: AMD Ryzen 7 9800X3D. Memory: 128GB Corsair Vengeance DDR5-5600 CL-40. GPU: 24GB Asus TUF Gaming OC GeForce RTX 4090. Monitor: LG UltraGear+ 45" curved OLED. Power Supply: Corsair 1500 Watt 80+ Platinum ATX. HD: 2TB Sabrent Rocket NVME SSD. Windows 11 Pro. Flight Sim Hardware: Joystick: Thrustmaster T16000M. Rudder Pedals: Thrustmaster TPR Pendular Pedals. Yoke: Honeycomb Alpha. Throttles: Honeycomb Bravo. Controller: XBox Controller
September 1, 200421 yr I had the same prob recently. The reason was that I had two AFCADs for the same airport. One was installed by a 3rd party installer somwehere else than the AddonScenery/Scenery folder which was the reason I didn't know. There is a small utility in the library that is checking your disk for multiple AFCAD files for the same airport. I am at work now, so I don't know the file name, maybe someone else can help out.Alex
September 1, 200421 yr >I had the same prob recently. The reason was that I had two>AFCADs for the same airport. One was installed by a 3rd party>installer somwehere else than the AddonScenery/Scenery folder>which was the reason I didn't know. There is a small utility>in the library that is checking your disk for multiple AFCAD>files for the same airport. >>I am at work now, so I don't know the file name, maybe someone>else can help out.>>Alex> Yes, But...... That utility doesn't look in the FS9sceneryworldscenery folder.Joe w.
Create an account or sign in to comment