This is getting to be a bigger and bigger problem especially with more high-fidelity addons coming out like A2A, RealAir, NGX, etc. Combined with scenery packages, MyTraffic X (traffic set at about 30-35%), and sceneries (i.e. Manhattan X, FSDT KJFK, KLAS and Las Vegas X, Flightbeam KSFO and San Francisco X), FSX is crashing with increasing frequency.

 

My machine is more than capable of handling FSX at high settings. I have a new i7 3rd gen with Radeon 7850. Additionally I have followed the tweaks recommended by Word Not Allowed. Nevertheless I am often teetering on the edge of 3GB of RAM (for FSX), and once it hits the 3.5GB limit in higher density areas like LAS or NYC, FSX will crash with an OOM error. I notice that once the memory starts to creep up, even turning the traffic way down or turning down the Autogen to sparse does not help.

 

The problem seems especially severe with night flying, probably due to night lighting. FYI I keep my Autogen usually on "Normal" but still encounter the OOM errors described above. Here are my other settings:

 

-Target Frame Rate: 30

-LOD: Large

-Mesh complexity: 100

-Mesh Resolution: 2m

-Texture Resolution: 15cm

-Water Effects: Low 2x

-Land Detail Textures: Checked

-Scenery Complexity: Extremely Dense

-Autogen Density: Normal

-Ground Scenery Shadows: Unchecked

-Special Effects Detail: High

-Cloud Draw Distance: minimum 60mi

-Cloud coverage density: Max

-Traffic: 35% airliner and GA, airport vehicle density low, road vehicles 20, ships and ferries and leisure boats 30

 

Using REX textures

And GEX

 

Here are the relevant portions of my FSX cfg file.

 

[bufferPools]
Usepools=0
[sOUND]
AmbientUI=0
AmbientUIMusicVolume=-6.000000
PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}
SOUND=1
SOUND_LOD=1
SOUND_QUALITY=2
UISound=1
VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}
[DISPLAY.Device.AMD Radeon HD 7800 Series.0]
Mode=1600x900x32
Anisotropic=1
[GRAPHICS]
AC_SELF_SHADOW=1
AIRCRAFT_REFLECTIONS=1
AIRCRAFT_SHADOWS=0
ALLOW_SHADER_30=1
COCKPIT_HIGH_LOD=1
EFFECTS_QUALITY=2
ForceFullScreenVSync=1
ForceWindowedVSync=1
GROUND_SHADOWS=0
HIGHMEMFIX=1
LANDING_LIGHTS=1
NUM_LIGHTS=8
AC_SELF_SHADOW=1
TEXTURE_MAX_LOAD=4096
TEXTURE_QUALITY=3
Text_Scroll=1
D3D10=0
SHADER_CACHE_PRIMED_10=1693500672
SHADER_CACHE_PRIMED=1693500672
IMAGE_QUALITY=0
See_Self=1
[TrafficManager]
AIRPORT_SCENERY_DENSITY=2
AirlineDensity=35
FreewayDensity=20
GADensity=35
IFROnly=0
LeisureBoatsDensity=30
ShipsAndFerriesDensity=30
[Weather]
AdjustForMagVarInDialog=1
CLOUD_COVERAGE_DENSITY=8
CLOUD_DRAW_DISTANCE=3
DETAILED_CLOUDS=1
DisableTurbulence=0
DownloadWindsAloft=0
DynamicWeather=0
MaxGustRampSpeed=200
MaxGustTime=500
MaxVarRampSpeed=75
MaxVarTime=50
MinGustRampSpeed=1
MinGustTime=10
MinVarRampSpeed=10
MinVarTime=5
THERMAL_VISUALS=0
TurbulenceScale=1.000000
WeatherGraphDataInDialog=0
WeatherServerAddress=fs2k.zone.com
WeatherServerPort=80
WindshieldPrecipitationEffects=1
[Misc]
Com_Rate=7
[Main]
HideMenuFullscreen=1
HideMenuNormal=0
Location=1,0,1600,900,\\.\DISPLAY1
Maximized=0
SimObjectPaths.0=SimObjects\Airplanes
SimObjectPaths.1=SimObjects\Rotorcraft
SimObjectPaths.2=SimObjects\GroundVehicles
SimObjectPaths.3=SimObjects\Boats
SimObjectPaths.4=SimObjects\Animals
SimObjectPaths.5=SimObjects\Misc
SimObjectPaths.6=MyTraffic\Aircraft
User Objects=Airplane, Helicopter
ProcSpeed=8495
PerfBucket=7
FIBER_FRAME_TIME_FRACTION=0.1
[sIM]
SYSCLOCK=1
[Display]
ActiveWindowTitleBackGroundColor=0,28,140,64
ActiveWindowTitleTextColor=255,255,255
BLOOM_EFFECTS=0
ChangeTime=4.000000
InfoBrakesEnable=True
InfoLowerLeftBackGroundColor=255,0,0,128
InfoLowerLeftTextColor=255,255,255
InfoLowerRightBackGroundColor=255,0,0,128
InfoLowerRightTextColor=255,255,255
InfoOverspeedEnable=True
InfoParkingBrakesEnable=True
InfoPauseEnable=True
InfoSlewEnable=True
InfoStallEnable=True
InfoUpperRightBackGroundColor=0,0,0,0
InfoUpperRightTextColor=255,0,0
NonActiveWindowTitleBackGroundColor=24,33,87,64
NonActiveWindowTitleTextColor=255,255,255
SKINNED_ANIMATIONS=1
TEXTURE_BANDWIDTH_MULT=40
UPPER_FRAMERATE_LIMIT=30
WideViewAspect=True
TransitionTime=4.000000
[JOBSCHEDULER]
AffinityMask=14
[PANELS]
IMAGE_QUALITY=1
PANEL_MASKING=1
PANEL_OPACITY=100
PANEL_STRETCHING=1
QUICKTIPS=1
UNITS_OF_MEASURE=0
DEFAULT_VIEW=1
[slewTextInfo.2]
FrameRate=1,1
LockedFrameRate=1,2
[TERRAIN]
AUTOGEN_DENSITY=3
DETAIL_TEXTURE=1
LOD_RADIUS=4.500000
MESH_COMPLEXITY=100
MESH_RESOLUTION=24
TEXTURE_RESOLUTION=28
WATER_EFFECTS=4
[sCENERY]
DAWN_DUSK_SMOOTHING=1
IMAGE_COMPLEXITY=5
LENSFLARE=0

 

 

Is there any way to allow FSX to use more memory than the 3.5 GB limit for the 32 bit applications or otherwise fix these issues? This is going to become an even bigger problem as computers get more powerful and newer addons come out like the NGX and high-def sceneries that use a lot of memory.

<br />My machine is more than capable of handling FSX at high settings.<br />

 

You cannot have high settings and not have a crash once in a while. It's as simple as that. Srjan Word Not Allowed does not have AI enabled and that allows him to have very high settings. Why do you want to have your settings maxed out? Why do you want to have 20% cars running in the background? That setting should be no higher than 10%. Cars kills FPS and is one of the biggest memory hogs for FSX. You'll hardly see the difference between 20% and 8%. GA density is a killer too as well as leisure boats and ships. I have those turned off and I have a very powerful system. If you're going to have them running none should be any higher than 10% and that's really a FPS killer too.. You scenery settings look good as well as weather. It's just the AI that appears out of whack (airline density is great! Don't go any higher). Which version of Windows 7 is installed? 32 or 64 bit? The 64 bit version handles memory much better. OOM's are not uncommon with 32 bit systems but very, very rare for 64 bit systems. In fact, a OOM with a 64 bit system might indicate overheating, wrong CPU voltages, or wrong memory frequency/timings/and voltages. I also strongly recommend setting your virtual memory (page file) to System Managed size. FSX is an old program and it seems to work much better than one who sets his own virtual memory size. FSX can see around 4GB and the rest of the resources are used for other Windows functions. Microsoft.net framework manages memory for FSX and FSX addons and FSX was developed with Microsoft.net v1. Unfortunately the developers did not remain hired long enough to modify FSX's programming. Perhaps Prepar3D programmers will be able to modify things in the future.

 

Best regards,

Jim

Hello Jim

 

I agree on most statements except the following.

 

FSX just like Windows 7, Vista, or any prior version of Windows is written in the C language as well as native C++, and some assembly for extreme performance.

 

Dot Net is a modern Microsoft creation supposed to allow programmers to create applications faster, with little coding. It’s a middlemen between the programmer’s application and the core Windows components.

 

It could take 12 months just to create a complex UI, coding it in native C++.

 

With Dot NET, you drag and drop buttons and labels to a form without writing any code. Microsoft does that for you.

 

The only catch is that for your Dot NET program to run, it needs to be translated at run time (using the .Net runtime library)

 

You pay a price in terms of performance, that’s why serious games are very rarely if ever written in dot Net.

 

The Dot NET framework does manage memory, but only for programs written in Dot net. FSX is not one of them, nor is any previous simulator version.

 

Dot Net has its uses though. There are many programs that don’t need to refresh the screen at least 30 times per second.

@drnex: You have a great machine, and I am also going to disagree with Jim in a couple of places

Your config is pretty much where mine is, except that your TML is probably the straw that's breaking the Camel's back.

 

 

TEXTURE_MAX_LOAD=4096 Drop this one to 1024 or 2048. I think this is a "must do" until you figure out the OOM issue, which I'll get to, lower down.

 

Secondly - yes - your traffic is high, but mine is higher and it's fluid everywhere. This is my [TrafficManager]

 

[TrafficManager]

AIRPORT_SCENERY_DENSITY=2

AirlineDensity=51

ChangeTime=4.000000

FreewayDensity=28

GADensity=39

IFROnly=0

LeisureBoatsDensity=10

ShipsAndFerriesDensity=10

TransitionTime=4.000000

 

Here are a couple that can be modified:

 

CLOUD_COVERAGE_DENSITY=8 Cut to 6

 

FIBER_FRAME_TIME_FRACTION=0.1 GREAT!!! Leave it alone!!

 

TEXTURE_BANDWIDTH_MULT=40 Bring this to 120 in [Display]

 

TextureMaxLoad=12 ..... and add this line to [Display]

 

WATER_EFFECTS=4 Make this 6 to prevent artifacting when used wuth BufferPools=0

 

That's all for the cfg. It looks ok, and if your pc is popping 4.8 - 5.0 GHz you will have a really great experience.

 

The OOM is a different matter, and in your case - if the proc is only doing 3.9 GHz I would recommend upping it's speed from that 3.9 to at least 4.6 GHz or higher, and done in 3 or 4 steps over a few days. At 3.9GHz you are asking the machine to perform better than it can.

Secondly, I'm going to go 50-50 with Jim on this, as he's a proponent of system-managed swap-space and I am most definitely not. So let's do it Jim's way first, by rebuilding the system managed paging file, so that we know for sure - it's not the problem. Rt-Clk on "MyComputer" --> Properties -->Advanced --> Performance -->Settings, and uncheck the "Automatically manage paging file for all drives", and check the Custom size option, and making the sizes equal "100" in each min/max box. Press set, and restart the computer. When she's up again, go to the same Virtual Memory settings page and this time put a check back in the "Automatically manage paging file for all drives", and another check in "System Managed size., followed by "set" and another restart. She will now rebuild a brand new paging file on the C:. It will appear slow initially as this happens, but within a very short time it will be much faster.

 

If you have problems doing this, post back here, or pm me and I will walk you through it, either by phone, or TeamViewer. Good luck.

Thanks everyone. I will try these tips and get back to you all.

 

BTW my processor is not OC because I don't have the k model (regular 3770, not 3770k - stupid stupid stupid!). At 3.9 it works reasonably well. My frames tend to be quite good. Even at KJFK with complex HD plane, traffic, Manhattan X, FSDT KJFK, ImagineSim KLGA, I get 20-30 FPS. Everywhere else is locked at 30 for the most part. Would be nice to go higher but that's just not an option ATM. With my next upgrade in a couple years I will make sure to get an unlocked processor.

 

I wish MSFT brought back Aces and came out with FSXI and 64 bit support and backwards compatibility for all FSX addons. Oh well, a boy can dream.

The Dot NET framework does manage memory, but only for programs written in Dot net. FSX is not one of them, nor is any previous simulator version.

 

I disagree with your info/statement. FSX uses the first two versions of dotnet. Acceleration too. Here's a post and a statement from a Microsoft MVP.... http://www.fsdeveloper.com/forum/showthread.php?t=106298.

 

Best regards,

Jim

Framework 2 is used in constructing the SimConnect Client, and is probably used in other areas of the FSX code too.

hi ,

 

First th issue

of your problem

it's very simple

 

click right on M.S.Flight Simulator X and give all right in property compatibility and USER PC USER modify on control total

 

and finish your prob and crashs

and also

Menu START COMPUTEUR right click property give ALL RIGHT admin

 

that all

 

all addon instal finaly are best and good

 

best regards

 

Neptune

sorry for my english

Note that fsx is a native app, not a managed app; it does not use the .net framework. There is a managed interface to simconnect, which does require the .net framework, but that's it.

How can you say that cfops? DotNet v1 is installed when you first install FSX. Unbelievable! I agree with the native app description but FSX was developed with the first version of dotnet framework.

Let's say that I have some experience with it.

 

Regardless, I will bow to your deeper understanding and return whence I came.

 

My sincereset apologies for any disruption I may have caused.

I like to run heavy eye candy too and am running out of memory constantly. Very frustrating to have all these addons but can't run them in full monty due to FSX limitations.

Yeah I have started to get these too likely as a combination of many heavy addons and OpusFSX weather, I think I will turn my settings down a bit.

Lots of good advice from guys who have far more experience than myself, but I will throw two things into the thread from my own personal experience, which each affect OOM issues. The first running a 32bit OS, unsure whether this is relevent to yourself, but I'll mention it anyway, if you are running Windows XP or 7 as a 32 bit OS then OOM erros are almost inevitable I'm afraid. The second one relates to your GPU, which I see is 2Mb card. There have been many posts which suggest the extra memory on the GPU, above 1.2/1.5Mb actually reduces the available virtual address space and so results in OOM errors. Perhaps someone else can expand on this...

Myself I'm running Win 7 64 bit, I7 2600k locked at 4.4ghz,, 8GB RAM and Radeon 6990 with 4GB of Memory and still I have recently started to get these out of memory errors when flying around Europe with OpusFSX + AI + FS Altitude Western Europe + QW 757.

 

I don't know if there's a single addon to plane, I have recently started to use all UTX Europe, OpusFSX and FS Altitude with these flights... But these happened when I was also running almost max autogen, maybe reducing it to normal helps.