Hi

 

As running on Win7 x64 was staggered to see this error message!

 

Not surprised in that for a bit of fun maxed out all the Scenery sliders as well as the autogen then, tried to go to Manhattan X for a bit of sightseeing. At least now I know what happens with that "dream" configuration!

 

Task Manager quoted just over 3Gb of memory being used. Total physical memory is just 8Gb with a swap file of half that. Have always wanted an excuse to justify upgrading to 16Gb, is this it?

 

Does anyone else's Prepar3D consumer over 3Gb or more??!! Does anyone find any benefit of running in 16Gb?

This is normal if you are using very large LOD radius' or if you run very high settings.

Hi

 

As running on Win7 x64 was staggered to see this error message!

 

Not surprised in that for a bit of fun maxed out all the Scenery sliders as well as the autogen then, tried to go to Manhattan X for a bit of sightseeing. At least now I know what happens with that "dream" configuration!

 

Task Manager quoted just over 3Gb of memory being used. Total physical memory is just 8Gb with a swap file of half that. Have always wanted an excuse to justify upgrading to 16Gb, is this it?

 

Does anyone else's Prepar3D consumer over 3Gb or more??!! Does anyone find any benefit of running in 16Gb?

The problem lies not in amount of total system memory, but rather in amount of memory 32 bit applications are able to address (at the moment it is either 2 GB or 3 GB for large address aware applications). So adding system memory won't resolve this problem at all.

 

The only solution now, is to set LOD_RADIUS and texture resolution settings to some lower values (also reducing autogen and scenery settings will also help, although to lesser extent). Also, you can try to set large address aware executable flag using some binary editing tools for Prepar3d.exe file (but I think in your case it was already set).

Will highmemfix help?

 

Sent from my HTC One X using Tapatalk 2

You shouldn't need any cfg file `tweaking' for prepar3D and there isn't any concrete proof (That I've seen) any FSX cfg tweaks even work with Prepar3D. P3D is already Large Address Aware.. Turn your LOD down to 4.5 if you had it to 6.5 and try using that.

Hi, I am running P3d with 16 Gb RAM and have no issues with memory running out, I use the i7 2600k and an Asus HD 6950 with 1 Gb. Most settings are max with exception to Autogen and associated settings turned off as I am running Photo-realistic scenery. I do use 64 bit Windows 7 which will make a difference over the 32 bit restrictions already mentioned.

Hi, I am running P3d with 16 Gb RAM and have no issues with memory running out, I use the i7 2600k and an Asus HD 6950 with 1 Gb. Most settings are max with exception to Autogen and associated settings turned off as I am running Photo-realistic scenery. I do use 64 bit Windows 7 which will make a difference over the 32 bit restrictions already mentioned.

It makes a difference for running Windows to have the 64bit versions, it handles memory hungry applications better and is more stable because of this, but still FSX and P3D are 32bit applications with the mentioned limit of memory they can address.

This will only change if and when LM will make P3D a 64bit application.

Ost, may I ask what GPU and size are you using?

It makes a difference for running Windows to have the 64bit versions, it handles memory hungry applications better and is more stable because of this, but still FSX and P3D are 32bit applications with the mentioned limit of memory they can address.

This will only change if and when LM will make P3D a 64bit application.

 

Eric,

 

I agree with what you say regarding Windows usage, however LM do quote and recommend using 'Windows 7 64 bit and at least 4 Gb or more' over 32 bit which they quote as only using 2 Gb, therefore it must make a difference.

For those wishing to see the full recommendations for P3D here is the link, the table is at the bottom of the web page.

 

http://www.prepar3d.com/product-overview/

Thanks everyone for the contributions.

 

Note I was not surprised to find the son of FSX choke on Manhattan X with every slider at max. What did surprise was that the Prepar3D memory management choked when everything was thrown at it on a 64bit system. Having run in 64bit since XP x64 I was surprised to see in 2012 an app actually choke for a lack of memory; then again FSX/Prepar3D are not very modern at heart. Frankly though was also pleased as I was looking for limits and I found one.

 

The spec is an Asus overclocked GTX580P GPU with just 1.5Gb of GDDR.

Eric,

 

I agree with what you say regarding Windows usage, however LM do quote and recommend using 'Windows 7 64 bit and at least 4 Gb or more' over 32 bit which they quote as only using 2 Gb, therefore it must make a difference.

Foxy,

So we agree that according to LM it is best have more than 4Gb memory, I have 8Gb and P3D runs well.

I think that having 16Gb in your system does not make a difference (compared to 8GB) for P3D, as it is still a 32bit application that cannot address more than 3Gb om memory.

As running on Win7 x64 was staggered to see this error message!

 

Prepar3D is 32 bits application running in your case in 64 bits system. That error you got means P3D used all memory allowed to use for it as 32 bits application - 4GB. As P3D is complied with LARGE_ADDRESS_AWARE flag it may use up to 4GB of virtual adress space.

You saw in Task Manager that used memory was around 3 GB. Task Manager doesn't show size of used virtual adress space but only allocated physical memory. Applications under normal circumstances always are using more virtual adress space than physical.

To check how much of virtual adress space is using FSX in your case, you need to get Process Explorer, ( http://technet.microsoft.com/en-us/sysinternals/bb896653 ) run it and right click on the "Process" table header > Select Colums > Process Memory Tab > and mark "Virtual Size"

than run P3D with the same plane and scenery as eailer.

 

Memory and Address Space Limits:

32 bits process on 32-bits Windows OS:

2 GB or up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT

 

32 bits process on 64-bits Windows OS:

2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default), 4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set

source: http://msdn.microsoft.com/en-us/library/aa366778%28v=vs.85%29.aspx#physical_memory_limits_windows_7

 

PS. you won't get any benefits from adding more memory over 8 GB you have now.

Thanks ad_verbum for this and the tip on checking with a process explorer; will do.

Hi

 

As running on Win7 x64 was staggered to see this error message!

 

Not surprised in that for a bit of fun maxed out all the Scenery sliders as well as the autogen then, tried to go to Manhattan X for a bit of sightseeing. At least now I know what happens with that "dream" configuration!

 

Task Manager quoted just over 3Gb of memory being used. Total physical memory is just 8Gb with a swap file of half that. Have always wanted an excuse to justify upgrading to 16Gb, is this it?

 

Does anyone else's Prepar3D consumer over 3Gb or more??!! Does anyone find any benefit of running in 16Gb?

I have the same in FSX.