August 2, 201411 yr   Well I simply changed the FSX Compatibility to: Windows Server 2008 SP1, seems to be working lol,I tried everyytthing. Disabling scenery entries didnt work as much as Id hope to. Can actually fly at night with Night Environment UK and normally within 10 MINS OOM but so good so far....try it out and no guarantee it will work for you, diff setups may have differing results, could even be a placebo, but at least I dont hear the ding(as of yet)....please try and report back if it did/did not work for ya. MSI Codex 5 10SC-262UK Desktop PC - Intel Core i7-10700, RTX 2060 Graphics, 16GB RAM, 2TB HDD, 256GB SSD.
January 18, 201511 yr Well I simply changed the FSX Compatibility to: Windows Server 2008 SP1 Â (1) Is this solution continuing to work for OOM? Â (2) Do you use DX10? Â (3) If you have the NGX, did you have OOM issues with it? Michael Cubine
January 18, 201511 yr what OS are you using? do you have ai traffic? did you disable the scenery that you are not gonna fly in? is your OS a 64 or 32bit? how many ram does your PC have? is your FSX set to DX9 or DX10? are you always changing views or accessing menus while inflight? Richard Avenido
January 18, 201511 yr Ok... I don't think most people understand what causes OOM (Out Of Memory) problems in FSX. Changing the compatability feature, will (or atleast should) not affect how much memory a 32-bit program can access. A 32-Bit program (Which FSX is), you can access 4GB/4096MB of memory. There is nothing that can be done to raise this cap of 4GB of VAS unless you convert FSX to a 64-bit program.  I'd love a post with either a dump or a screenshot from process explorer showing that either, the initial VAS usage of FSX is lower when using Server 2008 compatability, or a screenshot showing FSX using more then 4GB of VAS and not crashing then by all means! Let's all go for it, but I highly suspect that you've done something else, that is causing it not to crash or that it is random.  Use this link for a guide on how to use and download process exploerer: http://support.precisionmanuals.com/kb/a108/vas-management-stopping-out-of-memory-oom-errors.aspx. Regards, Karl Mathias Moberg
January 18, 201511 yr Okay, I tried it twice and Windows 8 Server compaitiblity was significantly worse on my DX9 FSX.  Seemed like it was allocating larger chunks of memory and I ran out of VAS much quicker. Just for grins, I tried Windows XP SP3 mode and, while not as bad, it was worse as well. Gregg Seipp "A good landing is when you can walk away from the airplane. A great landing is when you can reuse it." i9 64GB RAM, GTX-5090
January 18, 201511 yr Author (1) Is this solution continuing to work for OOM?  (2) Do you use DX10?  (3) If you have the NGX, did you have OOM issues with it?  1)Currently yes  2) I fly the 777 what OS are you using? do you have ai traffic? did you disable the scenery that you are not gonna fly in? is your OS a 64 or 32bit? how many ram does your PC have? is your FSX set to DX9 or DX10? are you always changing views or accessing menus while inflight? Win 7 64 bit. 100% Custom ai, im an ai nut. Yes I disable scenery areas like VFR London, KJFK but not all scenery areas. 12GB ram but with VAS that doesn't matter. Im using DX10. Im always changing views in flight.  I'm also using Nvidia DSR which enables me to leave the TextureMaxLoad to 1048 and suffer no loss in quality. MSI Codex 5 10SC-262UK Desktop PC - Intel Core i7-10700, RTX 2060 Graphics, 16GB RAM, 2TB HDD, 256GB SSD.
January 18, 201511 yr   100% Custom ai, im an ai nut. Yes I disable scenery areas like VFR London, KJFK but not all scenery areas. Im always changing views in flight.   what ai addon do you use? is it WOAI, UT2, MT 2013? make sure you limit the ai settings to 30% ( depends on what other addons are running)  limit the view change cause its one of the top reasons why FSX crash ( even the DX10 is enabled ) Richard Avenido
Create an account or sign in to comment