Luca,Just to keep you upto date:I flew From Amsterdam to Zurich and back with the Project Fokker F100 - no problems at all with CTD's.I have had only 2 - these were both being caused by rogue AFCAD files - as soon as I deleted these my FS has been fine.I hope you are getting somewhere with yours!Regards,Alex.

Thanks Alex.Unfortunally, I'm not going anywhere with my CTD's.As a matter of fact I've quit flying, 'cause I'm tired and frustrated.Maybe one of these days I will re-install Fs9 and see what happens.But I'm tremendously skeptical, since I've been hearing from people who still have this problem on clean install of both Fs9 and OS.What I won't be doing is waste time re-formatting everything or running useless memory tests overnight, like a recent ridiculous trend on solving Fs9 problems is suggesting in other posts.Enough of that. FS9 doesn't deserve so much of my time, especially if it's not spent flying.Good luck with your flights.Luca

I have not changed anything with my computer since I loaded FS9 just after release--I could run program reasonably well-no CTD's-Haven't flown for a few months--Started flying again after X-mas-got CTD's right away--Live in an area with snow-downloaded current weather-medium dynamic change-download had snow-would get CTD on taxi to runway-tried changing from night to day time on this default flight out of small airport-would get CTD before sim could reload time of day change-Changed weather to user-defined-no precip-few clouds-wind 8knts.-then tried to change from evening to day-got CTD before sim could reload-changed date to 11/27/03-same problem-changed date to 10/30/03-changed from evening to day-flew for 1 hr. no problem-Everything being equal-FS9 has got a problem with winter Textures or Weather or both--have not tried advancing time of year into Spring to see when this CTD problem goes away-I have three friends that have the same problem-all with good mid to high performance PC's-You can bet that this problem well exceeds 5 per cent of FS9 simmers-This problem is endogenous with FS9-all this driver conflict B.S. is just that-Microsoft remains quiet-They must not have tested this product very well given the huge amount of performance problems listed on this board---Dell Pent 4 2ghzWin XP Home-no networks768 DD ramGEforce 4 Ti 68mb

"You can bet that this problem well exceeds 5 per cent of FS9 simmers-This problem is endogenous with FS9-all this driver conflict B.S. is just that-Microsoft remains quiet-They must not have tested this product very well given the huge amount of performance problems listed on this board"You can bet on that.I would like to remind everyone that it's not us having to suddenly buy new hardware to make the sim run, provided we meet system requirements.It's the sim that has to run flawlessly on any such machines, just like ANY other kind of software we are using.There's a basic law of trade and commerce many people seem to be forgetting.Nobody would undergo half the pain it takes to have the sim run decently, for any other program installed on their PC.And as beutiful and unique as FS9 may be, I'm not giving it any excuses.Unsatisfied customers have their right to speak up.I'm happy for all others.Luca

Hello, ""You can bet that this problem well exceeds 5 per cent of FS9 simmers-'I have been watchings post about this CTD, it is actually less then 5%, many of these CTD where fixed with landclasss files removed, Afcad addons removed, incompatible gauge removed and others video setting fast write disabled.8234 registered users here, let's say 7000 users for Msfs, I have yet to see 50 users about these problems, (Forget all about these first post users)It's the minority my freind Luca, I will conclude a patch will be needed if at least 50% of users have this issue, near 4000 users :)BestEric

You Know,Some of the responses in this thread and others about Crashes are just sad.JUST BECAUSE YOU ARE NOT HAVING A PROBLEM DOES NOT MEAN IT DOES NOT EXIST.Face it,MS could really give a rip about our problems.I don't have AFCAD,I don't have any MESH,I don't have UT, The only add-ons I have installed are the FSD Porter, Commander, and the c177. And I removed all of them as well recently. So no water texture changes, no clouds, runway lights, or other changes.I have reinstalled, and left everything default, and have CTD's.Try F70 French Valley to Palm SPrings. Default everything, and it CTD'sI am actually back to flying FLY!II, since even with all its old problems at least it has a support group that won't bash you when you have a problem.Face the reality. The MSFS9 program is flawed and MS don't give a rip about it.You want to see more people experiencing this.Go to MS website, in their community forums, and on virtually EVERY single page of their Newsgroup, MSN Gaming Zone Sim forums, there are 3-4 posts about MSFS2004 Crashing.Trying to say only a handful have the problem becuase you read Avsims forums is nothing short of a Joke. We are but a small precentage of overall users.Here is the link:http://support.microsoft.com/newsgroups/de...n-us;newsgroups(You need to copy and paste the whole link since it is large)For anyone here to state any percentage is making an assumption that you don't have a clue about. So why make it.Take all your fancy Math, and go to their newsgroups, add up the total number of Simulation Games they manufacture, and then sample the number of MSFS crash posts, and then try your little comparisons. And then go to every single Flightsim web site, and add up every seperate user having all these problems. It will be a lot higher than the number you have here. Or have Avsim start a poll, to see how many of the Users have experienced a Crash To Desktop without adding anything, after their sim was running flawlessly.Just acknowledge that people have these problems, and try to help.I have obserevd more people having this problem than any other major problem in the 4 or so years I have been here.And for the record, I am more than adept at diagnosing system problems, and everything I have tried or read up upon has not worked.The sim doesn't work great for 4 months and then without adding anything all of a sudden go CTD the majority of times I try to fly. Summmer, winter, daytime, no mountains, mountains. Extra, C172, lear45, DC-3, 747....The sim shouldn't CTD after starting a fresh install, after a reformat, a clean registry, and everything else, including going back to an older Geforce GTS pro 64mb card with very old drivers. The Sim shouldn't CTD at all, IMHO. IT's BROKE, and MS don't give a rip. And with no real competition, they won't give a rip.They have a SOLID History of making Code Flawed products ridiculed with problems. I submit MSFS2004, WIndows XP, WInMe, and Win98 as evidence. Atleast they give updates for their Operating Systems, so why people think we are not entitled to fixes is beyond me, unless they: A) Own Stock, or :( have A CONFLICT OF INTEREST.Here are my Current Specs:Athlon 1.2 GHZ512MB RamGainward GeForce 5600 128mbRam Vid Card running 44.71 Drivers.Win XP Pro I WANT MY PATCH...NOW......Regards,Joe(Heads to bunker with tin foil hat and waits for air raid sirens to start)Same comment Cross-posted here:http://pub162.ezboard.com/faboutpoliticsfr...topicID=3.topicNew POLL on Crashes started Here:http://pub162.ezboard.com/faboutpoliticsfr...topicID=4.topichttp://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

"Try F70 French Valley to Palm SPrings. Default everything, and it CTD's"Hi Joe Just did F70 to KPSP - twice - first time with all defaults set in default C172,second time with everything maxed ,in Sea Fury.No problems .Weather etc was set Winter/daytime.Sorry can't repeat your problem.For the record - sreen res is 1280/960. Default GPS runs on second monitor.System is K7S5A/XP2000/Ti4200/512mb DDRAM- nothing overclocked.Fps was around 30 fps (locked)all time except landing KPSP when average was about 20 on both flights.I tried all views cycling thru them several times on both flights.I realise this doesn't solve your problem but IMHO the problem lies elsewhere than the FS9 software.Good luckDave

Sometime a few days ago, these topics were taking an interesting direction, where people experiencing CTD's were sharing their occurencies of such problem in order to try and nail it down.Then people started hopping in, saying things like "I don't see why this is happening to you, since it's not happening to me", with such an attitude as if they were married to microsoft fot the rest of their lifes, considering customer complaint close to unacceptable.I frankly was not aware of such strong devotion in a forum I thought dedicated to problem solving in the first place.So now it's all down to "my thing works and your doesn't" 1st grade kind of thing.I tell you, we are going nowhere, and getting there fast, too.And may I add that, regardless of CTD's, Fs9 needs to be patched just like is happening with 99% of existing software.Bye to all,Luca

I've been following this thread for a while, and I would suggest that a few users that are experiencing CTD problems are inflaming the retoric by "demanding a patch", "implying dubious motives", and generally stating that MS does not care, has not tested properly, or worse..It seems to me that a good number of users have experienced CTD's and that most of them have found through dialogue with other users, that landclass files, AFCAD files, and other add-ons were at the root of their problems. Yet others have found their machine overheating, power supply glitches etc.. As you are well aware, this discussion is still ongoing, and I might suggest that if you were to post the exact circumstances of your crash, others would be willing to test out your flight to see if this problem is reproducible (examples of that right on this forum..)If, however, other users cannot reproduce your CTDs, that does not mean that FS9 has "a major problem", but instead that there is something unique about your circumstances.. I have yet to see "a large number of users" report problems with an unmodified copy of FS9.. so, as the troubleshooting continues, with everyone's thoughtful contribution, solutions or workarounds will surely be found.. Just keep your cool and you may well be able to help countless others by helping to identify a root cause.. and that is exactly what these forums are meant to do! :-)

I have to echo your reasonableness, Bert. The very notion that MS doesn't test FS and doesn't care about problems like this just demonstrates an amble quantity of ignorance about software development in general and the FS team in particular. I was at the last AvSim conference and attended the session they gave on testing the product. In fact the testing is extensive and methodical (anyone who complains about having to reformat shouldn't apply to be an FS tester--they do it every morning!) but like any software product you can't find all the bugs or account for every possible machine config.One thing I found very interesting in their presentation was about testing configs. They choose representative combinations of CPU, video, etc. based on what most of their customers own. Of course, most of their customers buy stock machines from Dell or Gateway and don't build custom rigs with overclocked CPUs, etc. and install lots of add-ons.It would be great if the people who are having these problems would post more detailed information about their configs, display settings, and how to repro the problem. Just saying, "it happens when I fly here" doesn't really help. I'd be happy to try out various scenarios to see if I could repro a CTD and thus shed light on the issue. So far I've not experienced one, even when trying to replicate the limited conditions described in the posts.

Hi Bert.I like your nickel's worth!I do not doubt some users are having crashes of the sim. I have had some of my own, and so far have been able to identify their origins.I do have 2 things to suggest:FLT and WX files are the saved flights files. These are found in the "C:Documents and Settings'your.name'My DocumentsFlight Simulator Files" folder. These can be easily zipped and attached to AVSIM posts. There is no reason not to do this. Then we can try to recreate the problem on our own machines.Reinstalling the sim may be a good idea, but that means you must first use the control panel of Windows ( add or remove programs ), then manually delete or rename the root folder ("C:Program FilesMicrosoft GamesFlight Simulator 9" ). Failure to take those steps will result in leftover addons automatically readded to the sim at it's first run.If those 2 suggestions are followed, I'm pretty confident we can nail down some of the crashes. Unfortunately, the cure for some of these crashes is not pleasant. Sometimes it means you cannot use a favorite addon BGL or aircraft.Sometimes it becomes obviously a hardware problem ( with faulty or overheated RAM modules as a prime suspect... and a faulty or overheated videocard as a close second ). This type of problem is very sneaky, as it is not apparent with most other applications... they must be extremely CPU/math intensive to occur ( just like FS9 ). These types of crashes are usually a freeze of the computer, a reboot, or an abrupt ending of the sim with no error messages.Dick

"FLT and WX files are the saved flights files. These are found in the "C:Documents and Settings'your.name'My DocumentsFlight Simulator Files" folder. These can be easily zipped and attached to AVSIM posts. There is no reason not to do this. Then we can try to recreate the problem on our own machines."An easy method replicating the leadup to the error may be to install Autosave- set the interval at say 300 seconds(5 mins).This will enable the unfortunate pilot to return to a point just before the "error" occured and try flying that particular sequence again - making changes to setting etc each time to see if the error can be eliminated.I don't know - but would it be possible to export a flight/point (via Email or whatever)saved with autosave to other users to try ?I can imagine that ,provided both the sender and the recipient were using default FS scenery and aircraft it may work - perhaps someone can tell us the answer to this.Dave

Hi, i really do not know if this can help but i recall that during FS2002 days i had several CTD around Honolulu.Later, after a small investigation i found that new autogens trees textures were responsiblwe of that crash; so i reverted back to default texture set and got rid of that frustrating problem.My 2 centsLuigi ;-)

Try reading some of the posts at FSGenesis forum=Fs2004--replies to one person having mountain-winter CTD's--several people seem to be having similar problems--some with apparently pure FS9 installs

I am bumping this back to the top, so others who participated in this thread can go read this other thread, where you will find the following.DOCUMENTED CTD's by some of the same people who said it was our sytems and not the program itself.They should also be commended for admitting that this is a problem with the program itself.Here is the thread:http://forums.avsim.net/dcboard.php?az=sho...id=169338&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