Before you start with the installation of FSX-SE it is our recommendation to uninstall the previous FSX version. FSX is dead! Be happy with Steam! Read the easy way to remove your previous FSX installation.
- The easy way:
- Go to Start/Program and Features/ and select the previous FSX installation in Uninstall or change a program.
- Uninstall FSX and when you have FSX+SP2 installed, it will return with FSX-SP1. Check the version number.
- Now, uninstall again FSX; it will no longer be in the list of Programs and Features.
- Clean your registry with CCleaner or another registry cleaner and repeat the cleaning until there are zero faults.
- The remaining folders in the still existing FSX installation folder contains important stuff that you added previously (FSUIPC Key, aircraft, add-on scenery, a.s.o.).
- Rename you rinstallation folder and move it to your backup location. You will need it later on.
- Reboot the system and ceck if all the previous registrations are gone in the registry; therefore use the TweakFSX Registry tool as mentioned HERE. Try to find the previous FSX path. If there’s nothing found, you’re clean and then install FSX-SE else you need to go into the registry manualy and delete the remaining registry entry as indicated in the tool. You will read the registry key as HKEY_LOCAL_MACHINE_SOFTWAREMicrosoft…and the installation path of y0ur previous installation
- How to get into the registry? In Windows 8 just type regedit @Start and hit ENTER
- Only delete the registry entries shown here, when uninstalling boxed version of FSX.
Once FSX:SE is then installed, this entry will be present again – so don’t delete it after the installation of FSX-SE! …
Only delete it just before you do a clean install of FSX-SE
Hello Captains, in this and coming articles we will inform you with tips and tricks about FSE-SE. Many thanks to our crew member Piejo who shared his early experiences with FSX-SE.
- How To Install FSX-SE as
- a Single Sim Setup (FSX-SE only) or
- a Dual Sim Setup (FSX + FSX-SE on one machine)
- What you should know:
- about Installers
- If you are not familiar with the requirements for a succesful deployment of your simulator, please read the related articles in our FSX-SE pages. When you have already FSX on board, you have 2 choices: either remove FSX from your PC and install FSX-SE as a Single Sim Setup (1.A. ) or install FSX-SE next to the already existing FSX installation (1.B. Dual Sim Setup).
Note: You cannot run both sims the same time on one machine !
- with Single Sim Setup: FSX-SE will install as a normal FSX installation, using the standard registry path, folder and file names. No issues.
- with Dual Sim Setup: FSX-SE is fully separated from FSX and after installation you can use both sims. FSX is not effected. But…
FSX-SE has its own registry values which results at the same time in a disadvantage for 3rd party FSX-Add-on-installers since they natively refer to the registry location of FSX and not to FSX_SE
A 3rd party add-on that needs to use the fsx.cfg must have another reference since in Dual Sim Setup this file is called fsx-se.cfg (!)
- Based on the fact that FSX-SE will further develop, manufacturers from aircraft, sceneries and other add-ons will phase out FSX development and focus on this new market. This brings us to the recommendation: create a Single Sim Setup.
- about Registry issues
- If you need to adapt your registry path for any reason, this article and this article will show you how to manage.
- the registry paths for FSX are named as HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Microsoft Games/flight simulator/10.0
HKEY_CURRENT_USER/SOFTWARE/Wow6432Node/Microsoft/Microsoft Games/flight simulator/10.0
- the registry path for FSX-SE is named as HKEY_LOCAL_MACHINE/SOFTWARE/Dovetail/Games/FSX
- about Add-ons made for FSX
- FSX-Add-ons that use FSUIPC: you need an updated version of FSUIPC4 4.3939 or later which can be retrieved HERE.
- FSX-Add-ons like non stock aircraft and non-stock sceneries: will work without issues; beware of any installation registry issues (see 2.A.c.)
- FSX-Add-ons that use SimConnect:
-with a Single Sim Setup: you should install the FSX SimConnect runtime libraries that can be found in the SDK folder in the FSX-SE installation. There you will read the legacy interface installers (.msi files).
-with a Dual Sim Setup: without installing FSX SimConnect runtime libraries (that can be found in the SDK folder in the FSX-SE installation) none of the FSX Add-ons using the previous simconnect version of FSX-SP1-SP2-Acc_pack will work.
- FSX-Add-ons that use customized .DLL modules to access directly FSX memory locations: most of this type of existing .dll’s don’t support FSX-SE and in that case will FSE-SE cause to crash.
- Add-ons that use customized .gau modules to access directly FSX memory locations: most of the existing .dll’s don’t support FSX-SE and in that case will FSE-SE cause to crash.
Remove the old FSX installation and start with FSX-SE.
Read further @ 3.A.
- Installation of a Single Sim Setup FSX-SE: (clean install)
- The advantage of this option is that FSX-SE, at installation, places a number of important files (fsx.cfg file, DLL.XML, the Controls folder, the Shaders folders, the scenery.cfg file and other files which are being placed outside the FSX-SE root), in folders which have the same name as previously in FSX. Therefore FSX-Addons can more easily be installed in FSX-SE. These are the folder names:
C:/Program Files (x86)/Steam/SteamApps/common/FSX) <- DEFAULT PATH C:/ProgramData/Microsoft/FSX
C:/Users/<username>/Documents/Flight Simulator X Files
- Note for choosing a different installation path/disk
- Go to Steam – Settings – Downloads
- Below Content Libraries select Steam Library Folders which opens a window where you could create or select a (new) Library folder (even at a separate drive)
- Setup the appropriate folder OR drive and folder where you want Steam to be installed.
- Install FSX-SE from STEAM
- Refer to par. 3.B. as to where you want it installed.
- Run the Sim once and reboot your PC. Continue with:
- Installing SimConnect library: Browse to C:(Program Files (x86))Steam/SteamApps/common/FSX/SDK/Core Utilities Kit/SimConnect SDKlib and run the SimConnect.msi installer by double clicking.
- Installing SimConnect Legacy Interface: Browse to C:(Program Files (x86))Steam/SteamApps/common/FSX/SDK/Core Utilities Kit/SimConnect SDK/LegacyInterfaces/ and run the SimConnect.msi installer in each of the three sub-folders by right clicking omn the .msi file.
- Installing FSUIPC4: if your add-ons need it, download and install the latest version of FSUIPC4 4.939 or later.
- Done! Almost all installers for the FSX-Add-ons should revert to FSX-SE’s location, e.g. all add-on scenery should install into the (correct) scenery.cfg location. FSX addons that use both the new Steam Simconnect and the older Simconnect versions should work ok.
- Installation of a Dual Sim Setup FSX-SE (don’t do this!)
If you did not follow our recommendation for the installation of a Single Sim Setup we will guide you through the installation steps to go.
- Install FSX:SE from STEAM then
- Refer to par. 3.B. as to where you want it to be installed.
- Run the Sim once and reboot your PC. Continue with:
- Installing SimConnect library: Browse to C:(Program Files (x86))SteamSteamAppscommonFSXSDKCore Utilities KitSimConnect SDKlib and run the SimConnect.msi installer by double clicking.
- Installing SimConnect Legacy Interface: Browse to C:(Program Files (x86))SteamSteamAppscommonFSXSDKCore Utilities KitSimConnect SDKLegacyInterfaces, and run the SimConnect.msi installer in each of the three sub-folders by double clicking.
- Which folders result after installation of FSX-SE?
After installation your PC will contain the following folders c.q. files:
For FSX (those files already existed)
C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator X C:ProgramDataMicrosoftFSX C:Users<yourname>AppDataLocalMicrosoftFSX C:Users<yourname>AppDataRoamingMicrosoftFSX C:Users<yourname>DocumentsFlight Simulator X Files
– HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft Gamesflight simulator10.0
– HKEY_CURRENT_USERSOFTWARE(Wow6432Node)MicrosoftMicrosoft Gamesflight simulator10.0
C:Program Files (x86)SteamSteamAppscommonFSX <- DEFAULT PATH
C:ProgramDataMicrosoftFSX-SE (scenery config file) C:Users<yourname>AppDataLocalMicrosoftFSX-SE (shaders) C:Users<yourname>AppDataRoamingMicrosoftFSX-SE (FSX-SE.cfg, (fall-back)scenery.cfg, controls.cfg, DLL.XML).
C:Users<yourname>DocumentsFlight Simulator X – Steam Edition Files
Registry key (64bit o/s shown)
- Install Addons in FSX-SE
In order to achieve that FSX addons will be installed correctly in FSX-SE, you have to do the following:
– Download and install FSUIPC4 4.393 or later, if your addons need it.
– Download TweakFS/FSRegUtil.
Note: TweakFS Registry Utility has a small bug where the first time you use it and select the ‘Search Reg’ button, it will launch the Windows Registry Editor, but will not search for the FSX entry. If this happens, simply close the Windows Reg Editor window (that has popped up) and go back to TweakFS Reg Utility and press the ‘Search Reg’ button again – it will work the second time, and will launch the registry and find your FSX entry.
-You will need this since a FSX-installer of an add-on needs to know where FSX-SE is installed.
-Save this utility program in your download folder and run it as Administrator, right clicking the exe file.
– Now -before you run the add-on installer- Get the FSX path. (Tab Get Path, then press Get FSX Path)
. In the sample below you see that FSX is installed directly on the D: drive. Now, you are going to change that path to where FSX-Se is installed.
- Select “Set Path” tab and select your FSX-SE installation directory. Then select “Set FSX Path”.
- After, check the “Add to Current User” checkbox and click “Set FSX Path” again. In the sample below you see that FSX-SE is also installed on the D: drive.
- Through this action an installer of an addon made for FSX can see that the addon must be installed in the folder and sub-folders where FSX-SE is installed.
- However, you are not ready yet, because, during the execution of the add-on installer, there are also FSX-SE files in the folders mentioned above, which by a number of addons have to be adapted during their installation. These (3) folder names are:
(namely the FSX-Steam scenery config file)
(namely the FSX-Steam shaders)
(namely the config file, the scenery config file, the Controls folders, and the XML config file for FSX-Steam).
- In order to achieve that an installer of a FSX add-on can also correctly effect the necessary changes in the files in those folders, you need to temporarily change the names of the above mentioned 3 :: folders, otherwise the changes are not written (!)
- So, if you also have a stock FSX installed too, this involves firstly to temporarily renaming the ‘FSX’ folder within the above file paths to something like ‘FSXbackup’.
- Rename C:ProgramDataMicrosoftFSX into C:ProgramDataMicrosoftFSXtemp
- Rename C:UsersyournameAppDataLocalMicrosoftFSX into
- Rename C:UsersyournameAppDataRoamingMicrosoftFSX into
- Then simply change the ‘FSX-SE’ folder within the above file paths, to ‘FSX’. Now when you run any addon installer for FSX, the FSX Steam folders will be properly adapted.
- Rename C:ProgramDataMicrosoftFSX-SE into C:ProgramDataMicrosoftFSX
- Rename C:UsersyournameAppDataLocalMicrosoftFSX-SE into
- Rename C:UsersyournameAppDataRoamingMicrosoftFSX-SE into
- It is essential that you change the names of these folders back to their original ‘FSX’ and ‘FSX-SE’ names, once you’ve finished installing scenery and before launching either FSX or FSX-SE !
- Moreover, if you later on want to install an FSX-addon in FSX (not FSX-SE), do not forget to change the path back to FSX again from FSX-SE with the help of the TWEAKFS FSX REGISTRY UTILITY!
Of course going forward, these steps should eventually become redundant; once native FSX-SE addons are released via Steam (or even 3rd parties). They will have then native abilities to point to the correct Scenery.cfg files, and similarly, eventually it’s hoped that DTG / Steam will update FSX-SE to remove all Registry confusions between the sims. What we really need until that time is a ‘switch’ that automatically changes all file paths (sim installation, fsx.cfg, scenery.cfg) according to which sim we want to install an add-on in to.