Live Dev Q&A: Guided Question

[CptLucky8]

[ ] Avionics
[ ] Flight Planning for Airport Approaches 
[ ] Input/Controls
[x] Flight Model

Here are links to some Flight Model questions:

About the goal and scope of the “1000 elements” approach:

(main point highlighted - link for context)

@CptLucky8

I don’t believe it is what it is actually doing. Instead, it makes concessions because they decided it was better to make FS2020 flying FSX ported aircraft like in FSX so that 3rd party devs could port their add-ons faster to FS2020. It is not dissimilar to what I’m saying about the FS2020 systems and gauges SDK either and probably for the same reasons as well. Given the number of “sophisticated” aircraft available and “ported” from FSX, this begs the question whether this is a good decision from the get go.

Which raises another question to me: in making their normalization algorithm "bending’ their 1000 element model to match the FSX historical flight model behaviour, didn’t they just cut out what could have made their new engine a key differentiator from the past and from competing simulators?

@CptLucky8

the FS2020 documentation about XP11 is wrong because it doesn’t take in account the latest XP11 developments in the flight model since XP11. It looks in fact as-if the FS2020 SDK docs was redacted by the time they started developing FS2020 and this relates to XP10 area flight model docs

NB: Please read the rest of the discussion for the pros and cons between what seem to be FS2020 and XP11 flight modeling respective technologies.