Will FSX Acceleration run well in 64 bit? Better than 32bit? If it will, then can I leave it installed in 32 bit while I try it out in 64 bit..

Thanks,

Ralph

FSX is coded in 32-bit, which means that running it on a 64-bit operating system won't give you much advantage. But it does work fine in a 64-bit system.

Will FSX Acceleration run well in 64 bit?

 

No problem!

In fact, PMDG recommends a 64bit operating system for it's NGX.

 

"PMDG *highly* recommends the use of 64-bit versions of Windows due to memory limitations in FSX."

FSX will run better on a 64 bit OS rather than a 32 bit OS if you have more than 4GB of RAM in your machine.

 

32 bit only allows 4GB of memory to be used (2 to the 32nd power = 4,294,967,295). That maximum has to take in to account the OS overhead and any other processes running in the background as well. So that only leaves about 2.5 to 3GB of RAM that FSX can really use. Even if you had 8GB of RAM, you wouldn't be using it all with a 32 bit OS.

 

A 64 bit OS however allows 2 to the 64th power of memory to be used, or 18,446,744,073,709,551,616 bits ... which is a lot of GB's!! This is the OS you'd want if you had more than 4GB of RAM in a system. This way the OS can take some memory, background apps etc, and still leave FSX able to consume a good chunk of 4GB. So you can see that the NGX would prefer 64 bit OS's - it's a complex aircraft and it will become problematic if FSX only has 3GB or less to "play" with - resulting in CTD (crash to desktop) and OOM (out of memory) errors).

 

So, if you have 4GB or less of RAM, a 64 bit OS won't help at all. If you have more (6GB, 8GB, 12GB etc) a 64 bit OS will.

 

The only other thing to keep in mind with FSX though is that even if you do move to 64bit OS with 8GB of RAM for an example, you'd still want to keep "active" background processes to a minimum. Anything that consumes clock cycles is FSX's enemy. Such is the layered complexity of finding the sweet spot for FSX to run the way you're happy with

 

Cheers,

Danny

Thanks every one. I would like to leave the program on 32bit until I get every thing worked out for 62 bit. Any problems with that?

Hello

What OS are you running it in at the moment ?

Every thing is good in my 64bit except I run out of memory quite often now. Particularly where I have too many airport addons and city addons.

 

My win 32but with that memory switch rarely gave me out of memory.

 

So I am genuinly puzzled

As been said FSX is a 32 bit Application so it's limited to 4GB Virtual Address Space (VAS) whether you are using a 32 bit or 64 bit OS. The main benefit of a 64bit OS is that your VRAM is not shadowed like it is with a 32bit OS, within the VAS. This leaves more Address space for your Applications (Within the 4GB VAS limit.) I'm still using Vista 32 bit, and I basically have to clear as much Address Space up front in order to run the NGX, which is the most demanding on your available VAS. I do this by not allowing Boot up DLL's that are not going to be used during the flight, basically all the DLL's for all the other addon aircraft, like the CS, Wilco/Feelthere, PMDG, aircraft. I do this by editing the dll.xml file and adding the following line to each entry that is optional to load (As I said usually the ones for your addon aircraft.) Remember also your VAS must also be contiguous, so clearing address space up front leaves larger available space for the rest of the APP. (This is also why those that get OOM's usually get them at the end of the flight on approach, when the Sim is loading all the detailed scenery of the arrival airport. While you may have enough available space in your VAS, the largest contiguous space may be too small for it to load into, resulting on a OOM or other CTD.

 

<ManualLoad>True</ManualLoad>

 

Note Leave the DLL's that you always need set to False.

 

Then when you startup FSX it will ask you if you want to load each of these DLLs individually. Say yes to the one(s) you are using for your flight and no to the rest. For example if you are flying the NGX, there is no need to load the CS or Feelthere DLLs. so say no to them. For me when I fly the NGX failure to do this will result in a OOM crash, usually during approach to a high detailed airport like FSDT or FlyTampa. Even this may not be enough, when flying to a real high detailed scenery area like New York, I also have to reduce Autogen to Sparse.

Manny - rebuild your Swap Space - whether it's on C:\, or a different drive. Simply make it Custom 100 - 100, reboot, then make it what you think it needs after it comes up.

 

My preference is for two files - a 100 meg Custom, fixed size on the C:, with a second, sized at 8 gig - again fixed size, Custom - not system managed.

 

https://dl.dropbox.c...ngs_C- copy.jpg

 

https://dl.dropbox.c...ngs_D- copy.jpg

 

 

<ManualLoad>True</ManualLoad>

Geat suggestion, Tom.. Never thought of it! (Sorry about the overlap - we posted at the same time)

 

Good site:- http://pcnineoneone.com/howto/swpfile2/

A 64 bit OS however allows 2 to the 64th power of memory to be used, or 18,446,744,073,709,551,616 bits ... which is a lot of GB's!!

 

the maximum physical memory supported by Win7 x64 Ultimate, Enterprise and Professional editions is 192Gb. That's a lot less than 2⁶⁴! The maximum supported by Win7 Home Premium is 16 GB, and by Win7 Home Basic is 8 Gb which is even less.

 

FS9 and FSX are both 32 bit application so the maximum Virtual Address Space (VAS) they can be allocated is 4 Gb, even on x64.

the maximum physical memory supported by Win7 x64 Ultimate, Enterprise and Professional editions is 192Gb. That's a lot less than 2⁶⁴! The maximum supported by Win7 Home Premium is 16 GB, and by Win7 Home Basic is 8 Gb which is even less.

 

FS9 and FSX are both 32 bit application so the maximum Virtual Address Space (VAS) they can be allocated is 4 Gb, even on x64.

 

Fair point. The 2⁶⁴ is the theoretical maximum a 64 bit OS can address. I'd forgotten about the stupid limits that Microsoft enforced for the different Win7 versions.

<ManualLoad>True</ManualLoad>

 

Note Leave the DLL's that you always need set to False.

 

Then when you startup FSX it will ask you if you want to load each of these DLLs individually. Say yes to the one(s) you are using for your flight and no to the rest. For example if you are flying the NGX, there is no need to load the CS or Feelthere DLLs. so say no to them. For me when I fly the NGX failure to do this will result in a OOM crash, usually during approach to a high detailed airport like FSDT or FlyTampa. Even this may not be enough, when flying to a real high detailed scenery area like New York, I also have to reduce Autogen to Sparse.

 

 

Manny - rebuild your Swap Space - whether it's on C:\, or a different drive. Simply make it Custom 100 - 100, reboot, then make it what you think it needs after it comes up.

 

My preference is for two files - a 100 meg Custom, fixed size on the C:, with a second, sized at 8 gig - again fixed size, Custom - not system managed.

 

https://dl.dropbox.c...ngs_C- copy.jpg

 

https://dl.dropbox.c...ngs_D- copy.jpg

 

 

[/font][/color]

Geat suggestion, Tom.. Never thought of it! (Sorry about the overlap - we posted at the same time)

 

Good site:- http://pcnineoneone....howto/swpfile2/

 

So I basically need to watch out for uncessary DLLs (which I can understand) as well as need a bigger swap file?

 

Would a bigger swap file help with avoiding OOM errors?

 

Manny

Depends upon how your paging file is configured, Manny, which OS you have, and how much system memory you have - and - if the paging file is system managed - how much contiguous space is left, (load dependent) as you fly?

 

A dedicated paging file will not become discontiguous, whereas a system-managed one will. Secondly, when Windows has a fair disk I/O when running something like FSX, it's also managing a slew of other work - like your NGX, TrackIR, AS2012, ATC_Pro, EZCA - in addition to managing it's own hardware, running it's Anti-virus, Windows Update, the internet, the firewall, the sound system, Explorer, and whatever else is running. Managing a paging file on the C:\ creates even more work for the CPU and for the disk. The CPU has to decide "where is the next free chunk of disk space", and "how big is it". If it's a dedicated, known size and location - on a different drive - it's work is cut in half. Disk access is no longer in contention, and contiguous space is always available. And performance goes up.

One last question. What order to install FSX? I do have the acceleration pack. Will I have to install the SP1 & 2 if I use this. It has been too long since I did all that. I just can't remember.

R

Acceleration includes all the updates.

 

Cheers.