GREAT Post .. Good constructive technical help & information. Thank you.
Question: Why would Asobo “NOT” be generating error reports that can automatically be sent back to Microsoft/Asobo ?
Manual reports with very little information, submitted to ZenDesk, just only seem to serve a PR function, making Users think they are helping to solve the problem.
In most cases, its a case of “Rubbish in = Rubbish out”
Personally, I never had a CTD, until I updated to Windows 10 2004 .. now, despite making sure I have all Windows patches for 2004, I cannot fly in MSFS for more than 30 minutes before seeming random CTD.
It would be re-assuring to know that Asobo is now currently developing and debugging on the 2004 version of W10.
I would go so far as saying, if you don’t keep Windows fully up-to-date, you should not expect an APP, in current development, to necessarily still be backwards compatible with an old version of the OS.
Any suggestion by Asobo, that users need to keep using an earlier version, or revert back to an earlier version, is just too ridiculous to consider,
Asobo’s #1 task should be to eliminate CTDs with 2004,
How they do that should not be that difficult.
They need to Internally, or Externally recruit a number of suitably vetted and qualified testers, (using verified and suitable hardware) and supply them with the tools, or a Debug version, that will automatically report crash logs to Asobo . (ignore Performance hit)
This Manual trying to report CTD issues to ZenDesk is a Total waste of everyone’s time, and will achieve nothing, apart form an enormous waste of everyone’s time & resources.
Until Asobo fix the frequent CTD issues with 2004, I see no point in wasting my time, as a customer, even trying to run MSFS ..
Yes, I’ve seen how GREAT the Graphics are, but whats the point if the APP keeps crashing.?