You guys may be on to something here. I got my first panel freeze when I first installed the airplane and flew it for the first time. I then attempted another flight and had no issues. I've been flying this airplane with the PMDG paint job, since from the cockpit I can't see the paint job anyway. I updated to HF 3 and haven't seen any freezes since. See Yah! Ray

WAIT. GUYS. I jsut realized, the textures are 4096 by 4096, and whenever people enable this feature (actually using HD mode) it seems to freeze SOME users' FSX. I wonder if this is connected to the panel freeze?

Don't see how, being as all the liveries use the same size DDS files. All of them, includingthe PMDG livery are 4096. Like I say, there is no logical explanation for this at all. The only thing I can think of, is possibly a problem if switching from the differentliveries. IE: you load the PMDG colors, but then switch to another livery.Myself, I have never had a problem doing this as long as I select a different model,but it's possible it could cause more memory to be used in the switching process.That's only a theory though..When I fire my sim up, my default flight is the Lear 45. I choose the NGX livery I want,and only that one.. I never switch once I've selected one.. But.. I fly Southwest 95.5 %of the time, so I'm almost always going to that one.Maybe that's why I've never had any trouble.Seems to me if this were an actual code/DDS problem, I would see the same problem.But.. I never have with any of the liveries I've tried so far.The only other liveries I ever really use are Continental, United, Delta and AA.And those last four I only use if I want to fly a route that SWA doesn't go to..IE: when I flew to Honduras, I believe I was a Delta buoy.. Or was it Continental.. :/One of those two.. I think they both go there.I've never had any trouble with any of them, and so far, the only textures I'veconverted to 2048 are the Southwest. All my others are still bone stock 4096..

No, I have seen it happen. Users that have HD textures enabled WILL see freezes on some machines. FSX out of the box cannot support 4096/4096 texture resolution, even at maximum resolution in the settings. You must physically tell it to use the full HD by eding the FSX.cfg to load in 4096/4096. This is the process I was speaking of. Some users (if they use REX, which does it automatically) may have automated tools that do this changed without their knowledge. Although these freezes I talk about are FSX actually freezing, it is definitely a memory issue, and seeing as though these freezes are appearing on certain variants in certain airports, are re creatable for the users that have them, BUT only some users have it, it definitely appears to be a user specific setting/hardware issue somewhere.

Is there an official thread where PMDG is keeping track of freezing issues? I am in my second flight with the babe and I am experiencing freezes. Some of them hard enough that the circling icon shows in Windows. Other are just a couple of seconds. I am flying the American Airlines livery, I had the same issue with the Alaska Boeing livery.My computer specs:Intel 2600K Sandy bridgeWindows Vista Home Premium 6416GB Ram7200 rpm Seagate HDNvidia GTX 470 with drivers 280.26

No, I have seen it happen. Users that have HD textures enabled WILL see freezes on some machines. FSX out of the box cannot support 4096/4096 texture resolution, even at maximum resolution in the settings. You must physically tell it to use the full HD by eding the FSX.cfg to load in 4096/4096. This is the process I was speaking of. Some users (if they use REX, which does it automatically) may have automated tools that do this changed without their knowledge. Although these freezes I talk about are FSX actually freezing, it is definitely a memory issue, and seeing as though these freezes are appearing on certain variants in certain airports, are re creatable for the users that have them, BUT only some users have it, it definitely appears to be a user specific setting/hardware issue somewhere.

Sure, they will increase the memory load. That's why I converted mine to 2048.My point was that all the PMDG textures are 4096. So if they are running in HDmode with the fsx.cfg set to 4096, if they see OOM's, it should do it onall of them, Including the house livery.I assume they are running 4096 in the cfg, which is why I said it made noreal sense for there to be a difference in livery textures.If they crash using the add on liveries in such a 4096 config, they should also becrashing using the house livery being as there is no size difference in thetextures.I've actually been running mine in default 1024 mode lately. The differencesin graphic quality are pretty small, and I want all the memory I can scrape upbeing as I'm running XP 32 bit. .

That is true, but the newly installed files may be more fragmented than files installed with the program. I had a far-fetched idea, I am just trying to help. I had an issue with the NGX for a while, and I want to make sure no one goes with out it.