1 So won't be changed unless PMDG do something on their side as well?
This doesn't have anything to do with PMDG, it's a general rule of how we consider the airplane having the last word on settings, and if you read what I wrote carefully, it would have been clear why it would be wrong to change it now but since apparently it isn't, I'll do better example:
An airplane developer (I'm not naming it, but they DO exists and they are not PMDG) wrote some integration *before* the menu to choose if you want to board pilots/crew was even a thing, so their integration flow didn't even take that into account.
Now, after we added that menu, the same developer got back to us, saying the new menu is screwing their flow, because they coded the integration before the menu was even there.
To "fix" this, we would have two choices:
- Go out there and find out each and every developer who ever coded some integration, and tell them "sorry, you must fix your code, because we added a non-skippable menu".
- Skip the menu when the airplane code said so, so nobody has to change anything.
Choice is fairly obvious and again, it's consistent with how GSX works almost everywhere, and it's whoever wrote some integration has the last word how GSX works. That's the same when the passengers number set by the airplane overrides the number read from Simbrief and it's the same when some airplanes *locks you up* from changing settings the are detrimental to how their integration works ( some settings can be automatically locked by the airplane and you can't change those ).
So please, don't try to pass this with an PMDG-FSDT issue, because it doesn't have anything to do with, it's more like not breaking the trust of those who took the extra effort and spend their time coding a GSX integration. They KNOW their airplane better than anybody.
