Why doesn’t the Object Placement Tool work in FSX: Steam Edition?
Fix the Object Placement Tool in FSX: Steam Edition when it does not appear, crashes the simulator or fails to save placed scenery.
The Object Placement Tool in FSX: Steam Edition usually fails because FSX is reading the wrong dll.xml, its launch path is invalid, the DLL is blocked, or the installed SDK module does not match the simulator. Load a flight, verify the active configuration folder, correct the module entry, then accept the trust prompt.
Why does the Object Placement Tool not appear in the Tools menu?
If the Object Placement Tool does not show in the menu, FSX has not loaded its module or the simulator menu bar is hidden.
- No flight is running: load an aircraft at an airport before looking for the tool. It is not available from the opening screen.
- The menu bar is hidden: press
Altin the cockpit, then look forTools > Object Placement Tool. - FSX is reading another profile: Steam Edition can use either
%APPDATA%\Microsoft\FSXor%APPDATA%\Microsoft\FSX-SE, particularly on a computer that has also had boxed FSX installed. - The launch entry is disabled or invalid: a wrong path, malformed XML or misplaced
<Launch.Addon>block stops the DLL from loading. - The DLL is missing or incompatible: copying an Object Placement Tool from a different boxed-FSX SDK release can produce a missing menu or a start-up crash.
- The module was blocked: Windows may mark the DLL as downloaded, or FSX may have stored an earlier decision not to trust it.
A mistake we see repeatedly is editing the FSX-SE copy of dll.xml while the simulator is using FSX, or vice versa. If several DLL-based menu entries have disappeared together, follow our diagnostic checks for missing FSX module menus; that usually points to a shared XML or trust problem rather than separate add-on failures.
Identify which Object Placement Tool you are using
The official SDK module and an external placement program use different loading methods, so they require different fixes.
| Tool type | How it runs | Primary checks |
|---|---|---|
| FSX SDK Object Placement Tool | object_placement.dll loads inside the 32-bit FSX process and adds a Tools menu entry | SDK edition, active dll.xml, DLL path, XML structure and trust |
| External placement utility | A separate Windows program connects to a flight running in FSX | Its own installation instructions, SimConnect requirements and matching Windows privilege levels |
Do not put an external executable in dll.xml unless its documentation explicitly supplies a separate DLL module. If the SDK tool remains unsuitable, our downloadable external FSX object-placement utility is a separate option; do not mix its files or instructions with the Microsoft SDK module.
How do I fix the FSX: Steam Edition Object Placement Tool?
The reliable repair is to find the configuration FSX actually reads, install the matching Steam Edition SDK module and correct its complete launch entry.
- Test inside a clean flight. Load a default aircraft at a default airport and wait until the cockpit has initialised. Press
Altto expose the menu bar. This rules out the common mistake of checking from the opening screen. - Find the active configuration folder. Close FSX normally, open
%APPDATA%\Microsoft\and inspect bothFSXandFSX-SEif they exist. The folder whosefsx.cfgwas updated when the simulator closed is normally the active one. - Back up the configuration. Copy the active
dll.xmlandfsx.cfgsomewhere safe before editing them. Do not assume that deletingdll.xmlwill make FSX recreate all third-party entries. - Confirm that the correct SDK is installed. Use the SDK distributed for FSX: Steam Edition, not an initial boxed-FSX SDK copied from another installation. Our Steam Edition SDK installation checklist explains edition matching, installation paths, permissions and repair options.
- Locate the actual module. Search the Steam Edition SDK tree for
SDK\Mission Creation Kit\object_placement.dll. A Steam library may be on any drive, so a path copied from an old guide is rarely dependable. If the DLL is absent, repair the SDK or verify the installed FSX files rather than downloading an unrelated copy. - Correct the launch entry. The Object Placement Tool belongs in
dll.xml, notexe.xml. Its<Launch.Addon>block must be inside the existing<SimBase.Document>root and contain<Disabled>False</Disabled>,<ManualLoad>False</ManualLoad>and a<Path>ending in the installedobject_placement.dll. An absolute path avoids ambiguity. Do not put quotation marks around it, even when the folder names contain spaces. - Validate the whole XML document. A lone launch block is not a valid
dll.xml. Check for one XML declaration, one root document, matching opening and closing tags, and every launch block inside that root. Use a plain-text editor rather than a word processor. - Reset blocking and trust. Open the DLL's Windows properties and use
Unblockif that option appears. If FSX previously rejected the module, remove only the[Trusted]entry in the activefsx.cfgthat namesobject_placement.dll. Restart FSX and approve the prompts only when the path points to the SDK copy you intended to install. - Restart and retest. FSX must be closed and reopened after every
dll.xmlchange. Load the clean flight again and checkTools > Object Placement Tool. If there is no trust prompt on a clean first attempt, FSX probably did not read that launch entry. - Isolate a start-up crash. Set only this module's entry to
<Disabled>True</Disabled>and restart FSX. If the simulator then opens, reinstall a matching SDK module and its supplied dependencies. External utilities that cannot connect may require a legacy SimConnect runtime installed alongside the existing versions; never replace system files with an arbitrarySimConnect.dll.
FSX: Steam Edition is a 32-bit application even on 64-bit Windows. Its in-process Object Placement Tool must therefore be compatible with a 32-bit process, and finding SDK components under Program Files (x86) is normal.
Which common fixes should I avoid?
Random DLL replacement and broad configuration deletion usually create additional faults without repairing the original module-loading problem.
- Do not copy
object_placement.dllorSimConnect.dllinto Windows system folders. - Do not install boxed-FSX simulator service packs over FSX: Steam Edition.
- Do not erase the entire
[Trusted]section when only one module needs to be reset. - Do not replace a working
dll.xmlwith a single launch fragment; that removes other modules and leaves an invalid document. - Do not use administrator mode as a universal fix. It cannot repair a wrong path or malformed XML, and an external utility may fail to connect if it runs at a different privilege level from FSX.
What does each Object Placement Tool failure mean?
The visible symptom usually identifies whether the fault lies in the menu, XML configuration, module build or later scenery workflow.
| Symptom | Likely cause | Next check |
|---|---|---|
| No Tools menu after loading a flight | Hidden menu bar, wrong active dll.xml, disabled entry or invalid path | Press Alt, compare the FSX and FSX-SE folders, then confirm the configured file exists |
| No trust prompt on a first clean attempt | FSX never read the entry, or the XML is malformed | Verify the active profile and restore the last known valid XML backup |
| A trust prompt appeared, but the tool did not remain available | Trust was denied, Windows blocked the DLL or loading failed afterwards | Unblock the DLL and reset only its saved trusted entry |
| All DLL-based menus disappeared | Broken dll.xml structure | Look for an unclosed tag, duplicate root document or launch block outside the root |
| FSX closes during start-up | Incompatible DLL or failed in-process dependency | Disable this launch entry, confirm FSX starts, then repair the matching SDK |
| An external utility cannot connect | No active flight, missing legacy SimConnect runtime or mismatched privilege levels | Load a flight, repair the supplied runtime and run both programs at the same user level |
| The editor works, but placements vanish later | The source was not compiled and installed as scenery | Create a BGL and place it in an enabled scenery area |
Does the boxed-FSX Object Placement Tool work in Steam Edition?
A boxed-FSX Object Placement Tool may load when its SDK level happens to be compatible, but the Steam Edition SDK module is the correct and safer choice for FSX: Steam Edition.
The boxed Deluxe SDK was updated alongside different simulator service levels, while Steam Edition uses its own supported installation. Identical filenames do not prove that two DLL builds are interchangeable. A mismatched copy may simply omit the menu, or it may close FSX while the simulator is starting.
On a computer with both editions installed, retain separate SDK directories and configuration folders. Check the full path in each edition's dll.xml; do not rely on a registry path left by whichever edition was installed last.
Why do placed objects disappear or not show after restarting FSX?
Placed objects disappear after restarting because editor source data is not permanent scenery until it has been compiled into a BGL and installed in an active scenery area.
For ordinary scenery, save the placement XML, compile it with the matching SDK scenery compiler, and place the resulting BGL in the scenery subfolder of an enabled scenery area. The library BGL containing the selected model must also remain active. Mission placements instead belong in the mission project's source and build process.
Our guide to placing, compiling and installing FSX scenery objects covers the workflow after the editor loads.
Why is a placed object invisible even though the tool opens?
An invisible object indicates a scenery-library or placement setting problem, not a failed Object Placement Tool module.
- Confirm that the library BGL containing the model is installed in an enabled scenery area.
- Check the coordinates, altitude and whether the placement uses height above ground or elevation above sea level; the wrong choice can put an object underground.
- Set the object's image-complexity requirement no higher than the Scenery Complexity setting selected in FSX.
- Place the compiled BGL inside the scenery area's
scenerysubfolder, not loose in its parent folder. - Restart FSX after adding or replacing a BGL so that the simulator reloads the scenery database.