Whoa that’s some question! Where to start. At the risk of turning this into an Op-Ed, let’s take some different angles.
In the days of FSX, developers were able to precisely define a flight model through a vast number of look-up tables. A ton of work, but highly accurate and versatile.
MSFS has (mostly) left that scheme and moved towards the ‘real world’.
In the real world, there is no such thing as a flight model. An aircraft’s behavior follows directly from the interplay of geometry, weight and engine with the air. There is no ‘flight model file’ (Exceptions are from aircraft that are heavily controlled through fly-by-wire). In order to predict the aicraft’s behavior, aircraft manufacturers like Boeing, Airbus use supercomputer-based CFD (Computational Fluid Dynamics). Even then, they need to resort to wind tunnels and flight testing to measure and finetune the details.
Problem is, that kind of calculations is WAY too heavy for realtime PC-based work.
And thus, MSFS seems to have adopted a compromise. The flight model is based on the geometry and MSFS translates that to a ‘normalized’ aircraft, and allows for tweaking and modification. Unfortunately, it is unclear to most flight model developers how it works exactly, and a flight model for MSFS has thus become a major trial & error, tweaking (through ‘scalars’) and testing effort.
And here comes the issue…
On the one hand, developers boast largely the same: performance ‘by the numbers’, tested by real pilots, in accordance with the manual, etcetera.
On the other hand, whereas many pilots voted flight model as their #1 priority ([POLL] Your most important things when deciding to BUY a NEW AIRCRAFT? - #80 by MatronlyApollo8), I suspect many don’t have a clue to what it implies. Many reviewers are explicit on this. They say ‘it feels fine, but I’ve never flown one for real’, and that’s it.
Many pilots fly airliners. And yes, these are mostly fine because the maneuvers are mild, the flight envelope used is very narrow etc. The difficulty is much more severe in fighters, aerobatics, high-altitude, supersonic aircraft and such.
You may be surprised to learn that MSFS does not model flaps differently from slats, although they are vastly different in terms of effect. MSFS does not allow a wing profile to vary across the wingspan. MSFS does not allow an asymmetric aircraft (except perhaps an engine placement), MSFS does not allow custom lift and drag for the fuselage, MSFS does not allow multi-position spoilers/airbrakes. And I’m not even starting to talk about engines and propellers. And, Asobo has not adhered to the established aerospace models, definitions and equations, making life difficult for developers (e.g. wing camber in degrees instead of percentage, a left-handed coordinate system instead of right-handed).
Most pilots are probably totally unaware of these complications.
The benefit for MSFS is that it has become a lot easier to start developing flight models, because there is a lot less to define. And thus we see a lot of payware aircraft of, let’s say, marginal flight model quality at best.
For developers, flight modelling is close to a nightmare. The flight_model.cfg features tens of obsolete parameters. But some are described as ‘legacy’, but are still required and may not be omitted (e.g. “pitch_moment_delta_elevator”).
As a result, developers like A2Asimulations seem to have totally bypassed the Asobo code, and use a prevailing fully custom code. Which is perfectly fine, except that the development time and cost will go through the roof.
Some other noteworthy solutions are what is being done by DCS and Il-2. They feature a very sophisticated and proprietary flight model. As a result, it is much harder for developers to come up with additional payware. Il-2 apparently does all their flight modelling in-house and does not even feature add-on aircraft as far as I know.
So, looking forward to MSFS2024, MS/Asobo have four options, in my opinion.
- Continue the present path, a difficult compromise with lots of legacy and tweaking, and a very reluctant developer community, working for an unaware customer base. It would mean that MSFS will outshine the competition (X-plane) in many areas but be a lot worse in flight modelling.
- Go back to FSX look-up tables. To the relief of many developers, but creating a strong barrier to new entrants.
- Move forward to the high-end CFD solution. Difficult, putting more pressure on the client CPU and fidelity, at risk of failing.
- Move further towards hi-end embedded solutions like DCS or Il-2, creating high quality flight models, but posing limitations to the third party developers.
Honestly, I’m not sure what to expect or hope for….
BTW… I hold an M.Sc. in Aerospace Engineering, specializing in flight performance. I have been flightsimming since 1985 (FS2 on a Commodore 64). I have held a private pilots licence. I am also a contractor Flight Model developer, although I must admit I have not done any modelling for FSX.