Why doesn’t the Object Placement Tool work in FSX: Steam Edition?
Object Placement Tool not working in FSX: Steam Edition? Fix a missing Tools menu, wrong dll.xml path, SDK mismatch, trust and SimConnect errors.
The Object Placement Tool in FSX: Steam Edition usually fails because its SDK DLL does not match the simulator, FSX is reading the wrong dll.xml, the path to object_placement.dll is invalid, or the module was blocked. Use the Steam-compatible SDK, repair the active configuration entry, then test after loading a flight.
Object Placement Tool が出ない: why is the Tools menu missing?
If the tool does not appear (出ない) at all, FSX has either failed to load its module or hidden the menu bar; compiling or saving scenery is not yet the problem.
- No flight is loaded: the Object Placement Tool is intended for use inside an active flight, not from the opening screen.
- The menu bar is hidden: press
Altafter entering the cockpit, then look forTools > Object Placement Tool. - FSX is reading another configuration folder: Steam Edition can use either
FSXorFSX-SEunder%APPDATA%\Microsoft\, especially on a PC that has also had boxed FSX installed. - The XML is invalid: a missing closing tag, duplicate root section or misplaced launch block can prevent every module in
dll.xmlfrom loading. - The DLL does not match the simulator: an initial-release boxed-FSX SDK module should not be mixed with the Steam Edition SDK.
- The module was rejected: Windows may block a downloaded DLL, or FSX may have saved a previous decision not to trust it.
- A legacy dependency is unavailable: FSX itself can run while an SDK component or external utility still lacks the particular SimConnect runtime it expects.
A mistake we see constantly is editing the FSX-SE copy of dll.xml while the simulator is actually reading FSX, or vice versa. If all DLL-based menu entries have disappeared, use our checks for missing FSX: Steam Edition add-on menus to inspect the shared XML and trust failures.
First identify which Object Placement Tool you have
The official SDK module and an external placement utility are repaired differently.
| Tool type | How it runs | What to check |
|---|---|---|
| FSX SDK Object Placement Tool | object_placement.dll loads inside FSX and adds a Tools menu entry | The SDK version, active dll.xml, DLL path, trust and in-process dependencies |
| External placement utility | A separate program opens outside FSX and usually connects to a running flight | Its supplied installation instructions, SimConnect runtime and whether both programs run at the same Windows privilege level |
Do not add an external program to dll.xml unless its own documentation explicitly supplies a DLL launch entry. If you need an alternative to the SDK module, our FSX Object Placement utility package and installation files provide a separate option; keep its files and instructions distinct from the Microsoft SDK installation.
How do I fix the FSX: Steam Edition Object Placement Tool?
For the official SDK tool, the reliable repair is to locate the configuration FSX actually uses, install a matching module and correct that module’s launch entry.
- Find the active FSX configuration folder. Start FSX: Steam Edition, let it reach the opening screen, then close it normally. Open
%APPDATA%\Microsoft\and inspect bothFSXandFSX-SE. The folder whosefsx.cfghas just been updated is normally the active one. Back up itsfsx.cfganddll.xmlbefore changing anything. - Install the Steam-compatible SDK files. Use the SDK supplied for FSX: Steam Edition rather than copying
object_placement.dllfrom an old boxed installation. Keep boxed and Steam SDK trees separate on a dual-installation PC. Our FSX SDK installation and troubleshooting guide covers the Steam location, edition matching and permission checks. - Confirm that the DLL exists. Search the installed SDK tree for
SDK\Mission Creation Kit\object_placement.dll. Do not assume an old guide’sMicrosoft Gamespath applies to a Steam library installed elsewhere. - Repair the launch entry. The module belongs in
dll.xml, notexe.xml. Its block must be inside the existing XML document and contain<Disabled>False</Disabled>,<ManualLoad>False</ManualLoad>and a path ending in the installedobject_placement.dll. An absolute path such asC:\full\path\object_placement.dllavoids ambiguity. Do not put quotation marks around the path, and do not replace launch blocks required by other add-ons. - Repair rather than guess if dll.xml is absent. A lone
<Launch.Addon>fragment is not a complete XML file. Reinstall or repair the SDK, or create the full document carefully using the correct root element. Edit it with a plain-text editor, not a word processor. - Reset blocking and trust. Open the DLL’s Windows properties and select
Unblockif that option is present. If FSX previously rejected it, find the[Trusted]section in the activefsx.cfgand remove only the line that referencesobject_placement.dll. Restart FSX and approve its software and trust prompts. - Repair legacy dependencies only after checking the path. If the entry is correct but the module still will not load, run the legacy SimConnect installers supplied with the Steam SDK or FSX installation. SimConnect versions install side by side, so an older component does not replace the simulator’s main interface. Never copy an arbitrary
SimConnect.dllinto the FSX or Windows system folders. - Test from a clean flight. Load a default aircraft at a default airport and wait for the cockpit to initialise. Press
Altif necessary, then openTools > Object Placement Tool. FSX must be restarted after everydll.xmlchange. - Isolate a start-up crash. Close FSX and temporarily set only the Object Placement Tool entry to
<Disabled>True</Disabled>. If FSX then starts normally, the DLL build or one of its dependencies is incompatible. Restore a matching SDK copy instead of moving the DLL into a Windows folder.
FSX: Steam Edition is a 32-bit application even on 64-bit Windows. Its SDK module must therefore be compatible with the simulator’s 32-bit process; installing it under Program Files (x86) is normal.
What does each Object Placement Tool failure mean?
The symptom usually identifies whether the fault is in module loading, dependency handling or the scenery workflow that follows.
| Symptom | Likely cause | Next check |
|---|---|---|
| No Tools menu after loading a flight | Wrong active dll.xml, disabled module or invalid DLL path | Compare the modification times of FSX and FSX-SE, then confirm the file exists at the configured path |
| No menu and no trust prompt | FSX never read the launch entry, or the XML is malformed | Verify the active configuration folder and restore the last valid XML backup |
| A trust prompt appeared, but the tool still vanished | Trust was denied, the DLL was blocked or a dependency failed afterwards | Unblock the file and remove only its saved [Trusted] entry before retrying |
| All DLL-based menu entries disappeared | Broken dll.xml structure | Look for an unclosed tag, duplicate XML document or launch block outside the root element |
| FSX closes while starting | Incompatible SDK DLL or failed in-process dependency | Disable the Object Placement Tool entry, confirm FSX starts, then reinstall a matching module |
| An external utility reports that it cannot connect | No active flight, missing legacy SimConnect runtime or mismatched Windows privileges | Load a flight, repair the utility’s supplied runtime and run both programs under the same user level |
| The tool works, but placements vanish after restarting | The placement source was never compiled and installed as scenery | Compile the source into a BGL and add it to 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 is the correct choice for FSX: Steam Edition.
The original boxed Deluxe SDK was updated alongside the boxed simulator’s service packs and Acceleration release. Mixing its initial DLL with Steam Edition can cause a missing menu or a start-up crash even though the filename is identical. Do not install boxed-FSX simulator service packs over Steam Edition, and do not let a boxed SDK installer overwrite the Steam SDK tree.
On a PC with both editions installed, retain separate SDK folders and separate configuration files. Check the actual path in each edition’s dll.xml rather than relying on registry entries created by whichever simulator was installed last.
Why do placed objects disappear after restarting FSX?
Placed objects disappear because the editor’s source data is not permanent scenery until it has been compiled and installed.
For normal scenery, save the placement XML, compile it with the matching SDK scenery compiler, and put the resulting BGL in the scenery subfolder of an enabled scenery area, such as Addon Scenery\scenery. Keep any separate library BGL containing the selected model active as well. Mission placements instead belong in the mission project’s source.
Our guide to placing and saving scenery objects in FSX covers the editor controls, compilation step and checks to make when the Tools entry is missing.
Why is a placed object invisible even though the tool opens?
An invisible object usually indicates a placement or library problem rather than a failed Object Placement Tool.
- Confirm that the library BGL containing the model is installed in an active scenery area.
- Check the object’s altitude and whether the placement uses height above ground or elevation above sea level; an incorrect choice can put it below the surface.
- Set the object’s image-complexity value no higher than the scenery-complexity setting used in FSX.
- Make sure the compiled placement BGL is in a
sceneryfolder, not loose in the parent scenery-area folder.