Hi Flight Simmers!

 

I just got the PMDG 737-800/900 because everybody says it is a really good jet. But I have a problem that REALLY bugs me. The problem is that I can only use the plane for about 2 or 3 minutes until it enters skeleton mode and gives me a OOM message. Sometimes the plane enters skeleton mode before I even start a flight (still in the Free Flight screen).

My settings are:

---------------------

Graphics: Custom

 

Aircraft: Medium High

 

Scenery: Very Low

 

Weather: Very Low

 

Traffic: Custom

------------------------

 

In my Graphics I set the display resolution to 1280x800 and set the Global Texture Resolution to High (otherwise can't read the letters in the VC). In Traffic I put General Aviation and Airline Traffic to 10%, and I put Road Vehicles and Leisure Boats to 15%. Ships and Ferries is at 5%.

 

 

My system is a Mid-2010 Apple MacBook (polycarbonite/white) with 8GB of RAM, a 2.4GHz Intel Core 2 Duo processor, and a 256GB Hitachi hard drive. I'm using BootCamp to play FSX. BootCamp has a 64-bit Windows 7 installed on it.

 

What can I do? Can I fix my problem or am I screwed over?

Get a modern Gaming PC ? (Not a Mac)

 

You can use your Mac Laptop to surf the web, as you fly, of Tweet, Facebook, email -- whatever.

...(polycarbonite/white)...

There is your problem right there. The white Macbooks are crap at playing FSX... Black ones are much better

 

Sorry, I couldn't resist. Start with the basics. Have you made the configuration adjustments as recommended in the introduction to the 737?

Also, It doesn't matter one bit if you have 8 Gigs of RAM or 16 Gigs of RAM. FSX is a 32-bit program, meaning the most it will use is 4 Gigs of RAM max. If you have a lot of excess apps running, along with the operatng system, all of that is going to take a slice out of the 4 Gigs being used.

Also, It doesn't matter one bit if you have 8 Gigs of RAM or 16 Gigs of RAM. FSX is a 32-bit program, meaning the most it will use is 4 Gigs of RAM max. If you have a lot of excess apps running, along with the operatng system, all of that is going to take a slice out of the 4 Gigs being used.

 

Not exactly a 32bit app can allocate 4GB Virtual Address Space, it's not a physical memory limitation. Even with a 2GB system you would still be able to run FSX provided you didn't exceed the 4GB VAS limit. This is what Paging memory (Or what's called Virtual Memory is for). So it's not how much memory is installed, but how much available address space of the 4GB allocated is available. Also remember the space must be contiguous. So say the APP (FSX in this case) needs to use 60MB of 150MB VAS available, of that the largest contiguous space available is only 50GB. This will result with a OOM error or other CTD. So with the large amount of VAS the NGX requires (Due to it's detail, both graphically and it's systems) it is important up front to keep as much VAS available right up front. The best way to do this is to prevent the upfront DLL's that are needed for addons like CS, Wilco, other PMDG aircraft, and any other addon that you won't need for your session from loading on FSX startup. (These are the ones defined in the DLL.xml file) The way I do that is add or modify the line

 

<ManualLoad>True</ManualLoad>

 

to each addon section in the dll.xml file that I want to load selectively. This will cause FSX to ask if I want to load the addons dll into FSX o startup. I answer no to all except for the addons I am using during that session. In the case of the NGX that would be the PMDG HUD Interface. It's a little more inconvenient, but since I've been doing this I haven't had a OOM error since, and FSX runs smoother, and this is on a 32bit Vista system, which has even greater limitations then a a 64 bit Window 7 system.

highmemfix=1

...Also remember the space must be contiguous...

Eh... no, sorry, but it doesn't.

 

Thats why they call it virtual.

 

An arbiturary amount of contiguous 'virtual' memory is mapped to what ever physical memory happens to be available.

It is coming from the VAS. That's normal.

Try to delete your fsx.cfg and let FSX build it again. THere is one of your addon that is leaking memory and maybe your .cfg

(you may have to install some addon in order to get them in fsx.cfg or add manually dll) Please try it.

 

All the workaround will be in vain there is no way for FSX to use more than 3.2-3.4GB of RAM even with Windows 7 64Bits

FSX is a 32 bits application and the 737 from PMDG is using almost 700-900MB but it is not eating all your VAS... Something is bad with your config. I had the same problem I got rid of it by install a new a french FSX in another DISK which is not use by WINDOWS

I also added step by step my addon ... not all in the same time.

Watch out for the BIG BIG SCENERIES (photosceneries they are eating memory too)

 

Get rid of the traffic road put 0%... You don't care about traffic unless you want to make VFR

Put maximum 20% of aircraft traffic using MyTraffic

Put maximum 50% with defaut Ai

 

For my part, MyTrafficX need more ressource than UT2.

 

Good luck

Eh... no, sorry, but it doesn't.

 

Thats why they call it virtual.

 

An arbiturary amount of contiguous 'virtual' memory is mapped to what ever physical memory happens to be available.

 

Address Space Fragmentation

 

"Another concern with memory allocation is that if you allocate memory in non-contiguous blocks, over time "holes" will develop. For example, if you allocate 10 KB and it is taken from the middle of a 20 MB chunk of memory, then you can no longer allocate that 20 MB a one chunk of memory. Doing this enough times will cause you to no longer be able to allocate 20 MB at once. This can cause allocation failures even when there is free memory. Note that this is true even with virtual memory because what matters is that you need a continuous block of addresses, not a continuous block of physical memory."

 

http://www.cprogramm..._and_heaps.html

[bufferPools]

PoolSize=50000000

Hayhay go here and get your fsx config tweaked and go from there. it might just be a couple adjustments that need to be made

 

http://www.venetubo.com/fsx.html

Address Space Fragmentation

 

"Another concern with memory allocation is that if you allocate memory in non-contiguous blocks, over time "holes" will develop. For example, if you allocate 10 KB and it is taken from the middle of a 20 MB chunk of memory, then you can no longer allocate that 20 MB a one chunk of memory. Doing this enough times will cause you to no longer be able to allocate 20 MB at once. This can cause allocation failures even when there is free memory. Note that this is true even with virtual memory because what matters is that you need a continuous block of addresses, not a continuous block of physical memory."

 

http://www.cprogramm..._and_heaps.html

 

+1

Hayhay go here and get your fsx config tweaked and go from there. it might just be a couple adjustments that need to be made

 

http://www.venetubo.com/fsx.html

 

Venotubo is a misleading junk link. I passed my fsx.cfg thru his site and thought I really was accomplishing something with an average FPS of 23. Then I checked out the various tweak threads posted by NickN and achieved in excess 38 FPS.

 

 

Buy a PC

Kill all the traffic settings