Word Not Allowed have made this very good article. I finally understood the VAS problem.

 

http://#####.wordpress.com/fsx-oom-and-addon-vas-usage/

 

It would be so nice if the were a big cooperation in the community by developers and Microsoft to break the 4 GB VAS seal. :p0310:

 

Now FTX Global is the  :Love: fantastic lift for FSX. With to Individual textures... what a creativity we are going to see.

 

But the OOM  :t0103:  

 

London VFR, UK2000 Heathrow and a big plane that is  :p0128: for me impossible. I will try minimise everything but it sure would be nice if the seal could be broken.

 

 

Jens Michlas

CPH Denmark

Wouldn't it be nice, if that whatever they did in the SP to make it use more, they could just open it back up, and then replace a couple numbers to make it double? Lol.

 

 

Sent from my Apple communications device.

No.

 

Save from a rewrite to 64bit architecture (which I hear LM are very, very slowly trying to do), you cannot do much. All we have is "Large Memory Aware flag" that MS used I think with SP2? that gave the app a bit more memory in 64bit systems.

 

You cannot give it more though. It simply cannot be told there is more memory than 32bit adressing lets it.

It is kinda like you were only allowed to use N and E coordinates in your GPS. You know there is more world out there - but you have no way of telling your GPS to get you there.

The VAS seal?

 

 

Why would you want to break such an adorable creature?

 

Lol

 

 

Sent from my Apple communications device.

The VAS seal?

 

 

Why would you want to break such an adorable creature?

 

Cant we just use our 777's to carry the seal up to 8GB?  Surely someone can fly a 777 with a seal on it, especially with all that thrust 

I recently purchased FTX Global and Ultimate terrain both Europe and North America. I found a helpful site which told me about a 4GB patch for FSX, I cannot remember but just search 4GB patch FSX and your bound to find it. Any way I had a OOM error when trying to land in KLAX with FSDream team scenery. After the patch I never got an OOM error again. Just today I took off from UK2000 Heathrow with the PMDG 747 no issues there. So try the patch it will help. 

This is an automatic message.

 

This topic has been moved from "PMDG General Forum" to "MOBO, RAM, CPU's & Other Hardware". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Dane

4GB patch for FSX

 

This has already been set in FSX SP2 it is called the Large Address Aware Flag and it means that a 32-bit app in a 64-bit OS can access 4GB of Virtual Address Space (NOT virtual memory - which is actually the paging file).  It should not need setting again. I guess it could work if the FSX version fails when starting but that would be unusual.

 

The VAS is totally independent of the Physical RAM and Paging File.  The VAS is part of the operating system whereas the RAM is part of the hardware. They communicate only via the OS and the cpu, for example a 'page fault' [usually called 'hard page fault'] (see a lot of these in FSX in some stuttering) usually means that code has been loaded into the VAS but is not yet present in the RAM.

 

I agree the 4GB is now too small for FSX with all the complicated add-ons that may have their own VAS and can also interact with the FSX VAS.  This is a limitation of a 32-bit app and cannot be increased.

 

The major advance has been X-Plane 10.2 64-bit which can access up to 8 TERAbytes of VAS (the OS accesses another 8 TB) and so a OOM is unlikely even with hundreds of add-ons.

 

pH

Ironically, it was AMD that kind of put the kibosh on what FSX could be capable of.

 

Back in the dim past of Pentium processors, it was recognized that applications, databases in particular, could really use a boost past 4GB of memory. So Intel came up with the scheme called Physical Address Extensions that provided just that capability. It was kind of like a secondary page table that allowed an application to access additional memory, if only slightly indirectly.

 

But AMD, who had been hitting foul balls left and right but still staying in the game, came out with Opteron, the first native 64-bit processor. Changed everything overnight, not to mention shaking Intel to its core since Itanium was so poor at running legacy 32-bit apps.

 

Fun times...