Your spec at the top said you have a 670 with 2gig ram, yet your config shows a 560Ti. Which is it?

Using DX9 your video memory will replicate into the system memory, effectively reducing your VAS even more. This doesn't happen with DX10, so you might look at that as onother option if you can't clear these OOM's.

 

If you have a 670:-

Move your proc up to 4.5 gig, your BufferPools to "0", drop your Texture_Max_Load to 1024, Airport_Scenery_Density to "1", and your LOD to 4.5.

 

If you only have a 560Ti:-

Move your proc up to 4.5 gig, your BufferPools to "1, with a RejectThreshold of 131072(to start with)", drop your Texture_Max_Load to 1024, Airport_Scenery_Density to "1", and your LOD to 4.5.

 

Last thing - the proc at 3.5 gig is your biggest bottleneck.

 

All the Best,

 

pj

It's not a CTD but out of memory so i can't see a error in event viewer

 

OOM errors should show up as well.

Running your LOD at 7.5 on 3.5gb CPU is asking far too much...

The simple and unsatisfactory solution is to set Global texture resolution down a notch to high in Settings - Display.

 

This will cause the textures of the PMDG 737 and OrbX England combined to remain below critical memory usage. You should be able to fly without crashes but obviously with reduced texture quality.

Hey guys, are you sure it is an OOM issue?

I have an absolute stable FsX (took me some time to figure that out).

However, the first time I flew to EGKK with ORBX ended in a Crash. It happened during descent.

It turned out it had something to do with an g3d.dll.

I tried a second flight into the ORBX-area and it crashed as well during descent and as well because of the g3d.dll issue.

Days before, I flew a lot around FTX England, and it never crashed. It only happened when I started in a different country, like germany, so the Add-on scenery (England) had to be loaded during the flight and not in the beginning.

Of course I looked the g3d.dll issue up, and subsequently installed the newest FSUIPC-Version available. I didn't try since, but you may do the same.

I as well thought that it maybe isn't a RAM problem but more an graphic-ram issue. But even with reduced settings it crashed. Again I want to point out, it never happened when I started and stayed in the England-Area.

 

Any thoughts on this?

 

Nik Reineke

It is with me Nik, running VMAPP I get to around 4k then I get the message. Sometimes I can just land and squeak to the gate around 3.9 but its touch and go.On VMAPP at starting gate at EGBB VMAPP shows around 3k, cruise around 3.2 and at EGKK 3.9-4.0. Is there any way to reset it without trying to restart FSX ? I have tried ALT/ENTER to switch windows but that has no effect and I am aware of the paid version of FSUIPC which allows you to save your flight.

Just checked event viewer again and nothing shows up.

Thanks Paul

Using DX9 your video memory will replicate into the system memory, effectively reducing your VAS even more. This doesn't happen with DX10, so you might look at that as onother option if you can't clear these OOM's.

 

Paul, could you elaborate on this please or point me towards additional information, as I've never heard this before. Certainly on a 32bit OS, your video memory effectively reduces the amount of RAM that can be addressed, but I've never heard of anything similar assuming a 64bit OS.

 

Thanks,

 

Scott

Hello

 

Try this site:

You may receive an "Out of Memory" error message because of the desktop heap limitation in Windows Vista or in Windows 7

 

Worked for me, hope it works for you too.

 

Cheers.

 

@Ramon,

 

to what value you changed the 3rd entry, 2048, 4096 or even more ?

Thank you !

The numbers for 64-bit Win7 and Vista need to be:-

 

SharedSection=1024,20480,1024, Chris.

Paul, could you elaborate on this please or point me towards additional information, as I've never heard this before. Certainly on a 32bit OS, your video memory effectively reduces the amount of RAM that can be addressed, but I've never heard of anything similar assuming a 64bit OS.

 

Thanks,

 

Scott

 

The easiedst place to start, Scott, is here , as it gives a short intro as to what DirectX3D is, and the changes made as each version was added. The lines of special interest are:-

 

"Direct3D 9Ex, in conjunction with DirectX 9 class WDDM drivers allows graphics memory to be virtualized and paged out to system memory, allows graphics operations to be interrupted and scheduled and allow DirectX surfaces to be shared across processes"..

In peeple-speak, it means that the system creates an area in the system memory, equivalent to the space being used in the GPU's memory - the more memory the gpu has - the less the system has.

DX10 does not do this, and you will see from continuing to read the page, that FSX is not the only game to be "retrofitted" for DX10.

"Examples of such titles are games originally written for Direct3D 9 and ported to Direct3D 10 after their release, such as Company of Heroes, or games originally developed for Direct3D 9 with a Direct3D 10 path retrofitted later in development, such as Hellgate: London or Crysis. "

 

There are lots of articles on the weeeb which offer good explanations of the differences and advances made since it was picked up by Microsoft.

 

.. and with this above in mind - consider: - our friend, Steve is "retrofitting" FSX..

 

All the Best,

 

pj

Thank you @Paul !

But this values were already set so I´ll stick with them.

Thank you @Paul !

But this values were already set so I´ll stick with them.

You mean these specific values: SharedSection=1024,20480,1024 are already set in the registry?

If so - that's good! If not - you should change them - or risk more OOM's!

 

All the Best,

Paul,

 

Thanks for the link.

 

I'm not sure I read this the same way you do, or perhaps I'm not understanding exactly what you meant. The ability to virtualize video memory and page to system memory doesn't suggest to me that you'll reduce the amount of memory available to a given application unless 1) you're exceeding the VRAM you have available so that you're forced to page and 2) you're short on system memory such that adding some paged video memory to the mix means you've don't have enough total RAM to support FSX' share, plus all the other stuff you've got running, plus the paged VRAM.

 

If you're having to page VRAM, you're already taking a pretty good performance hit anyway and if you have sufficient total RAM it shouldn't affect OOMs which for most of us (and assuming 64 bit Windows) are about 32 bit apps running out of addressable space, not total physical RAM.

 

And, again, I may be missing something, but I wasn't aware that DX10 didn't support paging to system memory in pretty much the same way.

 

BTW, I certainly don't claim to be an expert in these areas, but what you were saying didn't match my understanding of things which was why I asked for "further reading".

 

Thanks,

 

Scott

The OP is running a 670 with 2 gig of ram with a 3.5 gig proc and a single 500 gig drive - this system can't do anything fast enough to satisfy FSX!

 

He has the 737, AS2012, UK2000 and FTX England, plus lord-knows what else the system might be doing or running. If he was overclocked to 4.7 or 8, he probably would be ok, but assume his paging file on the hard drive, is system managed, is small, is fragmented, and on the OS drive - he's going to have a hard time not getting an OOM.

 

I also have OOM's when approaching EGKK. When I run Process Explorer I can see FSX is using the limit of 3,2 GB of VAS when I receive the OOM.

 

When I fly at 3000 feet the ORBX England scenery is very blurry now and all the buildings on the UK2000 airport are all white. Whats the reason for that?

 

It's pretty obvious he has minimal experience, because of his fsx settings, so all of these things are possible. If, If, If...

 

All the Best,

@Ramon,

to what value you changed the 3rd entry, 2048, 4096 or even more ?

Thank you !

 

Like Paul said, the values for your Windows 7 x64 should be SharedSection=1024,20480,1024

 

I didn't play with other values on the 3rd parameter. Those are sensitive values that control all windows subsystems and could mess up the system. (Best to create a restore point before fiddling with those values)

 

Or run the FixIt applet from that webpage, and let it do the changes.

 

Cheers.