Well, the FSR Phenom FBO placer has shown that a simple object placer for MSFS2024 is definitely possible, bypassing the vastly overly complicated built in Scenery Editor. Wouldn't it be nice to have something similar that would work with all of the object libraries and allow us to place stuff on airports with a minimum of hair pulling?

Open letter to someone out there who may know how to do this:

PLEASE do it! I for one would pay to have a program like this, and I'm sure I'm not alone in this.

Make it so!

Discuss...

I don't know if that's really possible on a wide scale. The SDK is deeply linked to the core sim...

Pretty sure you can place "SimObjects" (as opposed to "Scenery" objects) using Simconnect. That's how AI traffic gets injected. No reason a SimObject can't be static, and it wouldn't surprise me that this is how they add the FBO. Utilities like WAMA and Campout do that as well. Having said that, I have no answer to the OP, other than to say it shouldn't be that hard for someone who knows their way around Simconnect.

I dream about having something like this!

I have no inclination or energy to learn the 2024 SDK and scenery editor, but as said above, FSReborn have unambiguously shown that an intuitive, user-friendly, in-sim method of placing persistent scenery is possible.

All that would need to be added to what FSR have done is the ability to select a wider range of objects, most likely organised by category.

We see so so many duplicated, repetitive mods and addon utilities on FS.TO for MSFS, that all do the same thing; 47 x landing rate mods, 87 x sim rate tools, 18 million announcement mods ...... what we really need is something groundbreaking like this.

Raul has all the core architecture and base coding there - FSR could develop a dedicated object placer addon and I bet it would sell wildly. I know it would never happen though.

Edited May 24May 24 by JYW

Parallel 42's Campout utility comes with camping-related objects that you can place wherever and it saves that state.

FS Fire sounds like it has an "any object in the sim" placer feature:

Simobject (Props) Scene Builder

Browse the MSFS simobject catalog — hundreds of default objects, direct user entry, or MSFS 2024 file system scanned simobjects — spanning aircraft, ground vehicles, boats, animals, humans, and landmarks. Spawn any object by map-click or coordinate, rotate its heading, and drag it to reposition. Save and load entire scenes including fire layouts, with optional prop-only or fires-only saves.

Edited May 24May 24 by Magenta Line

On 5/21/2026 at 1:23 PM, b1bmsgt said:

Well, the FSR Phenom FBO placer has shown that a simple object placer for MSFS2024 is definitely possible, bypassing the vastly overly complicated built in Scenery Editor. Wouldn't it be nice to have something similar that would work with all of the object libraries and allow us to place stuff on airports with a minimum of hair pulling?

Open letter to someone out there who may know how to do this:

PLEASE do it! I for one would pay to have a program like this, and I'm sure I'm not alone in this.

Make it so!

Discuss...

Or even just to make your airport from scratch, I'd love to make the old Airport where I grew up was, now under where Nissan UK is built.

On 5/21/2026 at 5:23 AM, b1bmsgt said:

Well, the FSR Phenom FBO placer has shown that a simple object placer for MSFS2024 is definitely possible, bypassing the vastly overly complicated built in Scenery Editor. Wouldn't it be nice to have something similar that would work with all of the object libraries and allow us to place stuff on airports with a minimum of hair pulling?

Open letter to someone out there who may know how to do this:

PLEASE do it! I for one would pay to have a program like this, and I'm sure I'm not alone in this.

Make it so!

Discuss...

No need to pay for a program. You already have it in MSFS 2024. Just ask AI to give you instructions on how to do it.

Example:
Request: "Show very detailed instruction on how to place a static object using freeware object libraries in MSFS 2024"

Reply:
----
You’re basically trying to do what every scenery tweaker wants: drop a nice static object from a freeware library exactly where you want it in MSFS 2024, and have it show up reliably. Here’s a full, end‑to‑end workflow—from installing the library to placing the object and building your package.

01

Install the freeware object library correctly

Foundation

MSFS 2024 only sees objects that are inside properly structured packages mounted via the Community folder.

Place the library folder into your MSFS 2024\Community directory

• Download the freeware object library (usually from flightsim.to or a forum link)

• Unzip it and check that the top-level folder contains manifest.json and layout.json

• Copy that entire folder into your Community folder (not inside another add-on)

• Restart MSFS 2024 if it was running so the package is mounted by the Virtual File System

02

Enable Developer Mode in MSFS 2024

Developer Mode unlocks the in-sim SDK tools, including the Scenery Editor you’ll use to place objects.

Main menu → Options → General → Developers → Developer Mode = ON

• From the main menu, open Options → General

• Go to the Developers tab

• Turn Developer Mode to ON

• A small Dev Mode menu bar will appear at the top of the screen

03

Create a new scenery project

Project Setup

All placed objects must live inside a scenery package (project) so they can be built and loaded as an add-on.

Dev Mode menu → Project Editor → File → New Project

• Start a flight near the area where you want to place the object

• On the Dev Mode bar, click Project Editor

• In Project Editor, choose File → New Project

• Enter a Project Name (e.g., my-static-objects)

• Set a Project Folder (a working folder outside Community, e.g., D:\MSFS_Projects\my-static-objects)

• Click Create and then Open in Editor if prompted

04

Add a scenery package and asset group

Your project needs a scenery package with a scenery asset group where the placed objects will be stored.

Project Editor → New Package → Add Asset Group → Type: Scenery

• In Project Editor, click New Package (or edit the default one created)

• Give the package a name (e.g., my-static-objects-scenery)

• Set Content Type to Scenery

• Click Add Asset Group

• Choose Type: Scenery

• Set a Title (e.g., my_static_objects_area)

• Set a Folder (e.g., scenery\my_static_objects_area)

• Click Create and then Save the project (Ctrl+S in Project Editor)

05

Open the Scenery Editor for your package

The Scenery Editor is where you visually place and manipulate objects in the world.

Dev Mode menu → Scenery Editor → Load your scenery asset group

• On the Dev Mode bar, click Scenery Editor

• If prompted, select your scenery asset group from the list

• The Scenery Editor window appears, usually docked on the left/right

• Ensure your scenery package is active (checkbox ticked) in the Scenery Editor content list

06

Move the camera to your placement location

You want the camera roughly over the spot where the static object will go before placing it.

• Use normal sim controls to fly or slew to the target area

• You can use Drone Camera for precise positioning

• In the Scenery Editor, enable Developer Camera if you prefer (View menu)

• Zoom in until you clearly see the ground reference where the object should sit

07

Locate the freeware library objects in the Objects list

Key Step

Freeware library models appear as scenery objects under their package name in the Objects window.

Scenery Editor → Objects window → Filter or scroll to the library package

• In the Scenery Editor, open the Objects window (if hidden, enable it from the editor’s View menu)

• Set Object Type to Scenery Objects

• Use the search/filter box to type part of the library name or object name

• Hover an object entry: the tooltip or properties will show the Package it comes from (e.g., the freeware library’s package name)

• Confirm you’re seeing objects from the intended third-party library, not just default Asobo assets

08

Activate one-click placing or Add mode

You can either click once per object placement or use the Add button and then click in the world.

• In the Objects window, select the desired object from the list

• Option 1: Click Add to enter placement mode, then click in the world where you want it

• Option 2: Enable One-Click Placing (if available) so each click in the world drops an instance

• Make sure Snap To Ground is enabled in the object properties so it sits on terrain by default

09

Place the static object in the world

This is the actual drop of the object instance into your scenery asset group.

• With the object selected and placement mode active, move the mouse over the terrain

• Left-click to place the object at the cursor location

• The object appears and is also listed in the Scenery Contents List for your package

• If you misplace it, you can undo (Ctrl+Z) or select and delete it

10

Adjust position, rotation, and scale precisely

Use the gizmos to fine-tune the object’s location, heading, and size for a realistic fit.

• Select the placed object in the world or from the Content List

• Use the Translate Gizmo (arrows) to nudge it along X/Y/Z

• Use the Rotation Gizmo to align it with roads, buildings, or other references

• Use the Scale Gizmo if appropriate (some objects scale well, others may not)

• In the Properties panel, verify Snap To Ground is on; disable it if you need to float or sink the object slightly

• Optionally click Assign Instance ID if you need a unique GUID for scripting or missions

11

Verify the object’s source package and dependencies

Licensing Awareness

Before publishing, you must know which package the object comes from to respect licensing and dependencies.

• With the object selected, check the Package field in the Properties panel

• Confirm it shows the freeware library’s package name, not some other add-on

• Note this package name for your documentation/readme (users must install that library)

• If you plan to upload your scenery, ensure the library’s license allows referencing its objects (most do) but not redistributing its files

12

Save, build, and test your scenery package

Finalization

Building the package compiles your placed objects into a redistributable scenery add-on.

Project Editor → Build All → Copy built package to Community (if needed)

• In Scenery Editor, click Save Scenery (disk icon) to write changes to your project files

• In Project Editor, click Save to ensure the project and package definitions are updated

• Click Build All (or build your specific package) and wait for the build to complete

• The compiled package appears in your project’s Packages or Packages\Community folder

• If necessary, copy that built package into your main MSFS 2024 Community folder

• Restart the sim or reload the project, then load a normal flight at the location and confirm the static object appears as expected

13

Document the required freeware library for users

If you share your scenery, users must know they need the same object library installed.

• In your scenery’s readme or product page, list the freeware object library as a required dependency

• Include the exact package name and a download link (e.g., flightsim.to page)

• Clarify that you do not include the library’s files—users must download and install it separately

• Optionally mention that objects are used as static scenery only (no simulation/physics) so users know what to expect

In practice, once you’ve done this once or twice, the “flow” becomes:

• Install library → confirm it mounts in Community

• Create/update your scenery project → open Scenery Editor

• Pick object from the library’s package → drop, tweak, save

• Build package → test in a normal flight → publish with clear dependency notes

1 hour ago, bofhlusr said:

No need to pay for a program. You already have it in MSFS 2024. Just ask AI to give you instructions on how to do it.

Example:
Request: "Show very detailed instruction on how to place a static object using freeware object libraries in MSFS 2024"

Reply:
----
You’re basically trying to do what every scenery tweaker wants: drop a nice static object from a freeware library exactly where you want it in MSFS 2024, and have it show up reliably. Here’s a full, end‑to‑end workflow—from installing the library to placing the object and building your package.

01

Install the freeware object library correctly

Foundation

MSFS 2024 only sees objects that are inside properly structured packages mounted via the Community folder.

Place the library folder into your MSFS 2024\Community directory

• Download the freeware object library (usually from flightsim.to or a forum link)

• Unzip it and check that the top-level folder contains manifest.json and layout.json

• Copy that entire folder into your Community folder (not inside another add-on)

• Restart MSFS 2024 if it was running so the package is mounted by the Virtual File System

02

Enable Developer Mode in MSFS 2024

Developer Mode unlocks the in-sim SDK tools, including the Scenery Editor you’ll use to place objects.

Main menu → Options → General → Developers → Developer Mode = ON

• From the main menu, open Options → General

• Go to the Developers tab

• Turn Developer Mode to ON

• A small Dev Mode menu bar will appear at the top of the screen

03

Create a new scenery project

Project Setup

All placed objects must live inside a scenery package (project) so they can be built and loaded as an add-on.

Dev Mode menu → Project Editor → File → New Project

• Start a flight near the area where you want to place the object

• On the Dev Mode bar, click Project Editor

• In Project Editor, choose File → New Project

• Enter a Project Name (e.g., my-static-objects)

• Set a Project Folder (a working folder outside Community, e.g., D:\MSFS_Projects\my-static-objects)

• Click Create and then Open in Editor if prompted

04

Add a scenery package and asset group

Your project needs a scenery package with a scenery asset group where the placed objects will be stored.

Project Editor → New Package → Add Asset Group → Type: Scenery

• In Project Editor, click New Package (or edit the default one created)

• Give the package a name (e.g., my-static-objects-scenery)

• Set Content Type to Scenery

• Click Add Asset Group

• Choose Type: Scenery

• Set a Title (e.g., my_static_objects_area)

• Set a Folder (e.g., scenery\my_static_objects_area)

• Click Create and then Save the project (Ctrl+S in Project Editor)

05

Open the Scenery Editor for your package

The Scenery Editor is where you visually place and manipulate objects in the world.

Dev Mode menu → Scenery Editor → Load your scenery asset group

• On the Dev Mode bar, click Scenery Editor

• If prompted, select your scenery asset group from the list

• The Scenery Editor window appears, usually docked on the left/right

• Ensure your scenery package is active (checkbox ticked) in the Scenery Editor content list

06

Move the camera to your placement location

You want the camera roughly over the spot where the static object will go before placing it.

• Use normal sim controls to fly or slew to the target area

• You can use Drone Camera for precise positioning

• In the Scenery Editor, enable Developer Camera if you prefer (View menu)

• Zoom in until you clearly see the ground reference where the object should sit

07

Locate the freeware library objects in the Objects list

Key Step

Freeware library models appear as scenery objects under their package name in the Objects window.

Scenery Editor → Objects window → Filter or scroll to the library package

• In the Scenery Editor, open the Objects window (if hidden, enable it from the editor’s View menu)

• Set Object Type to Scenery Objects

• Use the search/filter box to type part of the library name or object name

• Hover an object entry: the tooltip or properties will show the Package it comes from (e.g., the freeware library’s package name)

• Confirm you’re seeing objects from the intended third-party library, not just default Asobo assets

08

Activate one-click placing or Add mode

You can either click once per object placement or use the Add button and then click in the world.

• In the Objects window, select the desired object from the list

• Option 1: Click Add to enter placement mode, then click in the world where you want it

• Option 2: Enable One-Click Placing (if available) so each click in the world drops an instance

• Make sure Snap To Ground is enabled in the object properties so it sits on terrain by default

09

Place the static object in the world

This is the actual drop of the object instance into your scenery asset group.

• With the object selected and placement mode active, move the mouse over the terrain

• Left-click to place the object at the cursor location

• The object appears and is also listed in the Scenery Contents List for your package

• If you misplace it, you can undo (Ctrl+Z) or select and delete it

10

Adjust position, rotation, and scale precisely

Use the gizmos to fine-tune the object’s location, heading, and size for a realistic fit.

• Select the placed object in the world or from the Content List

• Use the Translate Gizmo (arrows) to nudge it along X/Y/Z

• Use the Rotation Gizmo to align it with roads, buildings, or other references

• Use the Scale Gizmo if appropriate (some objects scale well, others may not)

• In the Properties panel, verify Snap To Ground is on; disable it if you need to float or sink the object slightly

• Optionally click Assign Instance ID if you need a unique GUID for scripting or missions

11

Verify the object’s source package and dependencies

Licensing Awareness

Before publishing, you must know which package the object comes from to respect licensing and dependencies.

• With the object selected, check the Package field in the Properties panel

• Confirm it shows the freeware library’s package name, not some other add-on

• Note this package name for your documentation/readme (users must install that library)

• If you plan to upload your scenery, ensure the library’s license allows referencing its objects (most do) but not redistributing its files

12

Save, build, and test your scenery package

Finalization

Building the package compiles your placed objects into a redistributable scenery add-on.

Project Editor → Build All → Copy built package to Community (if needed)

• In Scenery Editor, click Save Scenery (disk icon) to write changes to your project files

• In Project Editor, click Save to ensure the project and package definitions are updated

• Click Build All (or build your specific package) and wait for the build to complete

• The compiled package appears in your project’s Packages or Packages\Community folder

• If necessary, copy that built package into your main MSFS 2024 Community folder

• Restart the sim or reload the project, then load a normal flight at the location and confirm the static object appears as expected

13

Document the required freeware library for users

If you share your scenery, users must know they need the same object library installed.

• In your scenery’s readme or product page, list the freeware object library as a required dependency

• Include the exact package name and a download link (e.g., flightsim.to page)

• Clarify that you do not include the library’s files—users must download and install it separately

• Optionally mention that objects are used as static scenery only (no simulation/physics) so users know what to expect

In practice, once you’ve done this once or twice, the “flow” becomes:

• Install library → confirm it mounts in Community

• Create/update your scenery project → open Scenery Editor

• Pick object from the library’s package → drop, tweak, save

• Build package → test in a normal flight → publish with clear dependency notes

You perfectly demonstrated why some of us would like a user-orientated, intuitive addon to do this! 😄

I would happily pay money not to have to follow those 68 steps, mess it up, trace where I went wrong, and tear my hair out.

Edited May 28May 28 by JYW

I started messing around with the SDK back in 2022, creating a few simple airport enhancements ... i.e. placing an object or two. I'm now at a stage where I could create quite complex airports from scratch, if I wanted, including custom models. But if I had to rely on a bunch of AI slop back then, I don't think I'd ever gotten off the ground 🤣

For anyone interested, the MSFS SDK reference includes detailed (yet easily followed) tutorials on how to do all that and more:

https://docs.flightsimulator.com/msfs2024/html/7_Samples_Tutorials/Tutorials/Creating_Or_Replacing_An_Airport.htm

Mamu Designs just released a tool that does a lot of miscellaneous stuff, mostly related to exploring on foot, but one of the things it does is let you place objects down, save their locations, and share that info with other users of the addon so they can see what you've placed.

https://www.fsexplore.com/

13 hours ago, JYW said:

You perfectly demonstrated why some of us would like a user-orientated, intuitive addon to do this!

Indeed. Compare this to the procedure for using the FSReborn FBO placer. That was the whole point of my original post. If FSR can do that with their FBO's, why can't we come up with a way to do it with Library Objects?? (I looked at FSExplore and also FSFire, and they are still too involved for my tastes.)

Click on the Library Object in a list to spawn it, (Should be a picture of the object when you click on it so you know what you actually have), adjust the postion, and forget about it. The next time you go to that airport, it's just THERE! THAT is what we need!

14 hours ago, bofhlusr said:

Here’s a full, end‑to‑end workflow—from installing the library to placing the object and building your package.

Has this procedure been verified as accurate? One little mistake and the whole process falls apart...

Which leads back to the purpose of my original post. As I said above:

Click on the Library Object in a list to spawn it, (Should be a picture of the object when you click on it so you know what you actually have), adjust the postion, and forget about it. The next time you go to that airport, it's just THERE! THAT is what we need!

https://docs.flightsimulator.com/msfs2024/html/2_DevMode/Menus/Tools/SimObject_Spawner.htm?rhhlterm=simobject%20simobjects&rhsearch=Simobject

There is an integrated Simobject placer in the 2024 SDK

Those are the only object that are possible to place at runtime (when the game is running)

Everything else require creating a project as instructed in previous post, it sound intimidating by looking at wall of text, but less that 30 seconds are needed , believe, the counter on my video is real

That's the architecture of the game!

About Simobject placing, there are a few apps out there, my new fsexplore has a web editor too, but because of the architecture you are limited to Simobject (compared to normal Library objects aka Scenery objects the choice is extremely limited)

Don't be scared of the in game Scenery Editor, thousands of creator have already digest hit and brought to all the community wonderful sceneries!

On 5/28/2026 at 3:58 PM, JYW said:

You perfectly demonstrated why some of us would like a user-orientated, intuitive addon to do this! 😄

I would happily pay money not to have to follow those 68 steps, mess it up, trace where I went wrong, and tear my hai

Delete (wishing for the old forum software).

Edited May 30May 30 by bofhlusr