Been getting this too, except my final freezes are full on CTDs.

Maybe arguing semantics a bit, but the hotfixes WOULD be cumulative if you only needed the latest one. ;)

Yup. It was a typo that I already fixed. :(

Yup. It was a typo that I already fixed.

No problem.

Applied both hotfixes (I heard there was a 3rd one, but I can't find it? I have 2622 or whatever the latest one is....)... I thought everyone was referring to a complete FSX freeze. That's happened a few times on final, too.

the download link in RSR's sticky post was updated. also, you you login to the shop and download the whole NGX package and install that, it will nicely update your existing installation.

Guys you know whats really handy for helping folks out is if you go into your settings and add your specs to your signature like Majid, Anyways I had something like this happen to me awhile ago way before the ngx even came out, the cause was a new feature of nvdia drivers, the Auto Update, while doing a flight it became active and began to search for new drivers I suppose, and the MD11 locked up completely, the next time this happens if you can get to your task manager and see if anything unusual is running in the background ie anything that says auto update, I forget the exact name of the process, I leave this option out of my installs from now on.

Guys you know whats really handy for helping folks out is if you go into your settings and add your specs to your signature

Good point. I hope we don't get jumped by those who vocally complained about the "useless" hardware sigs recently. :(

Have hade the same problem on final and now inflight. Anybody confirmed any improvement with the hotfix?

Had this happen to me as well with hotfix 2 (not yet on 3). Panel froze but sim still ran and I could still brake, spool up engines but nothing else. Panel and control surfaces froze. Happened right after landing. Wierd....

Now I finally understand. I thought I was the only one having this problem. I thought everyone else was having classic CTD and I have not had THAT problem. With the original download when I disconnected the AP on short final the a/c would immediately roll right and hit the ground wing and nose first. FSX would continue to run but NGX would not respond to any control input and the altimeter was frozen to the altitude it was at when I disconnected. Before I applied the fix, I tried to test out different settings on FSX and my graphics card. I saved situations at different stages of approach for the tests. The only problem was that each time I attempted to reload a saved flight, FSX would give me a fatal error. So I applied fix #1 and it eliminated the loss of control on AP disconnect BUT this time it froze the entire flight the moment I started to flare. It also did this on autoland! I could not go to the menu or even close the program. Had to use Task Mgr to end the program and regain control of computer! I was able, however, to now access saved scenerios but the FMC programming would not reload. I had to reprogram everything before I could unpause and begin the flight. When I accessed a menu item such as weather or map view and then returned to the flight, much of the scenery would either disappear or become terribly corrupted and within a few minutes the flight would totally freeze. I uninstalled the fix and did a completely clean reinstall of the original program and most of the time everything works perfectly - no CTD or freezes but still, every so often, accessing menus and then returning to the flight will corrupt the panel or scenery and I will have to close out and restart, but at least I can now save and reload. Most importantly, I have had 8 completed flights without any weird anomalies on short final or touchdown. To address a point that was put forth in an earlier post on this thread: while having my problems I had a monitor window active and never observed an overtaxed memory or CPU core no matter how busy the scenery was. And BTW my freezes were occurring with all sliders to the left and traffic and weather off so I do believe it has something to do with the way NGX is programmed rather than our hardware. I am able to fly with ASE/UT2 and all sliders to the right with all my other complex products and still average over 30 fps in most areas. I am going to wait until the dust settles before I apply any new fixes. Eventually an SP will be out once they firmly get a handle everything.

very much doubt that this is the reason for the panel freezes. I'm running FSX on Windows 7 x64 Home Premium with 4GB of RAM. When the last panel freeze happened, I had autogen to Sparse, flew from Unakleet to Barrow, over the Alaskian tundra in default scenery, where trees and buildings are pretty much non-existent anyway, and there was no traffic around. The FSX.exe was listed with 1.8 GB of memory consumption in the task manager (I've seen it go up as high as 2.8 GB

Just out of curiosity are you using 32-Bit windows? Also what video card and how much onboard memory on the card?

Take a look at this post. : http://forum.avsim.net/topic/344959-hotfis-8-16-issue/unread/

I very much doubt that this is the reason for the panel freezes. I'm running FSX on Windows 7 x64 Home Premium with 4GB of RAM. When the last panel freeze happened,

I'm running FSX on a quad core q6600 with 8 gigs of ram, twin video cards in sli mode, and a load of other niceties.. It freezes every time on me.. Or, did at least.. The problem is not the machine, but the FSX 32 bit architecture. It can only access 3 gigs of ram, and it cant swap out for other ram that you may have as overhead. It also doesnt make real good use of your video cards. its mostly CPU driven. So, if like mine, your FSX is at any given time using over a gig and a half of ram, youve already used up half of whats available too it. Since it doesnt make any real use of the GPUs capabilities, all those textures are also loaded into its available ram. now youve got even less, and those textures are each 4096x4096 pixels in size. you animate them ( as in do a flight ) and now youve got two or three frames loaded into the buffers, or up to three sets of textures loaded into memory. Add in the floating point calculations that this bird needs to be as real as it is, and your talking some majorly serious usage of memory.. And thats where its suspected the freezes come from..I resized one of my textures to 2048x2048 and the last test flight i took, had zero problems. PS.. I'm running 64 bit Windows 7 Ultimate. I could put 64 gigs of ram in this machine if i wanted, and the end result would still be that FSX freezes..

So what you are saying is that PMDG built an FSX add-on aircraft that basically can't run on FSX because of the FSX architecture? I highly doubt that as well. I think it would be better if we wouldn't just stab in the dark with strange and unlikely theories and just wait for the official word on these issues.

I resized one of my textures to 2048x2048 and the last test flight i took, had zero problems.

One flight is hardly conclusive. I did several successful flights between panel freezes. Do quite a few more flights with lots of FMC operation and only then you will know if you really succeded.

Just out of curiosity are you using 32-Bit windows? Also what video card and how much onboard memory on the card?

I already said that I used 64 bit Windows 7 in the part that you quoted. The rest of my system specs can be found in my signature.

For edification, I am using a I7 975, 6gb of RAM and two 1gb Ati 5870 cards on W7 64bit. So it ain't the 'puter. Though the comments about FSX 32 bit is interesting. Would love if a dev would wade in with their thoughts on this freeze issue.

So what you are saying is that PMDG built an FSX add-on aircraft that basically can't run on FSX because of the FSX architecture? I highly doubt that as well. I think it would be better if we wouldn't just stab in the dark with strange and unlikely theories and just wait for the official word on these issues. One flight is hardly conclusive. I did several successful flights between panel freezes. Do quite a few more flights with lots of FMC operation and only then you will know if you really succeded.

I'm saying that PMDG has built an aircraft that runs fine in a 32 bit environment where there isnt a lot of graphics overhead that needs to be remapped to main memory.. Thats what PMDG themselves are saying.. I also agree that one success out of 32 tests is not conclusive by any stretch of the imagination. However, it does validate the continuance of testing instead of just chalking the plane up to a 70 dollar waste of money. However, I am very optimistic about the success of further tests, and optimism isnt my normal gig.