My FS is configured with "Previous Flight" as the default flight, so that it always starts in the situation where I left it before.Everything worked fine, and suddenly FS does not start any more. The progress bar shows "Loading Terrain" and stops at 13%. I thought there was a problem with an add-on scenery I had used last time, so I restarted and selected the "Meigs Field" default flight. FS started, and then I loaded my "Previous flight", and everything went fine.It means my situation saved in "Previous flight" is not buggy, but FS does not want to start with it. I always have to start a default flight, and switch to my "Previous flight" after.Strange, isn't it?I tried many things but nothing worked...Thanks for any clue...Eric

Can't be sure but there could be a problem with the a/c especially if you have a hanger folder like many of us.

What do you call a "hangar folder"? Is it a folder where you put aircrafts you want to keep, but you don't want FS to see them?If yes, I do have such a folder, but I don't see how it can make a problem... I will try to move this folder outside of the FS directory, and I'll see if it changes something.Thanks anyway !!Eric

I, too, have started to have this problem. It began a few weeks ago, after FS was running just fine ever since it was originally installed last year.It doesn't happen everywhere, but right now I cannot load any airport from anywhere in the UK or western France, without starting from somewhere else first. The loading stops at around 11%, when indicating loading terrain.The alert I get sometimes says the terrain.cfg file is at fault, other times it's just 'hungapp'.I have the feeling this stems from one or more of the airports or aircraft that have been downloaded and installed, but unfortunately I don't have the expertise to decipher what it is exactly.Mike F.

Additional clue: when my "Prevous flight" is located in a place where only the default scenery is used, it works fine. But if I try to start FS with an add-on scenery, it fails.I remember now that this problem occured the first time just after I installed a freeware add-on mesh scenery for the French Alps. I will check this scenery and also check the terrain.cfg.Any other idea is welcome !!Eric

It could be an AFCAD file...I had a similar problem when FS9 would crash to desktop when I tried to load FS weather from my home airport! In addition to that, I couldn't load a flight plan, too. It turned out that one of the AFCAD files was bad although the fault finder in AFCAD2 didn't find anything. The airport in question was pretty far away, too.Try to temporarily move all AF2 files from Fs2004/Addon Scenery/Scenery and see if the sim starts properly. Just an idea... :)Regards,Jurehttp://www.globecargo.org/images/VAA_Captain.jpg

I thought the AF2 files were "compiled" into BGL files, is that right?Anyway, I couldn't find any AF2 file into my scenery directories...Thanks for the hint anyway.Eric

Eric,yes, you're right, of course, AFCAD2 files do get compiled into *.bgl files. A slip of the tongue :) . Try and move all of them, at least you'll be sure that it is (or isn't) one of them.I strictly keep all AFCAD bgl's in Addon Scenery/Scenery, even from payware sceneries, simply to avoid confusion. Also, check that you don't have more than one AFCAD bgl for the same airport. Regards,Jure

I finally found out what was wrong. I deleted all the add-on sceneries I had (in the scenery.cfg file) and I added them back, one by one, to detect which was the faulty one. It appears it is Ouessant, one of the Britanny Islands. The Britanny Islands is a great add-on from France VFR, and i am very surprised it makes a problem because I have installed it several weeks ago and never had problems before. I will contact the authors to know more about this.BTW, I noticed there is an "AF2_LFEC.bgl" that certainly comes from the compilation of an AF2 file. I deleted it, and it didn't solve the problem.I'll let you know if I have more news about this problem, hoping this experience can help other people who may have this problem.EricPS. I will be out of connection next week, don't be amazed if you have no reply from me.

Eric, thank you for your hard work. :D I had Ouessant, as well, and removing it solved the problem here, too.(Say Hi to Paris for me, I grew up there (well, Le Vesinet).) :)Mike F.

Several people, in other threads, have reported an inability to save new flights as default. Could this problem be causing their trouble too? If so, then perhaps someone should tell them. R-

Good thinking. Perhaps they'll see this thread. I've had this problem as well, although I didn't think to try to save any new flights as default after taking out Ouessant. I'll try it tomorow....Mike F.