Exactly. You can totally have your own custom flight model, that’s always been the case (start with the flying brick GitHub - tml1024/flying-brick: Silly sample aircraft for MSFS built from scratch ) but every plane/asset doesn’t sit in isolation, they need to be integrated properly via all the other interfaces. Ignoring these interfaces is going to cause a lot of user pain, and we’re seeing it already.
Microasobo really need to get on top of this in terms of documenting interfaces and standards so this doesn’t become a bigger problem than it should be, and it’s already a problem that starting to become a pita.
I raised these issues already with W&B on the dev forum a while back, but no response so far: https://devsupport.flightsimulator.com/questions/17290/weight-balance-synchronisation-from-table.html
Be careful what you wish for, is all I’ll say.
We should be pressuring all parties here to come to the table and sort this out so every plane, no matter if it’s using internal or external FM’s/Functionality, also conform to standard sim functionality and data feeds so the ecosystem of addons surrounding that (including base sim functions) works seamlessly and doesn’t cause undue user pain.