I did have a CTD problem as soon as my flight loaded. It had to do with my NGX loading with my default flight. If your NGX is loaded as part of your default flight, I'd suggest first changing to a default aircraft and saving that as your default flight before installing to prevent this possible problem. Aside from that, I've been trouble free so far. The part about deleting the entries from the fsx.cfg is pretty crucial too, I would imagine, as not deleting them seems to create CTDs also. My pre hotfix procedure was to copy the aircraft.cfg files to my desktop so I could reinstall my liveries with ease, then I deleted them from their original location. Then open fsx.cfg and delete the pmdg ngx entries from the trusted section. Those are the only steps I took. AFTER I started having problems, I followed the suggestion about deleting the shader folder, but I don't think it was ever part of my problem. I had to learn the hard way about saving a default aircraft to my default flight first.

After reading that I am scared to try deleting the cfg's, but what the heck, I can always reinstall it if I need to. For some reason not having the proper number in the cfg's bothers me because I am not sure if they have been updated properly. Sean Campbell

Hi Sean, After writing this I noticed someone else said the enb mod was working again with this latest version of the NGX and since I've been really missing the enb mod I figured it might be worth trying to get this latest hotfix work just a little bit more so after applying the hotfix I deleted all my previous states and situations and started FSX with the default flight and then switched over to the default FSX Cessna 172 and then to the NGX and set everything up again and this time it seems to work at least so far and now also with the enb mod back in the FSX folder so for the time being I'm very happy :( Will give the hotfix together with the enb mod a chance tonight when doing a flight and see how well it works. One thing I noticed though was that if using both the enb mod and the Antilag FPS limiter I got a CTD with the d3d9.dll module reported in the event log. So...I hope this CTD was only because I used the combo of the Antilag FPS limiter and the enb mod and I'm now back only using the enb mod and the Java-based FPS limiter instead. Will report back how things work out.

I've git a queation about the hotfix. What happened to the option to disable the autotuning of the ILS-course?I can't find it anymory and I want to tune in the course myself because sometimes it tunes in the wrong course. Was that a change of the hotfix? It looks like some of the option for the aircraft configuration got changed. So can someone please tell my how to disable the autotuning with the latest version installed. Thanks Paul

can we please have a proper changelog so we could see what was actually done ? in "\FSX\PMDG\PMDG 737 NGX\Aircraft" edit the correct file for the model u want to configure and change this

[AFS]AutotuneOBSinLOC=0

Thank you!This way I can change it, but where is the option within the FMC. Before the hotfix it was on the first site of the aircraft options, on the bottom of the page. Now there is an empty space.Is it it still possible to change this within the FMC or is there a reason the option has been dropped? Thanks

I am curious. My IRS CDU showed countdown to alignment by selecting HDG on top dial. I have the original Aug 5th version with no fixes. I have had no CTD's and I start my FSX startup with a default FSX plane first so that may be why I have been successful. I also have a 2.66GHZ Intel Quad Core but I have Affinity set to 14 so only use two cores. Again, no fatal errors or CTDs at anytime. Frame rates do vary wildly sometimes in external view over heavy scenery and heavy weather but very smooth in VC or 2D panel views. My main issues are: 1) Go Around procedure is wrongly implemented; 2) restarting a situation adds 9000 ft to the radio altimeter setting; 3) wild oscillations in ADF gauge; and finally, 4) no way to refill fluid levels. Are any of these issues corrected in fix #4? If so then I may attempt to implement the fix. If I do, however, must I first update to the new installer or can I add the fix to my original installation?

Richard, I see you have FSX installed in proggyfiles x86, not a good idea mate, prob not helping your cause.

I know you are usually suggested not to install FSX using the default path since you might end up with problems caused by the proggyfiles directory is a bit of a system directory but in my case this is not the default proggyfiles directory located on the C (system) partition but a directory with the same name but on a separate partition in this case F which I only use for FSX and FSX related stuff and programs so I don't think that should be a problem since that directory in the eyes of Windows is just like any other directory...?

I did have a CTD problem as soon as my flight loaded. It had to do with my NGX loading with my default flight. If your NGX is loaded as part of your default flight, I'd suggest first changing to a default aircraft and saving that as your default flight before installing to prevent this possible problem. Aside from that, I've been trouble free so far. The part about deleting the entries from the fsx.cfg is pretty crucial too, I would imagine, as not deleting them seems to create CTDs also. My pre hotfix procedure was to copy the aircraft.cfg files to my desktop so I could reinstall my liveries with ease, then I deleted them from their original location. Then open fsx.cfg and delete the pmdg ngx entries from the trusted section. Those are the only steps I took. AFTER I started having problems, I followed the suggestion about deleting the shader folder, but I don't think it was ever part of my problem. I had to learn the hard way about saving a default aircraft to my default flight first.

I never changed the default flight,so that's ok.....I really not comfortable with deleting entries from FSX cfg. files. Changing yes deleting, no. Which entries to delete would be the questionI found the Shader files so that will be ok also if needed.Coping the Aircraft cfg seems easy enough but how do I re-instate them.( I gonna put you on my Xmas list)

...........

backup backup, backup dont delete anything, rename, or move.in fsx.cfg u can comment lines out with a semi-colon at the start of the line like so,

;comment

that way fsx will ignore that line, or just backup the entire fsx.cfg file.all u need to backup from the ngx aircraft.cfg is copy paste the [fltsim.X] sections to some text file, which are the liveries info. and paste them back to the new aircraft.cfg in the same place.sorry if this is not clear enough, just trying to save some typing, and i dont want to over elaborate for no good reason, since im sure most ppl are already familiar with these procedures.if u need more info just ask.

Thanks to all for your responses...You were very clear... Seems like a lot to do for an hot fix Unlike most ppl I have never had to re-install FSX to a different location or Win7 to fix something. Or make any cfg. changes to make things work, It just works. I think I'll wait for the SP since I am not having any real significant problems.

Thanks so much.

....we will also be moving certain members of the team to the 777 in order to get that project moving at full speed, so we'll just plan for a few months between each of the NGX expansion packages. (Whoa... Did he just mention the 777? Yes, yes he did.) Okay folks- I think that is all I have for you tonight!

and the Dash..? He he he ;)

Considering that many of you have heavily customized your Aircraft.cfg files it is not a suprise that some of you are not having all your aircraft.cfg files updated to the latest version. Your safest best is to just reinstall the NGX, Hotfix, Liveries, then any other modifications you made. I did it this way and all works fine. I did not know the First Officer Terrain was now operational so will check that out on my next flight. Did anyone notice the 737-800WL turned into a 900WL? It appears that way to me. When loading up max passengers intead of 162 it loads 174 lilke it is a 900?

tks mate, downloading.........im waiting for more...........hehehe.

Considering that many of you have heavily customized your Aircraft.cfg files it is not a suprise that some of you are not having all your aircraft.cfg files updated to the latest version. Your safest best is to just reinstall the NGX, Hotfix, Liveries, then any other modifications you made. I did it this way and all works fine. I did not know the First Officer Terrain was now operational so will check that out on my next flight. Did anyone notice the 737-800WL turned into a 900WL? It appears that way to me. When loading up max passengers intead of 162 it loads 174 lilke it is a 900?

Paul, I still only load 162 pax in a two class config. in my -800 when I press the 'set full' button. Is this what you meant?

but they should be deleted before applying the hotfix or they will not all be updated to the latest version.

Wrong. I didn't delete mine and all updated correctly.

Paul, I still only load 162 pax in a two class config. in my -800 when I press the 'set full' button. Is this what you meant?

Yes thats what I mean. I loaded up the Ryan Air Livery at KBOS and went to load max passengers in the 800 Winglets and it loaded 174 instead of 162. I going to go back and look at everything again and see if I missed something.