Directed mainly to Lefteris, just wondering if you may have found yet the source of the memory usage and is it fixable? Thanks

bump

From what PMDG indicated that issue will be addressed with the patch that comes out the at or around the 19th.I'm sure once the patch comes out most if not all of the issues people have been having will be resolved.Jason

Eric, and all-The memory usage you see is partly our fault and partly a result of wanting to please everyone too much!I will NOT go into more detail about it, as I might have to retract my statements later, but I will say this:It seems that with each extra panel that we create (for example, we have four different panels for the Main View), FS wants to eat up lots of memory for the panel bitmaps themselves. Each bitmap is 24bit quality, therefore eating up lots of space in memory.This is not the only reason - there are others, but I cannot divulge any more details, as I want to be 100% certain about them.Suffice it to say, "we're looking deep into it!" ;-)As for the frame rate issues... Well, that's solved! ;-)

Lefteris,How can it be the bitmaps causing the problem though when the tests that some of us ran showed the "main" .gau gauge files as directly causing the high memory usage? The bitmaps only add up to 46.6MB if you select all of them - I did discover something else though:I'm fairly sure it's loading completely new instances of the CRT's with each panel view. Could that have something to do with it? I verified this by setting a super-low brightness on the ND, then loading the "Z" view - the ND in that view was normal in it's brightness and it took about 10 seconds for the "Z" view to come up. I then went to the approach panel and got the same thing setting a medium level brightness - I can switch between them and they all retain their individual settings. Doesn't that suggest that they're all separately running in memory?Ryan