Hi everyone!I need someone to confirm this-1) Pick some random airplane and back up your panel.cfg file.2) Delete the contents of the Panel.cfg, and add this instead: alias=PMDG737-700/panel.3) Note your frames.4) Replace the edited panel.cfg with the original.5) Reload the plane, go back into FS, and note frames.6) Report both frames here.I stubled across this tonight by chance when I wanted to use the PMDG panel with the FFX 737-800. I experienced significantly lower frames with the PMDG panel than with the default 737-400 panel. I realize that their should be a difference since the PMDG is more complex, but I found a 10 frame-plus difference. This cannot be simply attributed to the additional complexity of the PMDG panel. I believe the culprit to be the main.gau file, which some people report having trouble loading. I am currently of the belief that these problems may be related. I am thinking that the frame problem when we use the VC stems from the memory leak in the panel, since we are having to load it twice (once in the main panel and once in the VC), it doubles the memory leakage and we notice it. The memory leakage is still there with just the 2D panel, but we don't notice it because we only have to load the main.gau file once, and the frame hit is therefore half as much. If we can confirm that we get a significant reduction of frames when we alias the PMDG panel, that certainly narrows the options down for Lefteris and team as they attempt to fix this.Hope we can nail this sucker-

Hi Matt,I would be very careful aliasing this panel to other aircraft. The readme in the docs supplied clearly states that this is a reason for not getting further support. I don't know what harm a simple aliasing statement in another panel.cfg can do, but the security system that PMDG have designed is really sensitive.Just my opinion, and I only state it as you're asking others to do it too, albeit for a good reason in trying to find out what the memory issue is. :)Bruce.

Wow. Thanks for the heads-up! I didn't read the read-me, of course. What a bonehead I am.PMDG- Really sorry about this. I was honestly just trying to help. Is there any way you could give us a special dispensation so that we could alias just to run this test?Thanks a TON, either way.Regards-Matt "Read-me's are for whimps" Smith ;-)

Hi Matt,Have you tried the PMDG 737NG since you used the aliasing statement in the other panel.cfg? You might want to check this out :)Thanks,Bruce.

I just had the same thought. Scared me to death for a moment. However, I just loaded up FS and the PMDG works fine, so no ill effects using the aliasing statement that I used. Baffling why they included the warning in the read-me.Regards-

Hi Matt,I'm glad it's working OK :)Bruce.

Just my "op" on this:if i payed 40 US Dollers for a plane and a panel, i gonna use this panel on every plane i like to use it!!!!!!If this should be a problem, PMDG should let me know, then they could send a "companyman" to my house to delete the 737 NG and give me my money back.loud and clearsorry for the bad grammerMcDanielDaniel Niederer

Hi all. It isnt that we do not "allow" merges, nor will we stop giving support to those who choose to merge. However, we simply cannot give support on problems resulting from a merge, and will not address issues of anomolous behavior of the panel, model, or FDE when they are linked/merged with a non PMDG panel, model or FDE.Vin ScimonePMDGwww.precisionmanuals.comhttp://www.vinscimone.com/dancnkid.gif

ok, so i take my words back, sorry and thanks for the statement!!GreetsDaniel Niederer

Where did I put my black suit and my dark sunglasses ?When I find them...heheheAnthony MertonPrecision Manuals Developmenthttp://www.precisionmanuals.com