~Craig~

A couple of tips for FSX:SE users

Recommended Posts

This advice applies to FSX / FSX:SE parallel installs only!

 

Firstly, one of the things FSX:SE users may have noticed is that add-on scenery that is installed using the proper installer, never gets automatically added to your Scenery Library and always needs to be added manually within the sim.

 

This is because all scenery installers for FSX, add the scenery by updating the Scenery.cfg file, and in the boxed version of FSX, this file is located at :-

 

C:\ProgramData\Microsoft\FSX\Scenery.cfg

 

So an installer that was intended for the boxed version of FSX, will always update the Scenery.cfg at the above location.  But the location for the Scenery.cfg in FSX:SE changed.

 

The Scenery.cfg for FSX:SE is located at the subtley different :-

 

C:\ProgramData\Microsoft\FSX-SE\Scenery.cfg

 

So this is why scenery installed into FSX:SE is never automatically added to your scenery library (even if the installer path correctly points to the FSX:SE installation location  (C:\Program Files (x86)\Steam\SteamApps\common\FSX).

 

There are two solutions to this problem:-

 

1). Simply add scenery manually using the Scenery Library within FSX:SE,

 

or,

 

2). You can temporarily change the names of the scenery.cfg paths, so that scenery is installed directly into FSX:SE...... but you must remember to then change it back!

 

So, if you also have boxed FSX installed too, this involves firstly, temporarily renaming the 'FSX' folder within the above file path (the part marked in green), to something like 'FSXbackup'.

 

Then simply change the 'FSX-SE' folder within the above file path (again, the bit in green), to 'FSX'.

 

Now when you run any scenery installer for FSX, the scenery will be properly added to FSX:SE's scenery library as it should be.

 

It is essential that you change the names of both of these folder back to their original 'FSX' and 'FSX:SE' names, once you've finished installing scenery, and before launching either FSX or FSX:SE  !

 

===========================

 

Secondly, it appears from reports so far, that users who already have boxed FSX installed, and then install FSX:SE tend to have a more successful time with installers that were made for boxed FSX, and in them locating FSX:SE's updated location, via Registry.

 

However some users, may want to delete boxed FSX, and start solely using FSX:SE, for ease of management, hard disk capacity etc.

 

In this case, it is advised not to uninstall boxed FSX using it's standard uninstaller.  The reason for this is that whereas FSX and FSX:SE do share some registry elements (which is why when you install FSX:SE after boxed FSX, most installers automatically know and point to the FSX:SE location), but other Registry elements are not shared.

 

If you do currently have both boxed FSX and FSX:SE installed, and wish to remove boxed FSX, I'd suggest at this time that the best way of doing this is simply to manually delete your Microsoft Games/Microsoft Flight Simulator X folder.   This contains all core files and for most users will be many Gigabytes in size.   Expect deletion to take around 20 minutes+.

 

This will restore all of the HD space that FSX was taking up, but without messing up the registry elements.  If you use FSX's uninstall process, it will unistall at least some of FSX:SE's Registry elements!

 

Manually deleting your FSX folder is also good because it will retain directories like your FSX.CFG (which you may want to keep to refer to), and the Scenery.cfg as noted above  - both of which are in different locations from the main FSX folder that you're deleting here.

 

Of course going forward, both of these steps should eventually become redundant;  once native FSX:SE addons are released via Steam (or even 3rd parties) they will have 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.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Great post, Craig. Very useful, your efforts are really much appreciated.

I will strictly follow your recommendations as soon as the Steam support will bother replying to my ticket and helping me complete the transaction, which I can't do since day 24... :(

Pretty surprised to be honest.

Share this post


Link to post
Share on other sites

Hey Craig,

I havent noticed any problems yet with scenery addons not being added to the scenery.cfg automaticly, but I do like to know how to add scenery manually, so I can add scenery that is already on my system, on other drives. I cant seem to figure out how to do this and from your post I get the impression you found how to do that.

Would you mind explaining how you get this done?

Share this post


Link to post
Share on other sites

Hey Craig,

I havent noticed any problems yet with scenery addons not being added to the scenery.cfg automaticly, but I do like to know how to add scenery manually, so I can add scenery that is already on my system, on other drives. I cant seem to figure out how to do this and from your post I get the impression you found how to do that.

Would you mind explaining how you get this done?

 

Hi Maarten,

 

Did you install just FSX:SE on it's own (without an existing FSX installation in place) ? ... In that situation, it is possible that FSX:SE will use the same folder name for the Scenery.cfg (as it does for the FSX_SE.cfg in the same scenario).    

 

In which case, my advice in the OP, would only apply to those who have a parallel installation of FSX and FSX:SE.     Unfortunately, I can no longer edit the OP to clarify this.   Apologies for any inconvenience.

 

In the OP, when I referred to "adding scenery manually", I really just meant by using FSX / FSX:SE's Scenery Library.   (under 'Settings' within the sim options, or 'World' once you're in a flight).

 

If you take a look at the scenery.cfg file though (at the path(s) shown in the OP), you can see how scenery can indeed be added manually, outside of FSX.

 

The format for each piece of scenery looks like this ;-

 

[Area.199]
Title=UK2000 Manchester Xtreme
Local=UK2000 scenery\UK2000 Manchester Xtreme
Active=TRUE
Required=FALSE
Layer=201
 
So to add scenery completely manually, you would simply store it somewhere (I'd suggest FSX or FSX:SE's "Addon Scenery" folder), and then add an entry such as the above, to the scenery.cfg.
 
In the above example, I've added UK2000 Manchester Xtreme (in this example, the scenery is stored in the main FSX root folder, not in the "Addon Scenery folder), and the most important part of that entry is the location of the scenery (within the FSX root directory):-  
 
UK2000 scenery\UK2000 Manchester Xtreme
 
Hope this helps!

Share this post


Link to post
Share on other sites

Did you install just FSX:SE on it's own (without an existing FSX installation in place) ? ... In that situation, it is possible that FSX:SE will use the same folder name for the Scenery.cfg (as it does for the FSX_SE.cfg in the same scenario).

 

That is the case with me also, Stand Alone Install. So the type of install should be pointed out with any "how to's". Your not the only one, some developers are finding this out also.

Share this post


Link to post
Share on other sites

Ah, of course. I hadnt even thought about adding them to the .cfg manually. I've been trying to do it through the library, but FSX:SE didnt pick up the selected folders.

Thanks, Craig! :)

Share this post


Link to post
Share on other sites

Thanks Craig, these are excellent tips!

 

I did install FSX-SE on a clean system, and can confirm that it did emulate an original FSX installation, with all of the config files placed in the standard folders in users/(user name)/appdata/microsoft/FSX, and programdata/Microsoft/FSX, and with the standard names "FSX.CFG" and "SCENERY.CFG". This allows most installers to work just as they would in original FSX.

 

One very important thing that needs to be done on a clean (FSX-SE ONLY) installation is to install all three versions of simconnect that were associated with original FSX. The new FSX installs its own version of simconnect, which works well if you just run the program with no add-ons, but that version will not work with simconnect-enabled add-ons that were designed for original FSX.

 

There is a folder in the Steam FSX directory named "SDK". If you drill down into that folder, beginning with the subfolder "Core Utilities Kit", you will come to a "Legacy Interfaces" folder, containing simconnect.msi installers for all three original FSX versions: FSX-RTM, FSX-SP1, and FSX-XPACK (which is the simconnect for SP2/Acceleration).

 

All three legacy installers should be run in turn, which will insure that any add-on looking for any older version of simconnect.dll will find the right one when running under FSX-SE.

Share this post


Link to post
Share on other sites

/\ /\ /\  ... That's great advice as well Jim, about the Legacy Simconnect dependencies. 

 

 

====================

 

I'll contact a moderator and see if they can add the text;

 

"For FSX / FSX:SE Parallel installs only"  to the OP.   

Share this post


Link to post
Share on other sites

For the 'side-by-side' case as addressed by Craig in the original post here, an option that SHOULD work is to create a symbolic "junction" from the location of the FSX-SE Scenery.cfg file to the FSX Scenery.cfg file location. Then any scenery added in the FSX install will automatically be seen in the FSX-SE install. Junctions ( mklink /j) works on directories/folders that can be on different volumes.

 

For FILES, use:

 

mklink /H d:\Linked_TO c:\Linked_From

 

"Linked_From" is the 'real' file, "Linked_TO" is the location where the 'hard link' to the 'real' file will reside.

 

to create a Hard Link for files. They MUST reside on the same Drive but can be in different locations on that drive.

 

mklink /H C:\ProgramData\Microsoft\FSX-SE\Scenery.cfg C:\ProgramData\Microsoft\FSX\Scenery.cfg

 

Changing the contents of the Scenery.cfg file in either location changes the actuall file contents as seen by both locations.

 

This would be entered in a Command Line after first renaming the FSX-SE Scenery.cfg to any name of your chosing since the file can not exist in the FSX-SE location for the "junction" to work.

 

More info here:

http://www.sevenforums.com/tutorials/278262-mklink-create-use-links-windows.html

 

Paul

Share this post


Link to post
Share on other sites

Hey Paul, great info, but not sure what you mean by  "first renaming the FSX-SE Scenery.cfg to any name of your chosing since the file can not exist in the FSX-SE location for the "junction" yo work"  In this example you gave  mklink /H C:\ProgramData\Microsoft\FSX-SE\Scenery.cfg C:\ProgramData\Microsoft\FSX\Scenery.cfg,     I would need to change the FSX-SE  Scenery.cfg in that folder to something else  IE:  myscenery.cfg

Share this post


Link to post
Share on other sites

After a lot of continued experimenting and investigation, I've come to the personal conclusion that the easiest way to proceed with FSX:SE, is to have it installed on it's own (without a parallel FSX installation), with a few notes :-

 

If you have never had 'boxed FSX' installed on the machine

 

  • Simply install FSX:SE from STEAM.
  • Browse to C:\Program Files (x86)\Steam\SteamApps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces, and install the 3 legacy Simconnect versions.
  • You're good to go - almost all installers for FSX should revert to FSX:SE's location, and all addon 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.

 

If you have previously had FSX installed on the machine, or presently still have it installed

 

  • If you still have boxed FSX installed, uninstall it, using the MS FSX uninstaller (not a program like CCleaner's uninstall page).

Now, in all cases;

  • Download (free) TweakFS Registry Utility, and use the 'Search Reg' button to locate both your "LOCAL MACHINE" and "CURRENT USER" registry entries for FSX.

Link to Download Registry Utility:-

 

http://tweakfs.com/download/fsx_reg_utility.zip

 

  • When your registry appears and locates FSX registry entries, right click on the highlighted "10.0" folder (on the left panel) and select 'delete'.     (Do this for the LOCAL MACHINE and CURRENT USER registry entries.
  • Re-boot your PC.
  • Install FSX:SE from Steam.
  • Browse to C:\Program Files (x86)\Steam\SteamApps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces, and install the 3 legacy Simconnect versions.
  • You're good to go - almost all installers for FSX should revert to FSX:SE's location, and all addon 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.

 

In summary, even after uninstalling boxed FSX, it will often leave a registry entry.  This registry registry will change how FSX:SE is installed (renaming files like the fsx.cfg and scenery.cfg).   So if you have had boxed FSX installed on the PC before, it's a very good idea to use a FSX registry tool such as TweakFS Registry Utility to search and find the 'boxed FSX entry' (which is called "10.0", within the "Flight Simulator" registry folder of the "Microsoft" directory), and delete it before installing FSX:SE.

 

In any scenario, after installing FSX:SE, it will be necessary to browse to C:\Program Files (x86)\Steam\SteamApps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces, to install the 3 legacy Simconnect interfaces.

Share this post


Link to post
Share on other sites

Hey Paul, great info, but not sure what you mean by  "first renaming the FSX-SE Scenery.cfg to any name of your chosing since the file can not exist in the FSX-SE location for the "junction" yo work"  In this example you gave  mklink /H C:\ProgramData\Microsoft\FSX-SE\Scenery.cfg C:\ProgramData\Microsoft\FSX\Scenery.cfg,     I would need to change the FSX-SE  Scenery.cfg in that folder to something else  IE:  myscenery.cfg

For the link to function there can be no file named "Scenery.cfg" in the FSX-SE location, thus you

must rename the existing Sencery.cfg there or remove it. I recommend you just ar .bak or ,save to the extention.

 

In the mklink statement you must still use the name "Scenery.cfg" as that is what the link will be called, as it were. In the location C:\ProgramData\Microsoft\FSX-SE\   before the mklink, you should no longer see a file named "Scenery.cfg" but  you will see a file called "Scenery.cfg" again after you execute a successful mkink /H

 

Note that you can change the contents of that file from either the destination location or the original location.

 

  Paul

Share this post


Link to post
Share on other sites

Hey Craig, i have both installed right now, should i uninstall both and then reinstall FSX-SE, or can i leave my FSX-SE still installed?

Share this post


Link to post
Share on other sites

Hey Craig, i have both installed right now, should i uninstall both and then reinstall FSX-SE, or can i leave my FSX-SE still installed?

 

It's entirely up to you Dutch.  If all is well, you may want to keep things as they are.  My advice above is more to do with people who want to remove 'boxed FSX' and revert to just having one sim to maintain! :smile:

 

If you do want to move to using FSX:SE only, personally I'd advise uninstalling both, and then using the TweakFS Registry Utility to remove all registry entries for both 'boxed FSX' (which is references as Microsoft / Flight Simulator / 10.0 in the registry, and also FSX:SE's entries too (which should be right below it).

 

For info, this is what you are looking for in the registry, when looking to delete the old boxed FSX registry entry, that can mess things up :-   (Right click and 'delete' the folder shown below)

 

NOTE:  Only delete the registry entries shown here, when uninstalling boxed FSX, or FSX:SE.   Once FSX:SE is then installed clean, both of these entries will be present again - so don't delete them then! ... just before you do the clean install :wink:

reg10.jpg

 

 

....and if you are looking to unistall FSX:SE, this is what you're looking for:- 

(Right click and 'delete' the folder shown below)

 

NOTE:  Only delete the registry entries shown here, when uninstalling boxed FSX, or FSX:SE.   Once FSX:SE is then installed clean, both of these entries will be present again - so don't delete them then! ... just before you do the clean install :wink:

reg_fs10.jpg

 

 

This will give you a completely fresh, clean install of FSX:SE.

 

NB. 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.

 

If you just remove boxed FSX and leave FSX:SE as it currently is - addons etc will still be installed into FSX:SE as though you still have boxed FSX installed.   (So scenery etc, may be added to the wrong scenery.cfg, etc).

 

So for those serious enough about FSX:SE to want to move to it solely at this time, my advice would be ;-

 

- uninstall boxed FSX

- uninstall FSX:SE

- Use TweakFS Registry Utility to remove all registry entries for both sims

- Install FSX:SE freshly, from Steam

- Browse to C:\Program Files (x86)\Steam\SteamApps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces, and install the 3 legacy simconnect versions.

 

It's a bit of a 'chew' but really worth it in the end.

Share this post


Link to post
Share on other sites

Beware. I was informed, by a very reputable developer to NOT delete that from the registry. I have had a clean standalone installation of FSX-SE and it has both The Steam and FSX 10 registry entries. I have yet to have a FSX addon not find SE and install properly and work as far as that goes. Just asking ?

 

2h3a049.jpg

Share this post


Link to post
Share on other sites

Beware. I was informed, by a very reputable developer to NOT delete that from the registry. I have had a clean standalone installation of FSX-SE and it has both The Steam and FSX 10 registry entries. Just asking ?

 

[snipped].

 

 

Yes - a FSX:SE installation does indeed have both registry entries. ("10.0" and ("-Steam Edition").

 

My advice above is about deleting these, before a new fresh, install of FSX:SE..... not deleting searching for them and deleting them after FSX:SE is installed properly.

 

So to clarify;-

 

Once FSX:SE is installed properly; do not under any circumstances search for, and delete either of the registry entries ("10.0" or "-Steam Edition".

 

The advice to delete those files is about before you have your clean install;  so if you have uninstalled FSX and just want to install a fresh, correct installation of FSX:SE.    In that case, the registry entries should be removed before the fresh install is performed.

Share this post


Link to post
Share on other sites

Ok, thx Craig. I know it cause them some grief. They were one of the first to have an installer for FSX-SE and I was the first to purchase...and it needed fixed. :)

Share this post


Link to post
Share on other sites

Ok, thx Craig. I know it cause them some grief. They were one of the first to have an installer for FSX-SE and I was the first to purchase...and it needed fixed. :)

 

Ah ok, no probs! :smile:

 

I've edited my post above, with a clarification that the Registry Entries must only be deleted prior to a fresh install of FSX:SE, and that both entries will then re-appear after the fresh install, and not be removed.

Share this post


Link to post
Share on other sites

One other question, can i install Steam into root C:Stream and not the topical "Program Files" folder

Share this post


Link to post
Share on other sites

One other question, can i install Steam into root C:Stream and not the topical "Program Files" folder

 Yes you can. My Steam folder is on my E: drive.

Share this post


Link to post
Share on other sites

When clicking on 'Install' for your FSX:SE product in the Steam library, you get multiple install options, so pretty useful.

Share this post


Link to post
Share on other sites

ok thanks, going for a clean install of FSX-SE, so going to follow your steps for uninstalling both FSX and FSX-SE. When i uninstall FSX-SE, does that mean the whole steam folder will be un-installed also

Share this post


Link to post
Share on other sites

Gents,

 

Just jumped on the Bandwagon and purchased FSX SE but still not down loaded.

 

I have a fully working FSX on my D drive this has ASN/Aerosoft Airports UK2000 Aiports and the Aerosoft Airbus....yes I am tube flyer.

 

All works very well, but I thought well why the Steam version is on offer lets jump in..

 

So to my question I have a spare SSD Drive E if I install to this would it mess up the original? also would installing all the above again mess up the original....

 

I do not want to at this stage remove FSX...but will do if FSX SE is the better one...best to leave it run FSX and watch development. Or install to E drive?

 

Would I really see any improvement over what I have now....FSX it runs well..no stutters at all...tried P3D and the scenery was for ever stuttering...as no VS available via NI..so gave up on that..

 

Anyway...this is where I am now so any advice..

 

Many Thanks Happy New Year To All

Share this post


Link to post
Share on other sites

ok thanks, going for a clean install of FSX-SE, so going to follow your steps for uninstalling both FSX and FSX-SE. When i uninstall FSX-SE, does that mean the whole steam folder will be un-installed also

 

Good question.

 

Strangely no.   When you uninstall FSX:SE, using the Steam GUI ...... it claims FSX:SE is then 'unistalled' but if you go to the FSX:SE 'root folder' on your PC, you'll see all the folders are still there!!!!

 

So my advice would be ;-

 

  • Unistall FSX:SE using Steam.
  • Browse to C:\Program Files (x86)\Steam\SteamApps\common  ......... and delete the whole 'FSX' folder within it.
  • Perform the Registry Cleaning to remove FSX and/or FSX:SE's reg entries (covered earlier in the thread).
  • Re-install FSX:SE
  • Re-install the old Simmconnects at ;-  C:\Program Files (x86)\Steam\SteamApps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\

 

You're good to go.

Gents,

 

Just jumped on the Bandwagon and purchased FSX SE but still not down loaded.

 

I have a fully working FSX on my D drive this has ASN/Aerosoft Airports UK2000 Aiports and the Aerosoft Airbus....yes I am tube flyer.

 

All works very well, but I thought well why the Steam version is on offer lets jump in..

 

So to my question I have a spare SSD Drive E if I install to this would it mess up the original? also would installing all the above again mess up the original....

 

I do not want to at this stage remove FSX...but will do if FSX SE is the better one...best to leave it run FSX and watch development. Or install to E drive?

 

Would I really see any improvement over what I have now....FSX it runs well..no stutters at all...tried P3D and the scenery was for ever stuttering...as no VS available via NI..so gave up on that..

 

Anyway...this is where I am now so any advice..

 

Many Thanks Happy New Year To All

 

 

I think I'd probably advise you to stick with your current FSX installation.  (and move to FSX:SE once other addons are compatible and you're ready to move to it as your sole version of FSX).

 

The reason I say this is that, the notion of a 'dual install' of FSX and FSX:SE is actually a fallacy... it doesn't work!

 

Let's say you have boxed FSX installed and you then install FSX:SE......   once you install FSX:SE it 'steals' the registry entry from boxed FSX, and you will not be able to easily install any add-ons in to 'boxed FSX'.       Reversion (unistalling FSX:SE with a view to returning to using FSX) has worked for some, but for others, it has left their FSX pretty messed up.

 

For example, when I unistalled some addons from FSX:SE ...... when I then went into 'boxed FSX' I found they were also uninstalled from that sim too!

 

So my personal advice would be that if you're installing FSX:SE and already have boxed FSX installed, that you do so with the view that your boxed FSX installation is really just a back-up reference of certain elements (like the FSX.CFG) that you may want to still keep and refer to.

 

But the scenario ever with FSX:SE, is to have it as a sole install, with a Registry properly cleaned beforehand.   Parallel installs seem fine - while you're using FSX:SE - but if you try going back to your FSX installation, you could be in for a shock.

Share this post


Link to post
Share on other sites

Quick question:

I didn't read all the posts, so it may have been covered, but I was feeling lazy ;-D

 

I would just like to clarify from any of you tech savvy folks; can I have my boxed version of FSX and FSX-SE installed on the same computer without problems? And in so doing, can I run one or the other separately as I see fit?

 

Thanks in advance for any help. 

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