Dicko

Thanks Richard

Is this a complete uninstall-reinstall or an update to existing program. Thanks Andrew

I want one!

That confirms an issue at Avsim and not specifically with my ISP. I too am back on line.

Finally able to log in!

try logging off Avsim then on the same computer access the Avsim forums. try logging off Avsim then on the same computer access the Avsim forums.Did you manage to log back in. Thanks Andrew

I have no idea why this is happening. I even tried from another computer at work and get the 503 error. The website 'is it down right now' shows Avsim.net has been down for everyone for 19 hours! At this stage I cannot even get onto the website apart from my iPad which I have not logged out on. If this is happening to others they will be unable to log a problem on the forums. I reiterate......I was unable to access Avsim.net after logging off. If I didn't log off the website was accessible as per normal. Andrew

I am unable to log onto the Avsim Forum Website after logging out. I have three computers and each time I logged out was unable to get back on the website. Each time after logging out I get the dreaded 503 message. This post was done using my iPad which I havnt logged out on. Any ideas, I also cannot log on from any other computer. Andrew Dixon

They're working on it!

I had this problem, downloaded Notepad++ and changed the encoding from UTF-8 format to ANSI. I deleted the XML entries created by the FSDT installer. I then re installed GSX again with no warning of a corrupt XML file.

Are there any more developments with this?

Yes

It is my understanding this issue is with 777 not NGX I keep a copy of all NAVDATA cycles I use. Check your PM.

I think Kyle is correct with the assumption that the version of NAVDATA installed contributes to the VAS leakage and ultimate OOM when approaching KLAX. With 1503 I started to experience OOMs when approaching KLAX for the first time. I lowered my FSX settings and repeated the same flight from KIAH (Flightbeam) to KLAX (FSDT) and observed VAS usage using Sysinternal Process Explorer. ASN was the weather platform used. I observed the gradual increase in VAS which coincided with imputing the approach and destination runway while enroute to KLAX. The arrival SEAVU 2 for 25L. On final OOM. This could be reproduced again and again. I then rolled back to 1412, increased my FSX settings including autogen and then repeated the flight. No OOM with VAS after landing 3237204. On the runway at KIAH prior to takeoff, VAS was 2761708 which dropped to 2740884 2 hours into the flight. I have no idea why this has occurred but rolling back the NAVDATA from 1503 to 1412 has allowed me to again fly to KLAX without running out of memory.

I will test tomorrow. Getting late. I have rolled back to cycle 1412, not just the KLAX txt file.I hope this can be sorted soon.