It’s worth a shot! I’ve seen a few here and there, usually on small airports you can use the pushback quick buttons or one of the apps and you don’t need the dude to spend 13 minutes hooking up.
More for goofing around with those moments after a flight where you don’t have any more time to do anything more than goof around.
Version 1.2.1 just released.
As usual, free for PC at https://flightsim.to/file/38035/brown-field-muni-kdsm
Version 2.0 is now available for free and for all PC. This is the update to make it compatible with Microsoft Flight Simulator 2024. This version include also fixes and a lot of improvement for MSFS2020.
Free to download at https://flightsim.to/file/38035/brown-field-muni-kdsm
Just to keep my fellow users posted : the main ATC tower (the tall one) disapears in this KSDM scenery if you use MSFS2024 SU3 Beta.
It looks like some included MSFS library object has changed. The tall tower of my KSDM scenery is actually the KNKX Miramar’s one. And it has been updated by who-ever have developped it for Microsoft (Gaya? Asobo?). The object is replaced by 2 objects (the building + props). It’s a bug-logged in the devsupport forum.
I have a quick fix for those interested that I may release but I’m not currently planning a intermediate version until the final public SU3 gets released.
Feedback welcome.
Thanks for the link. I read through the support forum posts primarily because I’m just curious how it all works behind the scenes.
I was wondering what is the actual “bug” that is logged? It looks like the airport scenery was modified/updated, and thus the object name changed. If the old object was referenced in a scenery (like you have done), then the scenery would need to be updated as well. So, that’s not really a bug in my mind? It’s kind of how it works, but the tough part for a scenery developer is if they don’t know something has changed, your work is impacted and you need to go off on a hunt to figure out why.
It’s probably unrealistic to have Asobo list out every object that changes at every airport or every model library change, so I’m not sure what bug could be fixed to address this. I mean, Asobo could just leave every legacy object in place when they make changes, but that would be pretty inefficient on its own.
Is there a clean way to do this?
I don’t know why they call it “bug-logged” and tend to agree with you that it’s not really a bug.
It’s just annoying for those like me that pick the object and discover inadvertently - via a user feedback - that something has disappeared. I’m not expected that Asobo maintain a list of all object and their update 
I would love of it… with a picture, size for each of them, a search engine… etc… LOL.
What would be cool to have the airport updates in the change log. If it’s not in any SU3 Beta changelogs, means that the change is not validated yet. And that in the final SU3 this invisible objet will be avail ?
Version 2.0.1 just released at https://flightsim.to/file/38035/brown-field-muni-kdsm#update with this changelog:
Enjoy my freeware and please share your feedback!
A small but important update has just been released for the freeware Brown Field Municipal (KSDM) scenery, thanks to valuable feedback from our community - especially supporter @doublelaunch from flightsim.to. This update focuses on refining runway textures and addressing a few bugs in MSFS 2024.
Specifically, the unreadable ATIS frequency has been fixed, and the issue of double windsocks has been resolved, ensuring a smoother and more polished airport experience. While modest in scope, these improvements help keep KSDM at its best for all sim pilots.
Experience one of Southern California’s most unique general aviation hubs like never before. Located just 1.5 miles from the U.S.-Mexico border, Brown Field Municipal (KSDM) is a bustling mix of private jets, military history, and active law enforcement operations.
What’s New in this version 2.1.0?
Why fly to KSDM?Free to download for PC MSFS2020/24 : https://flightsim.to/file/38035/brown-field-muni-kdsm
You added Airwolf! 
