Jump to content

Welcome to OZx Forum

Welcome to OZx Forum guest,

Wouldn't it be nice if I would call you by your name or nickname of your choice ? 

Like most online communities you must register to post in our community, but don't worry this is a simple free process that requires minimal information for you to signup. Be apart of OZx Forum by signing in or creating an account.

  • Start new topics and reply to others
  • Subscribe to topics and forums to get email updates
  • Get your own profile page and make new friends
  • Send personal messages to other members.

Sign in to follow this  

Did you know

Recommended Posts

that even though you are running FSX on a Windows 64bit system,you are truely running it as 32-bit program with 32-bit memory restrictions.

So even guys with 24GB of memory FSX will only use 3.5GB or so. These are 32-bit limitations.WOW,eye opener......Computer GURU's confirm or deny this simation.....

Edited by JohnM

Share this post

Link to post
Share on other sites

Actually, it is only 3Gb of address space that FSX gets allocated - if I understand the tech reading about it:

>> http://blogs.msdn.com/b/ptaylor/archive/2007/06/15/fsx-and-win32-process-address-space.aspx <<

But, a 64Bit OS has access to a much larger Virtual Address Space than a 32Bit OS does (I think [scratches head]). So that (sort-of) explains why, with a 64Bit OS you don't get the dreaded "OOM" errors. FSX still only uses 3Gb but can get allocated a contiguous section of mem space.

I was getting the "OOM" on my 32Bit Win7 using areas such as FTX Canberra. Switched to a 64Bit Win7 and no more "OOM"s ... (so far)

Did that help John?

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this