I agree with the OP wholeheartedly.
However, people often come into these kinds of threads and shift around responsibility between the end-user and the developer of the software in question.
Let’s face it. There are boatloads of very demanding software out there that use everything your PC has to give. Be it 3D rendering software, video editing or distributed computing, etc., that run perfectly stable even at peak demand.
Any piece of software needs to be able to not oversubscribe system resources inadvertently and MSFS currently fails in these scenarios. The sim will just blindly take whatever is available and even more (causing a CTD).
For example, if the PC of a user can not handle the level of detail selected, the sim should be able to detect that there is not enough memory available and either automatically reduce the level of detail, draw distance or at the very least throw a warning message.
MSFS does nothing of the above as far as I know or at least not sufficiently. It’s tedious to troubleshoot and actually grasp what’s going on. I had constant CTDs for a while until I turned down the details. Now CTDs are rare, but in some cases, the sim still demands more VAS than my system is able to provide. That has nothing at all to do with wrong or missing drivers. It’s just not good memory management.
Every software provider needs to test on as much hardware as they can, Asobo just as much as Autodesk or Adobe or Pixologic. Other companies don’t get a pass on this and do better.
I am sure these problems will get fixed eventually but saying they are not present at this time or the fault of the user is less than helpful.
And of course, sometimes they are the fault of the user and this is what this thread is all about!