The Mustang recently saw performance changes in AC 1.0.2. How are these changes achieved in an engine that physically models ship movement? Do these changes affect maneuverability across other ships?asked by SP3CTREnyc

So specifically in the Mustang, while I'm not 100% about what we did in 1.0.2 – though I know for 1.1 we've been doing a re-factor on IFCS and flight control modeling and background mathematical models we're using – to give a more predictable consistent outcome to the actual physical simulations. So hopefully in 1.1, there will be more stability of some of the flight issues Backers have seen. So it's aiming for 1.1, possibly for 1.1.1. It's still a work in progress.But generally, before that, if we're doing changes we're mostly doing things like adjusting thrust on various thrusters, adjusting mass to balance it, etc. We don't have any hard-line rules, like, "Okay, this ships rolls at this rate," – because everything is physically simulated. So we have to do things like move the position of a thruster, change the thruster mass, the amount of thrust put out, the mass of the ship, etc.We've had some Mustang issues, like a bucking issue (which is kinda appropriate for a Mustang since it, you know, bucks...). So you'll see these issues addressed in 1.1, or even 1.1.1. As well as the ability to toggle ESP off and on like you do with COMSTAB and G-SAFE. Generally, localized changes on ships don't affect other ships, because we're just changing the stats on the ship.But the work John's doing is gonna make the system a lot more stable inherently – and that will affect all the ships so they fly and feel a little better. Because as things are changed along the way, sometimes flight can deteriorate a bit because everything is physically modeled, so we have to go back and re-balance things to fix it up – just like in the real world!