Storm

Okay, just ran the same route once more ILM-FLL but this time I made two changes, I completely deleted the original dimmer cab file and dropped the new one in the proper locations, then I also disabled the Miami scenery which is a large plot of 3d and photo scenery to the south (in hopes of reducing the VAS footprint). I made it into FLL and parked, shut the engines down with no issues. I will say, whatever the issue is with the VAS usage (related to the dimmer cab and/or whatever else may/or may not be causing it), there are clearly some sceneries which we know are not VAS friendly. Managing the unused scenery as well certainly helps.

Yes, I did so before making the second set of test runs. There was an improvement but just after landing is when the OOM occurred,

I am having VAS OOM's as well. I don't have access to V 1.4 yet as I bought my L35 from Flightsim.com Pilot Shop. I ran a number of tests and like other users who have reported this issue, I can confirm that on most short range flights, there is no issue, evne with high end scenery in place for both airports. I did discover that most types of high end 3D ground lighting will eat up a good bit of VAS as well and depending on the aircraft model, OOM's are likely to occur. As a side note, I am able to use the MU-2 and C441 with night lighting and high level scenery without OOM's. Back to the Learjet, I did download and install the latest dimmer cab file and ran a day flight from ILM to FLL (with FLL being the high end FS Dream Team version). Using the FSX Scenery Configurator to disable all 3D ground lights and scenery not used. I had strictly a freeware version of ILM and FLL with Drzewiecki design's Miami scenery enabled. I was able to complete the flight to landing but during the rollout, an OOM happened. It's important to note that this was done during the day with no useage of the onboard aircraft lights other than the landing & taxi lights. On another test, I enabled various freeware photoreal Caribbean scenery and ran a flight from ILM to Barbados and other Islands. No OOM's occured but most of the flight was over open ocean. Regarding other high end models with high end scenery, again using the FSX Scenery Configurator, I was able to run the ILM to FLL flight (including the Drzewiecki design's Miami scenery) with my Aerosoft A319 and PMDG 737NGX without OOM's.

I agree, your listed settings are very close to my own and they certainly help go a long way to help prevent OOM issues.

Okay, I have fresh off the sim information to pass along. I rolled back my 737NGX to SP1C and ran the same routes twice with my original scenery settings as when I encountered the OOM's with SP1D. The first time all went well and I was able to complete the flight to landing and taxi to the gate without a CTD. However, I did hear several audible OOM warning bell sounds in the background but I continued to the gate and shutdown. After reaching the gate, I paused to check the status of the OOM error and oddly enough, there was no error message placard on the screen. I shut down both the flight and FSX normally with no issues. Frame rates remained normal as did all functions of the systems off the model. On the previous OOM's with SP1D, the warning sounds began a good 25 nautical miles away from the airport and continued until I was established on the ILS when I began seeing graphics problems as well as the loss of the PFD's and other displays on thy panel(followed by the CTD and OOM warning message on screen). Post flight I recalled reading about people having OOM's with FSX (and many other programs) and saw this fix for 32bit program usage w7x54 listed on one FSX related page: http://support.microsoft.com/kb/947246 Some here may argue the relevance of using that automatic registry fix and I won't argue but after I tried it. I am now getting the 737NGX(SP1C) all the way through the same route with no OOM error or audible warning and also of note, the frame rates for whatever reason are noticeably smoother now. Be it as it may, I agree some users are certainly having an issue with SP1D while many users may not be but from a wealth of experience on such matters which many of us have, there may be a mix of causes from one user PC from another which are causing OOM's and other glitches. I'd still urge investigating things further to see if the culprit(s) can be found and alleviated. I am going to continue testing in a number of sceneries and settings to see if there's any more occurrances or issues regarding this matter. BTW, I saved the P-8A folder and placed it back in FSX and it works fine with SP1C.

Okay, the issue persists regardless of lowering the scenery settings as well as disabling/removing some scenery. Luckily I kept my original installer and am going to roll back to that one and continue running a series of tests an keep notes while trying to isolate the issue based on what's installed or not. Will report back in a day or two.

To be clear, prior to installing SP1D, I had flown the NGX on a good number of long routes with scenery settings almost maxed out (and most of those routes included HD type scenery) and not a single OOM has ever occurred. I'm going to perform some more testing with different distances and scenery density level settings and see if there are any correlations/repeat OOM issues and report back.

Thanks for the replies, now I feel a bit better in thinking there's an issue. Anyhow, FYI, I did lower my scenery settings as A cross-check and it seemed to help a little but the OOM still occurred on final approach but the key difference between the different scenery level settings was that with the higher settings I would suffer OOM well before the final approach but with the settings turned down, I could actually land and the OOM would CTD the sim as I began to taxi. Driver170 & Admins, my mistake/appologies posting this issue here as I wasn't aware there was a separate CTD forum section. Admins, if possible would you move/merge this post to the appropriate area?

Hello, this is my first support post regarding the 737NGX since I have had it since Nov of 2013, Thus far, I have had zero issues with the model and no Out Of Memory Errors until after I installed SP1D. I am at a loss as to what is going on but I can say that the issue is occuring at the end of flights between KCLT to KMIA (as well as the same trip back to KCLT) and that there is both an audible and visual warning from windows when the OOM occurs. My KCLT scenery is freeware but my KMIA/Miami area is Miami City 2012 X. Drzewiecki Design. Knowing that the latter scenery is considerably large and takes a good bit of VAS, I have tested the NGX, MD-11, and Aerosoft A319 on the same and similar distance routes and and around Miami with no OOM issues. This issue so far as I can tell is specific to the NGX post SP1D Just to clarify, my LOD_Radius and Texture Max Load settings are totally stock, no modifications. My systems specs are as follows: Intel i7-3770 @ 3.40Ghz 16gb RAM W7-64 GPU - Radeon HD7770 2gb Again, others may not be experiencing what I am but I am just curious if anyone might be seeing this with the current update? BTW, everything works systems wise and runs smoother than the previous version. Regards,