Deighvid2011

Thanks again Kyle! I have read the intro manual and have seen the recommendations and from now forward will do a better job in following. I will always defer to the ones in the know. So far just saving the flight as not the default flight has worked fine. If there are any potential issues with this procedure please advise. I appreciate you and PMDG! David Rushing www.swavirtual.com

Thanks Kyle. I suppose since my other box operates fine using the ESC back to the splash screen then ESC again to close, I presumed there was something wrong getting the CTD. I also have had no problem on my other box, short-cutting and saving my NGX as my default aircraft along with saving the flight at conclusion so I am still at my last airport for the next flight. Again presuming something was wrong. Using the "X" to close is working. Lessons learned on uninstalling and reinstalling which never made a difference. Still perplexed as to why this happens, I guess some things "just do". Thanks Sir. David Rushing

I have done extensive searching on this subject with no luck finding current information, suggestions or fixes. I have a new build per below specs. I have WIN10 installed on drive C:\ on a 256GB SSD. I have FSX installed on a separate drive known as E:\FSX\ Everything I see appears to indicate there is no problem installing in this manner. I am trying to give as much information as possible with the least number of characters. Only when I install and use the NGX, do I have these problems. I can load the NGX at a gate or on a RWY and everything works normally. This problem starts when I esc and try to exit the program. I get a CTD with the following log files entered. I have seen old posts with this error info, but they are not addressed for WIN8 or 10. - EventData fsx.exe 10.0.61355.0 4643ee0a PMDG_737NGX.DLL 1.0.0.0 55119308 c0000005 000ec433 1288 01d16c621f2f6d36 D:\FSX\fsx.exe D:\FSX\GAUGES\PMDG_737NGX.DLL 888ad428-d855-11e5-9c04-3010b39cbfb7 If I uninstall the NGX and restart my computer and then restart FSX, everything is back to working normal. I can load any default aircraft and everything works fine and I can exit without any issues. I re-install the NGX and sometimes when I start FSX I do not get asked to register the NGX again, nor the warnings about allowing the program to run, which I presume are saved somewhere, however when I go into the cockpit all instruments are dark and can not be operated. Then when I just try to ESC and EXIT I get the crash at exit issue and nothing is saved. On my last build when I was having these problems I just gave up. I uninstalled FSX and followed PMDG's delete FSX instructions and then loaded FSX back on the same drive as WIN10, reinstalled the NGX and never had a problem, which makes no sense because apparently it's well known that Windows and FSX can be on separate drives without issue. I could find nothing that said the NGX would not operate correctly if done this way. Obviously I am missing something and I hope to find someone or ones that can address this from a more current view rather than 2011 to 2013, and before I submit a ticket to PMDG. Thank You. David Rushing HAF X / ASUS X99 PRO/USB / IntelCore i7-5930 3.5 Ghz O/C to 4.3Ghz cooled by H105 Extreme Corsair Vengeance LPX 4 x 4 GB DDR4 3300 / EVGA GeForce GTX 970 4GB Hybrid gaming WIN10 64bit on SAMSUNG 850 PRO 256GB SSD / FSX ON separate SAMSUNG 850 PRO 1TB SSD Photon 1200 P/S.

I just hope someone with PMDG signs on and checks tickets. I built a new rig and while waiting on a replacement SSD to be received, I installed my aircraft on the HDD to check and be sure everything else was working right. Once my replacement SSD arrived, I loaded the OS on it and reformatted the HDD. When I went to reinstall my aircraft along with the updates, only the third install mind you, I got the dreaded "activation of the fulfillment is denied......" So unless I missed something I am sitting around waiting on a response to my ticket request. I searched before I loaded them and found only that there were no restrictions as long as I had all my original information, as I did. Had I known I would have not loaded them. Flying a default plane is like making a paper airplane, so now I am just watching my email. If anyone has a contact give them a call and say a customer is whining and begging for help, he wants to fly.... :(

I sure hope you are right. Seems that more would be heard if the AIRAC had a problem.

I have not found anything in regards to my problem so I would like to know if anyone has any suggestions prior to me having to uninstall and reinstall my NGX. When programming in an arrival and I will use the following as my last flight done, KOMA to KMDW: Flight Plan is "DSM BDF MOTIF4" I departed on RWY 36 KOMA and landed on 4R KMDW. RTE page entered DIRECT ---- DSM, DIRECT --- BDF. Made no differece whether I Activated/Executed at this point. Then DEP/ARR page, DEP selected RWY 36 then made no difference If I selected a SID CATTL1 or BLUFS1 no transition offered. Then in ARR page selected ILS 4R (again made no difference whether I selected the BANER Rwy transition or not. Then selected MOTIF4 ARR, and the first transition offered is BDF, which I selected, but FMC responded "Not in database". (Obviously it is in the database due to inputting BDF in the RTE page. Never-the-less, activated/executed at this point and Legs page showed DSM then BDF then "Discontinuity" and blocks for an entry, which should have been the MOTIF waypoint, with the restrictions as per the approach plate the remainder of the approach is correct MINOK then JOT, to rwy. Opinions from other users state they get the MOTIF waypoint but I do not. I entered it manually with no problems but seems like since this is the first point on the arrival, and has important VNPI, it should be loaded and not have to be entered manually. A sidenote, I had several flights with the same issue, the first waypoint of the arrival does not show up, rather it shows up as a discontinuity. I have no other problems with my PMDG NGX and would hope it is a problem of "operator error" not needing a complete uninstall and reinstall. Also note that AIRAC 1206 is current and installed. Thanks for any suggestions. I tried to be brief but detailed enough to see if anyone could duplicate the issue. Thanks in advance. David Rushing Jackson, MS