Page 1 of 1

Help needed

PostPosted: Tue May 29, 2007 4:35 pm
by kagazi
Long time reader...first time posting.  For some odd reason fsx.1 no longer allows me to download real-world data.  As soon as I try, fsx.1 freezes and produces a fatal error.  This began to occur yesterday out of the blue.  

I was wondering if this problem has been seen before. If so, aside from complete reinstall, is there a quick fix?  

I have XP SP2 fsx.1 with sdk.1 installed.  The only real addon is KIAD by Blueprint Simulations and MyTrafficX 5.

I tried to repair fsx using the cd and after repair I was able to download the weather for the default airport that first shows up.  If I changed airports and attempted to re-download real-world weather fsx crashes.  Oddly, the first screen that shows the weather being downloaded appears and the bar goes to the end as though it's loading data...then nothing for a few seconds until the fatal error message shows up.  I even tried to uninstall KIAD and reinstall sp1 for fsx.  Again, it worked for the first default airport and nothing else.

I'm getting ready to reinstall fsx and the sp, but before going through the trouble I was hoping someone has seen this issue before.

Prior to this issue I have never experienced any problems with fsx.  And other than not being able to download real-world weather, everything else works fine.

thank you for your help.

kagazi

Re: Help needed

PostPosted: Tue May 29, 2007 4:44 pm
by Hagar
Hi kagazi. Before doing anything hasty you might like to check this out. http://www.simviation.com/cgi-bin/yabb2/YaBB.pl?num=1180452718

It seems the Real Weather site is having problems.

Re: Help needed

PostPosted: Tue May 29, 2007 6:41 pm
by kagazi
Hagar,
thank you.  I'll read the post mentioned and also wait a day or so to see if things work themselves out.  The reinstall option is not one I was looking forward to.

regards,
kagazi

Re: Help needed

PostPosted: Thu May 31, 2007 7:49 am
by kagazi
Hagar: Again thank you for your help...everything returned to normal as of yesterday.  Maybe this issue and "wait it out" solution should be sicky'd somewhere, especially if it occurs from time to time :-)