ekilmer

Hello. I know there are several threads concerning VAS usage. I also know PMDG rather staunchly asserts there is no VAS leakage with the 747. However, I thought I would start a new thread and toss in what I have discovered. I tried four times to fly from KABQ to LEST. All four attempts failed in an OOM at about three hours into the flight. I finally took the 777 and successfully completed the 10-hour flight. I got to thinking about the major differences between the 74 and the 77 and wondering why, despite PMDG's assertions to the contrary, the 74 seemed to be leaking memory. The major difference is the addition of ground service vehicles for the 74. Therefore, I determined to fly back to KABQ from LEST in the 74 but not request any PMDG ground vehicles. The only ground service I called for was ground power. This GPU is not drug into position by any vehicle. I did, however, use all the GSX ground services available. I successfully completed this 10-hour flight with no problems, though the 74 still seems to burn more memory than the 77. I obtained this information from the flight log files generated by FSUIPC. I did not change any of my FSX configuration settings between these flights, so I deem them negligible. What is important is that the FSX environment was the same for all three flights. I humbly submit the foregoing information for your, the forum's, evaluation. (I would have attached the three log files, but there does not seem to be a way to do this.) Eugene N. Kilmer

Hello, Jeff. I have seen that scary anomaly with every flight I have taken. However, I have been able to cancel all the alarms using the buttons on the overhead panel. I took one flight that was long enough to have it happen twice.

I was having the same problem until I opened a ticket and Paul provided this link to a Flight1 utility for repairing the registry. There are several utilities here. Be sure to download the one for repairing the registry.http://www.flight1.com/view.asp?page=libraryIt was very easy to do and fixed the problem. Now, both the STAR waypoints that were not lining up with the runway, and the localizer alignment error, were fixed. Also, this problem only appeared while trying to fly the 747. The 737 and JetStream never had this problem, either before my registry was repaired or after.Gene