An interesting idea, but I think this is, IMO, unlikely to happen based on (listing just a few reasons):
- Ongoing cost of managing the implementation of this idea.
- Copyright / licensing requirements and verification. Unfortunately, some creators may include scenery objects that they did not create & do not have the rights to use. Microsoft does not want to be a party to illegally (even if unknowingly) distributing copyrighted assets without permission.
- Verifying adherence to the 2024 SDK.
- Handling of version updates whenever required to do so by changes in the SDK. There are examples today of 3rd-party products failing to work with SU betas. Imagine 100’s of airports having issues due to a SU change. The creators are all volunteering their time & may not be able to update their airport(s) in a timely manner.
- Handling of “abandoned” airports where the developers are no longer willing or able to work on them.
An alternative that would be both possible, practical and useful would be for Microsoft / Asobo to create and maintain a large, free, generic model library - Similar to the current Emerald Scenery Library - that all airport developers could use in their airport sceneries. This would replace the myriad of common libraries that many airports require (I have a list of 24 that are needed just for the few airports I’ve tried out). This would allow airport designers to focus on structures that are unique to their airport, saving them time & effort, reducing disk space (as the MS library would be streamed) & potentially improving performance.
Some of the objects in this library could include:
Aircraft (static); Bridges; Campsite, bush & backcountry objects; Airport hangars, lights, & clutter; People, pets & animals; Port &
terminal objects; Seaplane base objects; Trains, stations and trackside objects; Vegetation, Vehicles (road & water), etc. etc.
Edit: There is another wish for this feature, here: