SDK Installation (FSX) - Troubleshooting
From FSDeveloper Wiki
A troubleshooting supplement for the SDK_Installation_(FSX) process.
Do not link directly to this document.
Only use this troubleshooting supplement -
Service Packs are available for both the FSX game and FSX SDK.
You must install the appropriate SDK SP version,
Find your installed FSX version in the FSX column,
* May also be available on magazine cover discs.
For basic installation instructions, please see the SDK_Installation_(FSX)#Installation process.
Do not attempt to install the original retail version of the Flight Simulator X SDK over an updated SDK, as unpredictable results can occur.
RTM, SP1 and SP1a documentation is supplied in html format, with each folder containing the relevant html file(s).
SP2 documentation is supplied in chm format, as a single compiled html file, fsxsdk.chm.
If your SDK is still in HTML format, rather than the Windows Help File format, (CHM),
If you had installed both FSX & SDK to their default locations,
If you had installed either FSX, or the SDK, to a non-default location,
 FSX in-game Tools menu
The Tools menu is accessed from within a flight, (not from the main GUI).
The only SDK tools available in-game, are the Object Placement Tool, (OPT), 3 Traffic tools, and the Effects tool.
All other tools are run/started from outside the sim GUI.
All changes must be made with FSX shut down.
Incorrect addon versions will prevent the in-game Tools menu from loading.
This is essential when you upgrade FSX to a newer service pack.
If the FSX Tools menu option is still not displaying,
Any changes will not be reflected till next time you start FSX.
.xml files are hidden by default.
To see dll.xml you must have enabled Show Hidden Files and Folders.
There are several example/backup dll.xml files located in the -
Ignore those, they are irrelevant.
Depending on your operation system you will find it in -
You must use a text editor, e.g. Notepad, or an XML editor.
..C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\Mission Creation Kit\object_placement.dll
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\Mission Creation Kit\object_placement.dll
 Editing Addons
<Launch.Addon> <Name>ADDONPRODUCTNAME</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>ADDONPATH\ADDONFILENAME</Path> </Launch.Addon>
 Enabling Addons
To enable each of the 3 SDK tools they need to be set as follows.
The paths must be valid, otherwise the tools wil not load.
 SDK Default Installation Location
A relative path e.g.
is relative to the FSX default location
 SDK Non-Default Installation Location
If either FSX or the SDK is installed to a non-standard location then use a full path (aka absolute path). e.g.
If you'd installed the SDK to your F: drive, then the full path would be:
 Documentation Errors
There are errors in two of the SDK's articles on -
They wrongly quote the dll.xml header's ManualLoad section.
All other SDK articles appear to be correct.
The correct header is -
<?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad>
When you install the SDK, or any SDK service pack,
Did you ever say no ?
Please open your fsx.cfg in a text editor.
Look for the [Trusted] section
Example entries, (from an XP system) -
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\Object_Placement.dll.LONGSTRING=1 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll.LONGSTRING=1 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll.LONGSTRING=1
Where LONGSTRING is a 'meaningless' alphanumeric string, (e.g. elqluuzchciqbqtwawurawalhakbwatuaiiwrrti).
The final value should be =1
Fire up FSX. Do the tools now display ?
 Vista users
If the 1's not sticking, it's because Vista treats all .cfg files as being system files.
It opens a copy, and then saves your edited/changed file to somewhere else, (personal folders).
Next time you open fsx.CFG, Vista is giving you the original.
 Still having problems ?
DO NOT post any help request in the FSDeveloper forums
We require that information about your system.
Now check your ADE report for the following lines, (separated by other data) -
FSX Version: 10.0.VERSION_NUMBER.0 (FSX-PRODUCT_CODE)
BGLComp Version: 10.0.VERSION_NUMBER.0 (fsx-PRODUCT_CODE)