We would need to be able to patch the exterior .xml
Which is not an ideal solution, because it has plenty of shortcomings: having to patch every newly installed livery, having to deal with a complex installer that needs to recognize every supported airplane, the inability to support Marketplace airplanes because their exterior .xml are also not accessible, and now with Streamed packages it’s even more complex.
And users can’t create seated passengers profile themselves, so they need to wait for us to support new planes.
If we had an Attach API, to attach/detach models dynamically:
https://devsupport.flightsimulator.com/t/attach-simobjects-api/3102
We could achieve the following benefits:
-
We could support any airplane, including Marketplace and Streamed ones.
-
There wouldn’t be any need to deal with “supported airplanes”: we could just enable our internal seating editor in the normal airplane editor, so users could create and share airplane profiles including passengers seats.
-
No need to patch any file in the airplane. No need to refresh liveries.
Of course, an Attach API might be useful for plenty of other applications, like picking up/carrying/dropping stuff, and we might even use it to interact with the new Navigation graphs with custom behaviors and interactions.