Hello friends I would like to know if you guys can help me.

 

win 7 64. Im using ENB and shade, all sliders maxed out except water at high, dx9, the tweaks are applied to the cfg file, LOD set to 6.5 and TML to 4096 although I have REX clouds at 2048.

I have a ton of addons, flying the NGX with FTX global severe weather I get frames in the 20s, however I get the OOM annoying error.

Paging file is set to system managed, no viruses or whatsoever.  

With my rig (click MY PC) I believe Im not supposed to have this type of stuff.

 

Also I get this weird texture looking from behind of the airplane in dusk or dawn only  http://flic.kr/p/fu6F1Q

 

Any thoughts? 

Lol.... Ya your LOD at 6.5 is a big factor... Maxed sliders is another. FTX and NGX... Ya unfortunately FSX is limited by its older architecture ... You need to balance sliders especially with NGX and Orbx addons.

Lol.... Ya your LOD at 6.5 is a big factor... Maxed sliders is another. FTX and NGX... Ya unfortunately FSX is limited by its older architecture ... You need to balance sliders especially with NGX and Orbx addons.

I will try reducing autogen a notch. I also noted that voxatc needs more than 1gb ram in the task mgr processes section which is a lot. Maybe cuz I have extra voice packs installed? Dunno

  Wow, seriously?  An OOM issue with FSX?  :rolleyes:  Search the forums,  OOMS are VERY common regardless of your PC specs.

You really gotta tone down the settings as Ryan mentions. LOD 5.5, use water low, there isnt that much difference. 1024 clouds, not much difference from higher res either. Saying you have a ton of addons just screams OOM as well. 

 

Look at it as FSX as a small car. You can only fit so many people in it no matter what addons you have for it. 

 

My other suggestion is to have a look at the DX10 thread as it will give you extra wiggle room. Easy to implement.

You really gotta tone down the settings as Ryan mentions. LOD 5.5, use water low, there isnt that much difference. 1024 clouds, not much difference from higher res either. Saying you have a ton of addons just screams OOM as well. 

 

Look at it as FSX as a small car. You can only fit so many people in it no matter what addons you have for it. 

 

My other suggestion is to have a look at the DX10 thread as it will give you extra wiggle room. Easy to implement.

 

Well I love ENB looks realistic to me and it doesnt work with Dx10. Also I like flying at night and most addon airports are not dx10 compatible so its not a choice to me.

I will lower the sliders and find some balance.

Noob question: If I get more RAM will it make fsx stable or I will get OOM errors no matter what? :ph34r:

 

thx

 

Small Car hope its not a Yugo or Ford Pinto Lolol

No.... adding more RAM has nothing to do with OOM.  OOM's are caused by FSXs' Virtual Address Space reaching the allotted 4GB limit.  This limit exists because FSX is a 32bit program.  It doens't matter if you run a 64bit OS (though it helps a little), or add more physical RAM.  4GB is the limit.  As you stack all those addons together, and jack up your LOD to 6.5 and max settings, your VAS will rapidly approach 4GB.  In addition to that, the higher the video card memory usually the faster you'll get OOM's.  I don't know exactly how the GPU vram affects FSX VAS saturation but I see a lot more users with 2GB-4GB video cards get OOM's.

 

I agree it is unfortunate now that we have monster rigs that could theoretically crush FSX we cannot use them to the full potential because FSX will OOM hehe.

 

You can check your usage with Process Explorer (excellent tool), freeware from here...:

http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

 

Also I've done a lot of testing (non scientific) with VAS and FSX and the things that affect VAS the most tend to be

 

1) LOD radius

2) Heavy textured (or many textured) addons

3) TML to 4096

4) Autogen

5) Clouds and added cloud entries above and beyond FSX's sliders

 

I recommend you create multiple cfg's for certain flying.  Just press options save config in game.

 

For example, when flying default scenery with lite addons I tend to use a cfg called LOD_6_5

 

It contains LOD 6.5 and basically max scenery except water at 2x low, and no AI

 

For Orbx flying with  heavy addons I load my LOD_4_5

 

It contains LOD 4.5 (max fsx stock slider setting) water 2x low no AI, and scenery one notch down.

 

 

Hello friends I would like to know if you guys can help me.

 

 

Search for DX10 here and switch to  DX10.

Post #6, although formatted weird (OP's message contained inside quoted part), explains that he doesn't care for DX10.  But ya I agree it would help a little.

DX10 can help but with all the still existing drawbacks I can imagine people not being too excited about it. 

DX9 can still be flown with high settings without OOM's as long as you're able to determine the right balance.

One thing I do wonder though about TML, what happens when an addon is equipped with 4096 textures, but TML is set to 1024 or 2048?

Reason I ask is because there seems to be a trend in upscaling of texture resolutions in addons and when multiple of those 4096 addons come together, OOM's are bound to occur...

 

 

Any thoughts? 

 

In case you haven't done the following yet:

 

 

1. Install FSUIPC.

 

http://www.schiratti.com/dowson.html

 

2. Put the UIAutomationCore.dll from this download into your main FSX folder (be sure to rename the file to UIAutomationCore.dll after downloading it).

 

https://dl.dropbox.c...in_fsx_root.dll

Use 4.5 LOD Radius and zoom out a notch or two to hide the blurries. Unfortunately we're getting to the point where even upgrading the hardware doesn't help us get around the inherit limitations of the old FSX any more.

In case you haven't done the following yet:

 

1. Install FSUIPC.

http://www.schiratti.com/dowson.html

2. Put the UIAutomationCore.dll from this download into your main FSX folder (be sure to rename the file to UIAutomationCore.dll after downloading it).

https://dl.dropbox.c...in_fsx_root.dll

Did it a long time ago. Thanks

 

 

Sent from my iPhone using Tapatalk 2

No.... adding more RAM has nothing to do with OOM. OOM's are caused by FSXs' Virtual Address Space reaching the allotted 4GB limit. This limit exists because FSX is a 32bit program. It doens't matter if you run a 64bit OS (though it helps a little), or add more physical RAM. 4GB is the limit. As you stack all those addons together, and jack up your LOD to 6.5 and max settings, your VAS will rapidly approach 4GB. In addition to that, the higher the video card memory usually the faster you'll get OOM's. I don't know exactly how the GPU vram affects FSX VAS saturation but I see a lot more users with 2GB-4GB video cards get OOM's.

 

I agree it is unfortunate now that we have monster rigs that could theoretically crush FSX we cannot use them to the full potential because FSX will OOM hehe.

 

You can check your usage with Process Explorer (excellent tool), freeware from here...:

http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

 

Also I've done a lot of testing (non scientific) with VAS and FSX and the things that affect VAS the most tend to be

 

1) LOD radius

2) Heavy textured (or many textured) addons

3) TML to 4096

4) Autogen

5) Clouds and added cloud entries above and beyond FSX's sliders

 

I recommend you create multiple cfg's for certain flying. Just press options save config in game.

 

For example, when flying default scenery with lite addons I tend to use a cfg called LOD_6_5

 

It contains LOD 6.5 and basically max scenery except water at 2x low, and no AI

 

For Orbx flying with heavy addons I load my LOD_4_5

 

It contains LOD 4.5 (max fsx stock slider setting) water 2x low no AI, and scenery one notch down.

Thanks a lot for this. Also I noticed that Im getting the OOM more frequently since I set the autogen slider at full. I havent tested how McPhat textures look with TML 2048, thats the reason I leave it at 4096.

 

 

Sent from my iPhone using Tapatalk 2

Also if not mentioned depending on where you fly turn the auto traffic way down or off (NYC, LA etc).