I don’t know. This sim is very complex and therefore potentially unstable, especially with all the mods flightsimmers use. So i think it’s a bad choice to not include error handling code that at least gives codes to identify problems.
The phoning home thing is an extra but at least provide the user with some info. If we know which mod gave the problem we can at least ditch that mod instead of opening another helpdesk ticket to Asobo.
We now have to speculate and rely on generic Windows crash messages that tells us which file/module crashed but not why.
I can get Crash dumps, and even “limited” analyze them with WinDbg, so I can see its always a bad memory access that has always been the cause of ALL my CTD since MSFS was released, but there is not enough information to identify exactly where the null pointer errors are occurring, or the source to see what was incorrectly coded, or more likely, not catering for Data sensitivity.
Yes bad memory access is mostly the reason of these CTDs, but i see them being caused by mods (more likely a bug in the sim triggered by a mod). Yesterday i had a very annoying CTD problem and after trying for hours i realized it is the GTN750 mod.
I think a mod shouldn’t have any access to something that crashes the whole sim, it shoulkd live in a secure container imo. If it does something wrong, the sim should produce a dialog box describing the problem and removing the mod.
But even this kind of error handling doesn’t seem to be present here.
Strange thing is us simmers have known for years what trouble mods can give us. If there is any software that needs this error handling it’s MSFS.
I am aware we are being armchair developers here but it seems so obvious.
Exactly, it’s most likely the Kernel causing the crashes, some of which may be being triggered by Mods, or anything in Official, calling the Kernel and that call causing the fault … probably mostly caused by Data sensitivity.
You have the performance loss over time issue? I had the same, i re-installed the sim and the problem was gone. Do you have any audio mixer software like voice meeter by chance?
Asobo did say they are working on the memory issues, but the mod thing concerns me the most.
I have trouble now with 7 mods in my Community folder, there will be more addons every month, if it works like this it will be impossible to have so much mods installed.
the funny thing is, i’m constantly flying from the same origin to the same destination, i.e. from LEBL (Barcelona) to EDDH (Hamburg) - just taking different routes. while one route works perfectly fine, the other route acts like this and on another different route the sim just crashes to desktop after two thirds of the way.
that’s why i rule out that it has anything to do with my hardware, the overclocking, the operating system, the swap file size, a vc++ lib or anything third party, let it be mods or anything running in the background.
Yes certain location also trigger bugs, that just means the software is not protected from bugs being caused by external packages. As the sim evolves this will get worse and worse, scenery and airports can cause big problems and CTDs, the sim should be protecting itself from external factors with error handling.
ya, right. hence my request for way more exception handling from the game itself. it needs to react to those issues in a proper way and not just degrade or crash due to those issues.
X-Plane does a pretty good job of writing out log files, and indicating causes of crashes. But in some cases even it cannot write out for the reason you describe, and it takes some educated guesswork to deduce what happened.
