Fix the FSX: Steam Edition Object Placement Tool by correcting SDK, dll.xml, SimConnect and permissions problems with edition-specific steps.
The Object Placement Tool usually fails in FSX: Steam Edition because the SDK module does not match the simulator, its dll.xml entry points to the wrong folder, or a required legacy SimConnect runtime is missing. Install the Steam-compatible SDK or tool, correct the active configuration file, then test it after loading a flight.
What stops the Object Placement Tool from loading?
Most failures come from mixing boxed-FSX instructions with the different paths and configuration behaviour used by FSX: Steam Edition.
- Wrong SDK build: an Object Placement DLL taken from an original, unpatched Deluxe SDK may not load correctly in Steam Edition.
- Wrong configuration folder: Steam Edition may use either
FSXorFSX-SEunder the Microsoft application-data folder, particularly on a computer that has also had boxed FSX installed. - Bad DLL path: many old instructions point to
Microsoft Games, while the actual SDK is inside the Steam library. - Missing SimConnect interface: the simulator can run normally while an older SDK tool still lacks the particular side-by-side SimConnect runtime it expects.
- Blocked or rejected module: Windows may block a downloaded DLL, or FSX may remember that permission to load it was denied.
- Testing from the opening screen: the SDK tool normally becomes available only after a flight has loaded.
Our explanation of how boxed FSX and Steam Edition use different paths and registry entries covers why copying an old installation guide exactly often fails.
How do I fix the Object Placement Tool in FSX: Steam Edition?
The reliable fix is to establish one matching tool installation, point the active dll.xml file at it, and repair its SimConnect dependency.
- Back up the configuration files. Close FSX and copy any existing
dll.xmlandfsx.cfgfiles somewhere safe before editing them. - Install the correct SDK or utility. In Steam, filter the Library to show Tools and install the SDK associated with FSX: Steam Edition. Avoid combining its files with an older boxed SDK. If using a separate package, consult our Object Placement utility package and installation notes for its requirements and newer-Windows caveats.
- Find the configuration folder FSX actually uses. Open
%APPDATA%\Microsoft\and check theFSXandFSX-SEfolders. Launch FSX, close it again, and identify which copy offsx.cfgreceived the newest modification time. Edit thedll.xmlbeside that file. - Correct the launch entry. The Object Placement module belongs in
dll.xml, notexe.xml. Its entry should follow this pattern, replacing the example with the full path to the installed DLL:<Launch.Addon><Name>Object Placement Tool</Name><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Path>C:\full\path\object_placement.dll</Path></Launch.Addon>. Place the block inside the existing document before its closing root tag; do not overwrite entries required by other add-ons. - Allow the module to load. Open the DLL’s Windows properties and use
Unblockif that option appears. When FSX asks whether to run or trust the software, approve it. If permission was denied previously, back upfsx.cfgand remove only the Object Placement Tool’s line from its[Trusted]section so FSX can ask again. - Install or repair legacy SimConnect. Use the Microsoft SimConnect installers supplied with the Steam SDK or tool, normally found in its SimConnect SDK or legacy-interface area. These versions install side by side. Do not copy an arbitrary
SimConnect.dllinto the FSX, Windows orSysWOW64folder. For connection failures, work through our practical SimConnect connection checks. - Load a flight before opening the tool. Start FSX through Steam, load into the cockpit and wait for the flight to initialise. Press
Altif the menu bar is hidden, then look for the Object Placement entry under the developer or Tools menu. A separate external utility should also be started after the flight loads and at the same Windows privilege level as FSX.
FSX: Steam Edition remains a 32-bit application even on 64-bit Windows, so installation under Program Files (x86) is normal. Moving DLLs into Windows system folders does not make them 64-bit compatible and often creates a second problem.
What does each failure symptom mean?
| Symptom | Likely cause | Next check |
|---|---|---|
| No Tools entry after loading a flight | Wrong dll.xml, incorrect path or disabled module | Identify the active FSX/FSX-SE folder and verify the DLL exists at the stated path |
| FSX asks for permission, then the tool vanishes | Trust was denied or the module is blocked | Unblock the DLL and reset only its saved trust entry |
| Tool reports that it cannot connect | Missing legacy SimConnect or no flight loaded | Repair the supplied SimConnect runtimes and retry from an active flight |
| FSX closes while loading the module | Incompatible SDK DLL, damaged dependency or malformed XML | Remove the launch entry, confirm FSX runs, then reinstall a matching tool build |
| All DLL add-ons disappear from the menu | Invalid XML structure | Restore the backup and add the launch block without creating a second root element |
Does the boxed FSX Object Placement Tool work in Steam Edition?
A boxed-FSX Object Placement Tool can sometimes work, but the original RTM SDK module is not the best choice for Steam Edition.
Use the Steam-supplied SDK where possible. If a project requires the boxed SDK, its SDK updates must match the corresponding simulator generation; do not apply boxed FSX simulator service packs over Steam Edition. Our guide to which FSX service packs belong to each edition explains that boundary.
Why do placed objects disappear after restarting FSX?
Objects disappear because placing them in the editor is not the same as installing permanent scenery.
For ordinary scenery, save the placement source, compile it with the matching SDK scenery compiler, and install the resulting BGL in an enabled scenery area. Mission projects instead retain their placements as part of the mission source. Placing an XML source file alone in Addon Scenery will not make those objects permanent.