First at all, I must say, the RTM Install of the 737 worked from the beginning for me !So I decided not to install the Hotfix 1 and also not the Hotfix 2.Now, as I saw a Hotfix 3 is released, I said to me, why not try it ? Luckily I made a Backup first of the drive where the FSX is installed.First I removed the Liverys, then I applied the Hotfix 3.First startup of the FSX and selecting a 737NGX, the FSX crashed to the Desktop ! Wow, I thought what a great improvement !The second try, then worked, The Plane was loaded, but no EZCAM anylonger. I read about, that this could happen, so I tried just to reintialize the EZCAM again, but this did not work.Ok, then I checked my Throttle and Button assigment oh the Throttle Quadrant. Nothing worked ! Then I thought, OK, maybe they now fixed the Name entry in the aircraft.cfg so all planes are named the same PMDG 737 NGX .... and so on, and not one of them PMDG and the other ones Boeing.To check this, I tried to open FSUIPC (Registered) to assign a new Axis, but also this was no longer possible, the FSUIPC Interface even did not come up ! So all after all, I restored the Drive, and now I am happy again.It costs me about 3 Hours of Backing up, testing and Restoring, to finaly finding out: NEVER TOUCH A RUNNING SYSTEM !

I'm sorry it's not worked for you...I've had no problems. It is strange how variable folks' experience has been with this aircraft...I've been very happy with it and the hotfixes so far.

my system is also running fine and stable with the RTM. have too little time at home anyway to fly so I don't want to waste it by adding and then messing with hotfixes I do not (seem to) need right now. on the other hand, I like the backup approach. guess the FSX folder w/o scenery folders would be enough? as long as gauges, aircraft and the like are covered and not my x gig of ORBX scenery...

HI In 08/16/2011 I install the file PMDG 737 8900 NGX RTM.EXE. (48.121kb)This file is a hot-fix 3 ?My 737 run fine. João Alfredo

As I mentioned in another thread I too was running smooth with the original release version. I applied HotFix 1 when it came out. When I tried to load the 737NGX it asked me to register again; however, it kept telling me my activation code was wrong and so I had to remove and re-install the 737NGX. I did not get a chance to install HotFix two; however, I did install HotFix three. Now my gauges are freezing up and when I exit after a flight FSX does a crash to desktop. I believe at this point I will roll back to the original release again and await the next hotfix.

First at all, I must say, the RTM Install of the 737 worked from the beginning for me !So I decided not to install the Hotfix 1 and also not the Hotfix 2.Now, as I saw a Hotfix 3 is released, I said to me, why not try it ? Luckily I made a Backup first of the drive where the FSX is installed.First I removed the Liverys, then I applied the Hotfix 3.First startup of the FSX and selecting a 737NGX, the FSX crashed to the Desktop ! Wow, I thought what a great improvement !The second try, then worked, The Plane was loaded, but no EZCAM anylonger. I read about, that this could happen, so I tried just to reintialize the EZCAM again, but this did not work.Ok, then I checked my Throttle and Button assigment oh the Throttle Quadrant. Nothing worked ! Then I thought, OK, maybe they now fixed the Name entry in the aircraft.cfg so all planes are named the same PMDG 737 NGX .... and so on, and not one of them PMDG and the other ones Boeing.To check this, I tried to open FSUIPC (Registered) to assign a new Axis, but also this was no longer possible, the FSUIPC Interface even did not come up ! So all after all, I restored the Drive, and now I am happy again.It costs me about 3 Hours of Backing up, testing and Restoring, to finaly finding out: NEVER TOUCH A RUNNING SYSTEM !

Outside of an initial crash which i believe was just user created. I just downloaded the NGX, activated it and didn't even set up my controllers, then just threw a flight plan into the FMC and tried it out. I have not had a problem since setting up my system and NGX. I have stated in previous threads that, unless i get problems, i think i'll just wait for the SP1. Reading your post just convinces me even more. From what i have been reading for the last 10 days and things go the way they have with my set up, i might even wait for reaction before installing the SP1.Sorry if that raises a few eyebrows, but me and Murphy's law have had run-ins before,

Don't fix it if it ain't broken

I'm asking this here

Look at the positive side -- we did not have to pay extra for the freezing DUs and the frustration. PLEASE excuse the sarcasm -- I am just a bit frustrated as many are. PMDG is working hard to solve this ugly wart on a superb plane. After beginning with FS1 (yes, I am that old) I think we are witnessing the final limitation of 32-bit FS for big, complex add-ons. Time for a 64-bit FLIGHT in my humble opinion. Think of the possibilities then! Fly both 32-bit legacy add-ons along with your upgraded and new 64-bit "heavies" ---- wow. I know its coming

Although I had no freezes/CTDs nor activation issues, I applied all hotfixes without collateral effects. But the last one seems to solved a sound issue between 2 monitors - when I clicked the upper panel on monitor 2, PMDG cockpit sounds were muted. Now this issue is gone. It is good to have both FMCs on monitor 2 and use one of them for FSX controls (fuel, pushback, etc). Before hotfix 3, if I did that I couldn’t hear the pushback dialog. To have PMDG sounds back I had to click the main panel on monitor 1. I don’t know if they are solving many other minor issues along these hotfixes or something was done that fixed this sound glitch. Regards,

Look at the positive side -- we did not have to pay extra for the freezing DUs and the frustration. PLEASE excuse the sarcasm -- I am just a bit frustrated as many are. PMDG is working hard to solve this ugly wart on a superb plane. After beginning with FS1 (yes, I am that old) I think we are witnessing the final limitation of 32-bit FS for big, complex add-ons. Time for a 64-bit FLIGHT in my humble opinion. Think of the possibilities then! Fly both 32-bit legacy add-ons along with your upgraded and new 64-bit "heavies" ---- wow. I know its coming

You don't know how much i want you to be right about that, but from what i've read and heard, MS Flight is going to be a totally different platform which will shut out great addons like NGX. If i am wrong, then i could not be happier.

I was doing a flight from PHLI - KBFI, (5 and a half hours worth) I was just exiting the OLM7 STAR for runway 31L (Vectors section), I edited the legs page (310 degree intc) to intercept localiser heading and I suddenly got a fatal error crash, first crash (excluding panel freeze which is fixed for me) I have seen in a very long long time and quite dissapointing after 5 hours of flying. Luckily I had saved it just after I started to descend but my service based failure hours were lost and hours to the log which is annoying. Not sure if it was stictly the NGX's or the new hotfixes fault however.

I just logged into my account on PMDG and Downloading the 737-NGX isntaller which is supposed to have all the fixes in it now. Will let you know the results after I install it.

Update it all works great. Except for a minor issue. I suggestion you uninstall the 737-NGX and go to your PMDG account and login and download the 737-NGX Installer that now has all 3 hot fixes included. Bet this will fix your problem. You can find my observations on the new NGX Installer at the link below. http://forum.avsim.net/topic/345134-third-time-is-the-charm-way-to-go-pmdg-dev-team/page__hl__third+times+the+charm__fromsearch__1

Hmm...... I think I will wait until SP1, as the Plane works for me without any Hotfixes.