Hi there!!! I think that I had found (for sure not discovered) what it looks like black holes in the scenery files of FS2004. It happened already three times out of the north coast of Scotland. The monitor goes black and the simulator reboots automatically but not before reporting the incident to MS. I think I saw something like this reported in the forum a while back but who knows where now. Any comments.Thanks,MABE:-hmmm

A while back I thought I had found one too. But not exactly near Scotland as I haven't flown up there yet. I had imported the Concorde from FS2000 into FS9 and was trying it out by taking off from Heathrow and travelling west, over the Bristol Channel and towards Ireland, then suddenly the program crashed. Trying it more than once I found it happened everytime and at what seemed to be the same place. Using other planes it does not happen. Whether that has anything to do with altitude I don't know, as I think I had got the Concorde pretty high up at that point. I have uninstalled the Concorde from FS9 and installed the freeware French Concorde instead but I have yet to try it to see if the same thing happens.

Two questions:~Have you applied the seasonal CTD fix? (search the forums for "seasonal CTD" if you haven't)~Do you have any add-on scenery installed, especially AFCAD files? Add on scenery and AFCAD can cause CTD's hundreds of miles away from the area they update...-John

Yes, John: I added AFCAD from Project AI (all of commercial ones) but no Scenery ADD-ONS. It fills kind of lonely without them. And yes, I had this problem ever since I found Project AI. I tried the fix with: http://jobia.bei.t-online.de/crashdes.htm and the advice found in: http://forums.avsim.net/dcboard.php?az=sho...opic_id=315#317 with emphasis in the suggestions by Dick at: rhumbaflappy. All MaskClassMap=0 set to zero. No go. It didn't do it. When flying from Manchester to St. Petersburg woammmmm!!! CTD. Right on the ocean. Thanks for answering quickly.Regards,Miguel:-zhelp

Thanks Charles: It happened to me with any airplane but around Manchester. I think it has to do with the AFCAD from Project AI and of course MS-FS2004 great sensitivities.Thanks,Miguel

Miguel, If you can locate all the added AfCad files there is no reason not to temporarily remove them to a folder away from FS and see if the problem goes away. If it does, then you know one or more AfCad files is bad. By adding them back a few at a time you can eventually find which ones are bad.

Charles: Where are they located??? I did it automatically which I heard too late was not the thing to do in the first place.Miguel

Miguel,Sorry I don't have that package so I can't tell you exactly where to find the files. You might try looking in the add on scenery folder first. If not, they might be within the main scenery folder. The names of the files should hopefully contain the airport codes EGxx to give you a clue. I don't know whether there are Ireland codes in the package as that distance is probably close enough to cause trouble too. Maybe someone else could help here please?

Charles:Before I got my CTD I saved the situation first just in case. When I tried to reload the situation a message came up saying a scen.scenfile must be deleted. So!!! Knock your- self out MSFS9 (it did erased it itself). Then I tried to reload the situation again and to my surprise, it did. Change the plane model (I saw a message somewhere that states that CTD has nothing to do with scenery but modules (aircraft)failures. I flew and got to St. Petersburg. Like Igor would say: It

Manuel, I never thought it would be possible that FS could delete a file on its own. Perhaps it just disabled it instead? Glad to hear you seem to be able to fly where you want now.