Hi All,I am not sure yet but it seems that since I have upgraded to the SU5 release I get a Memory Low message on both my #1 PC running FS and the #2 PC running ASV via FSUIPC. It usually runs like normal for about an hour or so and goes through multiple online refresh cycles. Has anyone else seen this since upgrading or knows of a simple way to troubleshoot short of going back to before SU5 ???Any tips appreciated.

Hi Sunny,No reports of this as far as I know. Have you added any FS04 scenery lately or since SU5?Not sure what else to suggest.Jimhttp://www.hifisim.com/Active Sky V6 Development Team Active Sky V6 Proud SupporterHiFi Beta TeamRadar Contact Supporter: http://www.jdtllc.com/AirSource Member: http://www.air-source.us/FSEconomy Member:http://www.fseconomy.com/

I don't have an answer to your problem, but I do have a suggestion for troubleshooting.On both machines, open Windows Task Manager. Click on the Processes tab. On the menu, click View, then Select Columns. Add a check to Peak Memory Usage. Click OK. At the bottom, add a check to Show processes from all users.Load everything you need for a flight, including being at your start position within the sim. Make a note of the memory usage for each program listed (easiest way is to take a screen print and save that somewhere.)Now minimize both Task Managers and go fly. When you get the out of memory error, do NOT close the programs. Restore the Task Managers and compare the current memory usage to the previous usage with particular attention to the peak usage.This should point you towards the program that is causing the problem.Hope that helps,...jim

Hi Jim and Jim,thanks for the replies. I have not installed anything new since the new version of ASV. On either machine. And both of them are showing this funky problem.One thing I did notice is that I was not using the latest version of FSUIPC. I had 3.65 running instead of 3.70I will try Jim Browns suggestion of adding the peak memory useage and see where that leads me....but so far with the new FSUIPC version installed on both machines it seems that they behave again.