I thought my CTD was seasonal until tonight. I was trying to do a flight from Prague (PRG) to Paris (CDG) using the 737-500, current date, real world weather, and Prague scenery. Shortly after take off from runway 24 (maybe 5 minutes into the flight) FS2004 crashes. Then I tried the same flight with the default 737, no weather, in summer, and no scenery. After take off from runway 24 FS2004 crashes again same spot as the other time.When you send in the report after a crash does that happen with it? Does MS actually read those reports we send in?

Just to letyou know......I used the default high altitude aiways route for both flights and AI at 100%

Sorry you feel that way, Jon. I didn't intend to get in the middle of a feud; just trying to enjoy the hobby and learn a little something too.

Hi Bill,Nothing against you, mate. You are the one who helped me to decide to buy an ATi card. You can PM me if you wish before my account is closed. No point discussing anything further on these forums, because according to Joe, my lack of CtDs is in my imagination. Therefore it's pointless me trying to assist people to overcome them, because I must have the same problem myself.

Jon,If you read my post, I NEVER called you a liar. I used just about the same words you used to sum up the rest of us.So if you feel like I called you a liar. I did not. The point I was making is that when you sit there and say your system runs great, we are all happy about that, but then you say:Jon:"I'm not saying you are all full of it, just that I'm not (yet) convinced there is an issue with Microsoft's code."Well, that may have made others feel offensive by you not stating we are full of it. But I guess you can't understand that so I will apologize to you for using your words to describe to you in the same manner that you used to describe us. I'm sorry if it made you upset.Regards,JoeJon Then wrote:"because according to Joe, my lack of CtDs is in my imagination."Nope, Jon, I never said that either.Please try sticking to the actual things I say instead of the ones that I do not. I never stated the above, and If I did. PROVE IT. I know exactly what I wrote. I suggest you take my words as they are actually written. Good Luck to you.http://aboutpolitics.net/images/bannerav.gif.About Politics.net - FORUMShttp://pub162.ezboard.com/baboutpolitics.Contribute to the Richard Harvey Scholarship Fund.http://www.avsim.com/pages/scholarship.shtml

Nope, I never called you a liar.Didn't happen. Sorry.Regards,Joe

Hello All,Well, for the life of me, if I disable fastwrite and keep the sound acceleration at basic, I don't experience any crashes any longer. Hopefully this will help some of you.Did the KORD to KDAY this evening on VATSIM, and didn't have one bit of problems with all acc programs running. So, I guess I'll count my blessings and keep flying until it starts again.Speaking of which . . . boy, VATSIM WAS WILD TONIGHT. Weather coming out of KORD was absolutely terrible, I was showing unbelievable thunderstorms, but ATC had KORD ready to shut down with heavy blowing snow and 0 visability. At FL260 everything was cool, but upon descent, KDAY weather was just about the same, was registering x winds from 12 to 40 kts. Had to do 2 GA's and finally clicked off the AP and just hand flew it in . . . I can tell you this, has this not been FS, I would have found an alternate . . .cause this was one of the most hairy landings I've had in FS or in real life. Anyways, I will keep monitoring this thread . . .and relay more if I have another CTD.Best to all and bundle up Chicago! Clay

Hello All Again I just wanted to add something seeing that Jon made the statement about we all needed to start building stable computers.Hmmmm! Well, it seems my puter as mentioned in the beginning of this thread is stable with every program I run with the exception of FS9.I will repeat that. EVERY PROGRAM I HAVE ON THIS COMPUTER I HAVE NO PROBLEM WITH EXCEPT FS9 NOT RAINBOW 6, NOT CFS3, NOT SPORTSCAR GT, NOT QUAKE NOT LOMAC . . .OR ANY REGULAR PROGRAMS.And, FS9 is the ONLY FS I have ever had any CTD's with . . . and I've been doing this stuff since FS4. Now I'm not a computer expert, by any means, but there ARE some who freqent this forum and I take their advice when I build a new unit . . . and in todays day and time, if you can read, and follow directions, and don't have hams for hands and can follow good advice and dial tech support . . . you can have a stable computer.Sorry, just wanted to take up for some of us who KNOW that there is a problem with FS9 . . (and I still love it, but would like to solve the buggar!)Best to all . . . Now I feel better.Clayton T. Dopke (Clay)Major, USAF (retired)"Drac" (there, I got official..LOL)

"You all just need to learn how to build and run stable computers."It's often difficult to write and express emotions, so I'll make this point right up front, Jon. While I find this remark comical at best, I'm in no way offended by it. I use the same MB as you, I know how to build and maintain a gaming system, and I'm fairly competent in setting up an FS install to run with the horses. The fact of the matter is that alot of people are having problems on many different configs. All we can do is try to lick the problem. You may not believe there is a problem, but there is.I hope you don't leave, Jon. Your expereince can be useful to us in trying to find a solution. But only if you accept that some of us are indeed having a problem. I'm convinced after my weekend of real time testing on 4 different gaming machines (all of them suffering the same CTD's) that this is not a hardware issue for all of us.Cheers mate,

:-beerchug to ya, Clay! :-)

Hi everybodyI've been doing some testing here for the last couple of weeks (CTDs), or should I say months (FS9)? Needless to mention, I'm jealous of those who have no complaints. Bill, will you sell me your computer, pleeeeeeaaase? (grin) I hadn't touched FS9 for a while. Till then, I was trying to run it on my cool (in terms of not hot, 4 fans) 2.5Ghz AMD/nForce2 rev.2/GF4600/512MB/Audigy2/Win2000sp4 FlyTendo, with little joy. Was back with FS2002. After extensive reads here however, just before Christmas, I decided to Install FS9 again, but this time on Win98se. This to try 2 things: The CTD phenomena on a bare FS9 install and to see how the sim handles with win98. Which I hadn't tried yet. So the setup is: Bare OS-install with absolutely no tweaks, apart from the MaxFile-line in the system.ini. FS9 bare install too, default.xml renamed, TerrainVectObjcts=0, fair weather theme. The method: I'ld start a saved flight in AMS and load a EHAM to LIRF plan. This plan includes an amazing zigzag over the Alpes. I also have a few saved situations along that route and in the Alpes. I would fly the respective date, first trying to make it beyond the Alpes. Then, changing the time at points (mainly afternoon and evening) and changing views etc. Every day for aproximately 2-3 hours. Also, I sometimes selected Zurich Airport i.e. mid flight. Or turned off the AP and flew manually. The most 'beflown' areas were located in the Alpes, specially the 'Geneva - Zurich - Northern Italy Triangle' as proposed. As I reckoned enough others were trying Innsbruck etc. This is what I could report back:CTD and black screens in the Alpes during the winter season on a bare FS9 install, is affirmative. Since I wasn't interested in finding a particular spot, I didn't try to reproduce these abnormalities spotwize. I was more interested to perhaps discover a broader pattern. Which I couldn't. Crashes would occur during day or dusk, not night. Didn't check dawn. My focus on trying to stress the sim a little. And repeating the same pattern of strain everyday (more or less, to not make it too boring). However, I also couldn't detect a regularity. Sometimes FS9 crashes, sometimes it doesn't. Some days the sim crashed, some it didn't. The area around Zurich and Torino are the most 'fragile' areas. Either at airport or in 40-mile vicinity, various CTDs and some BSDs. Another funny thing I observed, was awkward looking square-shaped texture blending taking place in some areas, mainly in the Alpes too. The areas looked like receiving the icing of a cake. Ground textzures still bleeding through. Weird. Beyond the snowy textures we're used to. Conclusion: Crashes OCCUR on bare FS9 install... Reproducable? Easy. Just sit back and wait... Thanks for your efforts everybody. Jaap

I apologise for that remark about building stable computers. It was said in the heat of an extremely angry moment indeed. I couldn't close my account here without apologising for that remark. That said, I am certain at least some CtDs are caused by unstable computers.Now that I am relaxed again, I should state my true position is that I am not yet convinced there is an issue with the FS9 base code and that my current belief is it is a hardware or configuration issue, possibly relating to memory , cpu and bandwidth latencies. As I stated before, the only way I have been able to reproduce CtDs in FS2004 is by making adjustments to my hardware settings that from experience tell me are likely to cause instability.As for other games / sims working fine. Well, FS9 isn't those other games, and FS9 could simply be such a "hardware agressive" sim (that can't be denied by anyone) that it topples an otherwise stable setup into submission. I have seen plently of machines breeze through the most agressive benchmarks ever devised only to fall over in flight sim.Anyway, I wish you all luck in the future in trying to sort of this and (no doubt) other flight simming related issues that will crop up :-wave

I believe it's already been confirmed that FS crashes even with a bare install. Chris Willis posted a simple set of repro steps and I followed with a workaround. Have you tried the terrain.cfg edits I suggested in another thread?

Here's another FLT file for LFNC. The zipped attachment has 2 FLT files and their associated WX files. They should be self explanitory. The date is the difference ( the CTD being November 25, 2003 ).The good FLT is summer... no CTD because there is no seasonal fall snow across the VTP2 airport background polys ( in higher elevations ).Joachim's terrain.cfg fix eliminates the CTD.Other CTDs may be found in far northen locations ( Norway, for example ) during dates that would have the seasonal change from fall to winter. There may also be problems with early springtime, when the snow gives way to spring textures.Dick

After being FALSELY accused of calling another member a Liar. I am posting this so that my Integrity remains in tact.*********************Jon said yesterday:"Well Joe, I've tried to be diplomatic about it, but posts like yours, accusing me of being a liar really get my goat.So no more beating around the bush trying to help people. The problem is not Microsoft, it's yours. You all just need to learn how to build and run stable computers. End of story."*********************Well, Jon has seen the light apparently and has returned to the forums, and guess what. He has also had CTD's. It seems, according to another member that Jon had placed a MSFS2002 file in his installation, meaning that he was not running a true fresh install of MSFS2004. This provides more evidence that this is the fault of Microsoft, and not the fact that I or anyone else needs to learn how to build and run a stable system.You can read about it here, and I will leave it at that FOR NOW.http://forums.avsim.net/dcboard.php?az=sho...id=170476&page=Regards,Joehttp://aboutpolitics.net/images/bannerav.gif.About Politics.net - FORUMShttp://pub162.ezboard.com/baboutpolitics.Contribute to the Richard Harvey Scholarship Fund.http://www.avsim.com/pages/scholarship.shtml