Found an option in the FSX.EXE that fools FSX into using more RAM.

Care to share what you think you found? The FSX.EXE is already large address aware and you can't fool it into using more than 4gb of RAM since it's a 32bit application, but would be interested to know what you did anyway.

Thanks for participating, I am in the process of installing quick change SSD's to keep my original installation on F:\Microsoft Flight Simulator X with Windows 7 64 bit on C: SSD.

The 2 new SSD's will have Windows 7 64 bit on Drive C: 256 GB SSD and FSX on F: 512 GB SSD both dedicated to FSX only. I just don't know at this time where I am going to put my scenery files. I was thinking of putting them on a third SSD altogether separate from Win 7 and FSX, but found that I only have two 6 GB SSD connections on my MB and the rest are 3 GB connections, silly ASUS.

 

Got mine in the default location on the C: drive (C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X). UAC is on and has been since I installed Windows 7 x64 - UAC stays running when installing add-ons (RealAir, A2A, REX, various scenery add-ons) and I have yet to have any problems. I even leave my antivirus running (Bitdefender) whilst running FSX. I can't help thinking that anyone who attributes their problems to any of these choices has issues outside of FSX which need sorting first.

Steam library folder on a separate SSD partition. Because SSD. And Steam.

on my C drive, C;\fsx on one SSD 512 GB

NOT the default location in C:\Program Files (x86)

 

The reason is that many addons will face problems with access rights to files if FSX is located there. Not all of them, but those which need to write files in the FSX directory while FSX or the addon is running.

 

So you won't experience problems with (most) scenery addons or planes, because they simply write their files once (during installation) and then work fine. Other addons need to write their configuration files into the FSX directory and cannot do that in the default location.

 

Cheers,

Peter

NOT the default location in C:\Program Files (x86)

 

The reason is that many addons will face problems with access rights to files if FSX is located there. Not all of them, but those which need to write files in the FSX directory while FSX or the addon is running.

 

So you won't experience problems with (most) scenery addons or planes, because they simply write their files once (during installation) and then work fine. Other addons need to write their configuration files into the FSX directory and cannot do that in the default location.

 

Cheers,

Peter

 

Which add-ons, for example?

Oh boy, that's a hard question because I moved FSX a couple of years ago, but I can assure you that I did have problems and that they are gone since I moved FSX.

 

One program I know for sure is FSCaptain (because I closely follow the support forum). Usually this can be overcome by running FSCaptain as administrator, but I recall that I had serious issues with another addon that required more tweaking (I think it was still under Win 7)

 

Generally, any program that needs to write files can potentially run into problems. Just Google "<Your addon Program Name> access rights" or the like. In this way I found something about PFPX and the flight plans for PMDG planes, for instance.

 

Peter

Hey I found this Ram thing On a video posted by Flightsim addict on youtube

 

Thanks for participating, I am in the process of installing quick change SSD's to keep my original installation on F:\Microsoft Flight Simulator X with Windows 7 64 bit on C: SSD.

The 2 new SSD's will have Windows 7 64 bit on Drive C: 256 GB SSD and FSX on F: 512 GB SSD both dedicated to FSX only. I just don't know at this time where I am going to put my scenery files. I was thinking of putting them on a third SSD altogether separate from Win 7 and FSX, but found that I only have two 6 GB SSD connections on my MB and the rest are 3 GB connections, silly ASUS.

 

 

Much of the scenery is installed into the FSX/P3D folders anyway, so no real need for a dedicated scenery drive.

 

Don't blame ASUS. I've got 6 x 6GB SATA ports on my computer + 2 x 3GB SATA connections on my ASUS MB. You get what you pay for.

Much of the scenery is installed into the FSX/P3D folders anyway, so no real need for a dedicated scenery drive.

 

Don't blame ASUS. I've got 6 x 6GB SATA ports on my computer + 2 x 3GB SATA connections on my ASUS MB. You get what you pay for.

At the time that was what was available for the Sabertooth.  :(

Oh boy, that's a hard question because I moved FSX a couple of years ago, but I can assure you that I did have problems and that they are gone since I moved FSX.One program I know for sure is FSCaptain (because I closely follow the support forum). Usually this can be overcome by running FSCaptain as administrator, but I recall that I had serious issues with another addon that required more tweaking (I think it was still under Win 7)Generally, any program that needs to write files can potentially run into problems. Just Google "<Your addon Program Name> access rights" or the like. In this way I found something about PFPX and the flight plans for PMDG planes, for instance.Peter

I don't have FSCaptain but I do have a few other add-ons which write to the FSX folder after having been installed and they seem to work flawlessly. As you hinted at in your post, setting programs to run with administrative privileges should always allow them to write to folders in C:\Program Files (x86).

Mine is 6 feet under....well you asked where it was....

Samsung 840 Evo 500GB

 

B:\Microsoft Flight Simulator X

 

Along with that on the same disk I run XP10, Rise of Flight, and Battlefield 4

 

OS is on totally separate drive (a sata II SSD)

Hi Vortex,

As you hinted at in your post, setting programs to run with administrative privileges should always allow them to write to folders in C:\Program Files (x86).

Not exactly. Running a program as admin solves the problem for most addons, but I recall that I had one addon where I had to dig deeper. It is too long ago for me to remember details, but it was either under XP or Win7. There was a rather subtle change in the file access rights required - not just set the file as readable and writeable, there was something more.

 

The bottom line is: you can solve the problems associated with the default FSX location, but its may cost you time to do so.

 

Best,

Peter