I just arrived in Portugal and installed my PC that followed me, fired up FS9 and... CTD, CTD, CTD, and more CTD! Whereas my FS9 performed perfectly well in Switzerland a few weeks ago, I am now unable to even start a flight regardless of the country or airport choosen. In such cases one must go through the list of the latest installed products so as to determine which one is the culprit.So here it is: Cloud 9 KLAX, REX Overdrive and a bunch of meshes from FS Genesis (many of them). I unselected KLAX from the scenery cfg. list and I still got my CTD, could any of the other products (i.e. REX Overdrive and FS Genesis) cause such a problem? One last piece of information, I have - apparently - no CTD when I start FS9 without REX or Active Sky Evolution. I just started one such scenario loading the IFly 737 in LFPO with no trouble, but as soon as I started Active Sky, bingo. Same phenomenon with REX, if I load FS9 through REX, then as soon as I get my airport on the screen (with standard Cessna), the message of error is there. So it would appear that this error is linked to the weather software (both and separately). On a last attempt, I loaded FS9 with no weather, prepared my flight planning and aircraft (Leonardo MD82) at KLAX, then used the FS9 weather request and there I go again: error message. This problem is definitely the result of weather, since any weather system I use terminates FS9.Could the change of country (and therefore of IP) be a cause? I worked in China in the past and do not remember having had such a problem with the same FS9 install. I would welcome feedback from anyone who encountered this and could solve it.With thanks and best regards.

I just arrived in Portugal and installed my PC that followed me, fired up FS9 and... CTD, CTD, CTD, and more CTD! Whereas my FS9 performed perfectly well in Switzerland a few weeks ago, I am now unable to even start a flight regardless of the country or airport choosen. In such cases one must go through the list of the latest installed products so as to determine which one is the culprit.So here it is: Cloud 9 KLAX, REX Overdrive and a bunch of meshes from FS Genesis (many of them). I unselected KLAX from the scenery cfg. list and I still got my CTD, could any of the other products (i.e. REX Overdrive and FS Genesis) cause such a problem? One last piece of information, I have - apparently - no CTD when I start FS9 without REX or Active Sky Evolution. I just started one such scenario loading the IFly 737 in LFPO with no trouble, but as soon as I started Active Sky, bingo. Same phenomenon with REX, if I load FS9 through REX, then as soon as I get my airport on the screen (with standard Cessna), the message of error is there. So it would appear that this error is linked to the weather software (both and separately). On a last attempt, I loaded FS9 with no weather, prepared my flight planning and aircraft (Leonardo MD82) at KLAX, then used the FS9 weather request and there I go again: error message. This problem is definitely the result of weather, since any weather system I use terminates FS9.Could the change of country (and therefore of IP) be a cause? I worked in China in the past and do not remember having had such a problem with the same FS9 install. I would welcome feedback from anyone who encountered this and could solve it.With thanks and best regards.

Your change in machine IP should have no effect - any system that uses a dynamic IP will have it change from time to time. It may be that whatever isp server you are accessing has no idea how to route the requests from the programs and your getting some weird error response instead of data.DJ

An easy way to check your net operation is to go into the the AVSIM page and see if it loads OK. Next see if you can download something from the library.It also would not hurt to update FSUIPC used I believe in the FS9 version of ASE. Get the latest version from:http://forum.simflight.com/topic/66139-updated-modules/FS9 and apps suck a lot of RAM. It would not hurt to check that all of RAM and cards and chips are fully seated after being bounced around in shipping. Make sure all of your cooling sinks and fans are functional. Look for anything floating around in the case. Check extra power connections to your video card (if it needs one) as well as cooling fans. When I run FS9 my processor heats up more than on less intensive applications.You have ASE. Rather than use real weather download an archive and load that for an FS flight to get the network out of the picture. See if you can access the ASE servers to get an archive. You don't need to run FS to download an archive.Regarding those two distress calls they are both explained here:http://en.wikipedia.org/wiki/Mayday_%28distress_signal%29

Thank you for your replies and suggestions.Unfortunately, none unlocked the situation, I made further tests today using FS9 weather themes (no download hence isolating the possible IP error) and I got the same result, therefore the download is not a factor. Again the summary of the problem is simple, as long as I do not add weather, FS9 is fine, as soon as I load ANY weather from ANY source (FS9 weather engine, FS9 weather download, REX or ASE) an immediate CTD happens. I am at a loss to understand. Any assistance would be greatly appreciated.With best wishes.

Jean-Claude,This may sound strange but I had the same problem and this cured it.Make sure Render To Texture is ticked.Once ticked quit FS and then reload it should be fine.Hope this helps.Mark

That is certainly a possibility if any add-on cloud sets are used. Maybe it suddenly changed.

Jean-Claude,This may sound strange but I had the same problem and this cured it.Make sure Render To Texture is ticked.Once ticked quit FS and then reload it should be fine.Hope this helps.Mark

Mark,I don't know how to thank you, it did work! Consider that I offer you a virtual bottle of Madeira wine as a thank you gesture...Now just how and why did this box get unticked is another matter, but what does matter is that I can now fly, even with clouds!!!Greetings from Madeira!Best regards,