Simviation Forums

This used to be in the FAQ but someone removed it.

Always a good idea to make a backup of your fsx.cfg file. So where is it?

With all the talk of Steam and how it might change your fsx.cfg file - I thought I would mention where this file is located (it's not in the FSX folder)

C:\Users\Your Name\AppData\Roaming\Microsoft\FSX (vista/w7)

(If you cannot see it go to left menu of the folder window - Organize - folder and search options - View - and 'Show hidden files)

Good one Pete!

pete wrote:Always a good idea to make a backup of your fsx.cfg file.

Indeed. This applies to all default files before attempting to edit/modify them.

All I know about FSX-SE is what I've read about it here & on other websites, including the Steam forums & FAQ.
As I understand it, if you have FSX boxed edition already installed FSX-SE & all associated files will be installed to separate directories.
Note: This could cause problems installing some 3rd party software with auto-installers to FSX-SE.

The main CFG file will be named fsx-se.cfg & will be in the following directory:
C:\Users\Your Name\AppData\Roaming\\Microsoft\FSX-SE\fsx_se.CFG

To be on the safe side here's a little tip I discovered years ago while experimenting with duplicate installations of MSFS.
Before installing FSX-SE take a copy of fsx.cfg & rename it. Any prefix will do, let's say fsx-ms.exe
Make sure your new fsx-ms.exe is in the same directory as the original fsx.exe
When you first run FSX from the renamed EXE file a brand new CFG file with the same prefix (in this case fsx-ms.cfg) will be created alongside fsx.cfg.
Data from your original fsx.cfg can then be pasted into it. I've tested this before posting so I know it works.

Hagar wrote:To be on the safe side here's a little tip I discovered years ago while experimenting with duplicate installations of MSFS.
Before installing FSX-SE take a copy of fsx.cfg & rename it. Any prefix will do, let's say fsx-ms.exe
Make sure your new fsx-ms.exe is in the same directory as the original fsx.exe
When you first run FSX from the renamed EXE file a brand new CFG file with the same prefix (in this case fsx-ms.cfg) will be created alongside fsx.cfg.
Data from your original fsx.cfg can then be pasted into it. I've tested this before posting so I know it works.

Please note that fsx.cfg should read fsx.exe. Sorry for the typo.

Hagar wrote:Good one Pete!

pete wrote:Always a good idea to make a backup of your fsx.cfg file.

Indeed. This applies to all default files before attempting to edit/modify them.

All I know about FSX-SE is what I've read about it here & on other websites, including the Steam forums & FAQ.
As I understand it, if you have FSX boxed edition already installed FSX-SE & all associated files will be installed to separate directories.
Note: This could cause problems installing some 3rd party software with auto-installers to FSX-SE.

The main CFG file will be named fsx-se.cfg & will be in the following directory:
C:\Users\Your Name\AppData\Roaming\\Microsoft\FSX-SE\fsx_se.CFG

To be on the safe side here's a little tip I discovered years ago while experimenting with duplicate installations of MSFS.
Before installing FSX-SE take a copy of fsx.cfg & rename it. Any prefix will do, let's say fsx-ms.exe
Make sure your new fsx-ms.exe is in the same directory as the original fsx.exe
When you first run FSX from the renamed EXE file a brand new CFG file with the same prefix (in this case fsx-ms.cfg) will be created alongside fsx.cfg.
Data from your original fsx.cfg can then be pasted into it. I've tested this before posting so I know it works.

All I can say is I know for a fact that when I was beta testing the steam edition of FSX it used my Microsoft version of the FSX cfg file. I know this for a fact because it tried to use the default aircraft that I have set up in FSX and because like you stated the steam edition creates its own folders it could not find the aircraft that I use in my Microsoft version because it is not a default aircraft. It took me a few minuets to figure out why I was getting the Aircraft not initializing error when I started up the Steam edition. That was when I renamed my FSX cfg file to force the steam version to make its own.
Now it is possible that Steam changed this as I reported it as a problem so It might make its own version of the FSX.cfg file
I uninstalled the Stem version as I personally did not like the textures that it was using. My default airport which is KJAX was completely different.
Now I have to be honest it was not all that bad but I just did not like the way it looked as the changes were nothing like the real thing.
But the auto installers could indeed be a problem as most of them look in the default location. Something I check out good before i download anything as I do not have FSX installed in the default location. In most cases reading the read me file will let you know this.
It has been my experience that most of the trusted download sites will give you a option as to where to install there products. But as they say it is wise to read the read me file and know your download source well.

I have my boxed FSX on C drive and my SE FSX installed/partitioned to D drive. Does anyone know if that would make a difference?

Steve M wrote:I have my boxed FSX on C drive and my SE FSX installed/partitioned to D drive. Does anyone know if that would make a difference?

It does not make a deference as to where you have the Game installed because the cfg file is put in the same place no matter what.
Location depends on your operating system in windows 7 and 8 64 bit you will find this file on the C drive under Users\Your Name\Application Data\roaming\Microsoft\FSX or something like that.
Now if steam does make its own FSX CFG file than you do not have to worry about it.

OK, thanks for your reply Garymb.

The 3 most imprtant words in simming: Back-up, Back-up, Back-up!

I foung a little desktop search engine called 'Everything' from www.voidtools.com.
This saves a lot of head scratching when trying to find stuff.
It's free, & once you install it, it takes a minute or two to index your drives (once only). Then, when you want to search for, let's say... fsx.cfg, as you start typing, it starts giving suggestions, so, by the time you get to fsx. it will give a list of appropiate files names.

I've found it to be pretty essential for any PC use.

garymbuska wrote:

Hagar wrote:Good one Pete!

pete wrote:Always a good idea to make a backup of your fsx.cfg file.

Indeed. This applies to all default files before attempting to edit/modify them.

All I know about FSX-SE is what I've read about it here & on other websites, including the Steam forums & FAQ.
As I understand it, if you have FSX boxed edition already installed FSX-SE & all associated files will be installed to separate directories.
Note: This could cause problems installing some 3rd party software with auto-installers to FSX-SE.

The main CFG file will be named fsx-se.cfg & will be in the following directory:
C:\Users\Your Name\AppData\Roaming\\Microsoft\FSX-SE\fsx_se.CFG

To be on the safe side here's a little tip I discovered years ago while experimenting with duplicate installations of MSFS.
Before installing FSX-SE take a copy of fsx.cfg & rename it. Any prefix will do, let's say fsx-ms.exe
Make sure your new fsx-ms.exe is in the same directory as the original fsx.exe
When you first run FSX from the renamed EXE file a brand new CFG file with the same prefix (in this case fsx-ms.cfg) will be created alongside fsx.cfg.
Data from your original fsx.cfg can then be pasted into it. I've tested this before posting so I know it works.

All I can say is I know for a fact that when I was beta testing the steam edition of FSX it used my Microsoft version of the FSX cfg file. I know this for a fact because it tried to use the default aircraft that I have set up in FSX and because like you stated the steam edition creates its own folders it could not find the aircraft that I use in my Microsoft version because it is not a default aircraft. It took me a few minuets to figure out why I was getting the Aircraft not initializing error when I started up the Steam edition. That was when I renamed my FSX cfg file to force the steam version to make its own.
Now it is possible that Steam changed this as I reported it as a problem so It might make its own version of the FSX.cfg file
I uninstalled the Stem version as I personally did not like the textures that it was using. My default airport which is KJAX was completely different.
Now I have to be honest it was not all that bad but I just did not like the way it looked as the changes were nothing like the real thing.
But the auto installers could indeed be a problem as most of them look in the default location. Something I check out good before i download anything as I do not have FSX installed in the default location. In most cases reading the read me file will let you know this.
It has been my experience that most of the trusted download sites will give you a option as to where to install there products. But as they say it is wise to read the read me file and know your download source well.

Steam does not change any textures. There have been and are no changes made to scenery. They only have rights from ms to enable the game to function through the steam portal. It includes some tweaks in the cfg for allowing the game to run with newer processors.
The release version does not interact with the box version cfg. However, if you install on a computer that has never had or does not have the box version, it will install with all the same named directories as fax normally would.

If you are running FSX in windows 8/8.1 click start then run and paste this %AppData%\Microsoft\FSX in and it will take you straight to your FSX.CFG file


Rick

Azframer wrote:If you are running FSX in windows 8/8.1 click start then run and paste this %AppData%\Microsoft\FSX in and it will take you straight to your FSX.CFG file


Rick

Excellent short-cut, Rick!.... ...!

Paul....short-cuts are always nice!.... ...!

For those of you yet to explore Windows 10, the FSX.cfg is in the same place as 7/8.1

Another trick to find a "missing" fsx.cfg file...

side-fish has Microsoft Flight Simulator X: Steam Edition Dec 28, 2014 @ 6:29pm

Open Notepad first. Go to File in the menu bar and click Open.

For fsx.cfg, copy this to the text box:

C:\Users\[user]\AppData\Roaming\Microsoft\FSX

Select 'All Files' to see files other than .txt documents. Select fsx.cfg and Open.

Found this technique utilizing Notepad when the above search for the file netted 0 results. I'm still running Windows7 for what it's worth.

Now it is possible that Steam changed this as I reported it as a problem so It might make its own version of the FSX.cfg file

[/quote]

Hello gary, yes your report worked. When you install FSX Steam Edition it makes its own file named FSX_SE.cfg and it does not interfere in any way with the FSX.cfg from your FSX installation. FYI.

pete wrote:This used to be in the FAQ but someone removed it.

Always a good idea to make a backup of your fsx.cfg file. So where is it?

With all the talk of Steam and how it might change your fsx.cfg file - I thought I would mention where this file is located (it's not in the FSX folder)

C:\Users\Your Name\AppData\Roaming\Microsoft\FSX (vista/w7)

(If you cannot see it go to left menu of the folder window - Organize - folder and search options - View - and 'Show hidden files)

Same place in Windows 10 also.