Installed the PMDG NGX Hot Fix this morning, hoping that display freeze issues would be resolved. Unfortunately, they were not resolved. Situation:KSFO to KMRY, MOLEN SID.SNS.RNAVZ 28L.KMRYB737-800 – No WingletsAdd-On’s: GoFlight FSX Bridge & software V2.01FSX Weather – NoneStartup sequence: FSX B737 at KICT, re-positioned to KSFO, loaded NGX B737-800. No further changes. Loaded flight plan & departed.Issue 1: After takeoff with 2D panel open, accessed the FSX Menu – Add Ons – FSUIPC (sequence that caused problems in the past). FSUIPC interface opened correctly. However, when closed, the NGX 2d panel did not correctly re-open, the FSUIPC remained, and the FSX menu “ghosted” as depicted in the screen shot below:Cycling of the view keys between the 2D and VC cockpit views did not clear the issue. Using ALT-ENTER to window FSX allowed me to regain control of the screen. I was able to return to full screen and continue flyingNOTE: When this same sequence was performed with ASE running and using live weather, the above screen shot rapidly "flashed" without any abilty to mouse a control. I was unable to regain control of the screen. I had to ALT-ENTER to window FSX and close the program. Issue 2: After regaining the 2D panel (sequencing to FSX windowed mode and back to full screen mode), the FSX menu exhibited the following behavior:Notice that the full dropdown menu is shown, only the item that mouse is currently over is shown.Issue 3:On approach into MRY, I noticed a gradual loss of terrain textures that increased the closer I came to runway. On short final, nearly all the terrain textures around the runway were lost, however, as you can see, the auto-gen objects remain:You can see that the terrain textures distant from the runway still appear. This is not weather, but rather a loss of textures.These issues will be reported as trouble ticket with PMDG. They are posted here for reference.Computer:i7 2600k 3.4 GHz (no overclocking), 8GB RAMGTX 460 - Current NVIDIA driver 275.33Win 7 64 bitAll NGX Introduction FSX.CFG addition/configurations complied with. Thoughts, ideas, suggestions for resolution are appreciated.Thanks!Rich BollWichita, KS.BTW....NICE RNP AR appraoch into MRY :)

Time for me to apologize. I re-checked my FSX.cfg file to make the correction from HIMEMFIX=1 to HIGHMEMFIX=1. At that time I noticed that TEXTURE_MAX_LOAD=1096 was still present. I thought (I swear!!!!) that I made all changes recommended by NGX Introduction document. After changing TEXTURE_MAX_LOAD=4096 and using the correct syntax for HIGHMEMFIX=1, all issues appear to be resolved.Sorry for the confusion!Rich Boll

Any time you make a change to your settings using the FSX interface, FSX changes TEXTURE_MAX_LOAD back to 1024. So, each time you change your settings in FSX, you have to manually edit your fsx,cfg file and change it back to 4096.