It is such a pity that something as simple as a repaint, or JSON file (basically a simple text file) in the community folder, can bring the simulator to it's knees with a CTD.

We all know where the solution lies.  This is one of the most fragile pieces of software I have ever used - Asobo need to deal with it.

Then there is the victim blaming if you put something in the Community folder.    For heavens sake - that is what Asobo put it there for! 
It should be able to parse the content and screen stuff out if it doesn't like it.
One guy had his Ju-52 repaint crashing to desktop because of a very basic error in the associated json description file - incredible!  It this right?  Should this be happening?
 

Edited December 9, 20214 yr by bobcat999

3 hours ago, MySound said:

100% right. 
And MSFS is really somehow demanding on the hardware. I run my 3080ti with a afterburner profile. And when I am right „on the edge“ then games like Forza, Cyberpunk etc may run without crashes - but MSFS will crash. 
i don’t know what MSFS is doing different in its engine. 

It's because flightsims, unlike most other applications, stresses not just one or two parts of your PC but most of them simultaneously.

Its not only graphics or CPU, but memory, harddrive (reading scenery), network (streaming scenery), input from lots of USB controllers etc. All this add to the workload of the chipset on your motherboard and/or CPU.

4 minutes ago, bobcat999 said:

  This is one of the most fragile pieces of software I have ever used - Asobo need to deal with it.

 
 

I agree with you here. I raised this issue of a poor error catching algorithm some time ago. Some fellow simmer answered me that it was an issue with Windows not the Asobo's code. FWIIW.

Check temperatures on GPU and CPU.
Once upon a time I had a problem with the GPU power supply which was causing MSFS to shut down on its own. After replacing the power supply with a better and more powerful one, all CDTs gave way.

Edited December 9, 20214 yr by PAT_Noe

2 minutes ago, PAT_Noe said:

Check temperatures on GPU and CPU.
Once upon a time I had a problem with the GPU power supply which was causing MSFS to shut down on its own. After replacing the power supply with a better and more powerful one, all CDTs gave way.

Gee really, you mean it might not be the simulator itself?  What a novel idea!

6 hours ago, orchestra_nl said:

It's because flightsims, unlike most other applications, stresses not just one or two parts of your PC but most of them simultaneously.

Its not only graphics or CPU, but memory, harddrive (reading scenery), network (streaming scenery), input from lots of USB controllers etc. All this add to the workload of the chipset on your motherboard and/or CPU.

Thank you for putting this in context--given these ideas it's remarkable the sim is as stable as it is.  Just the very fact of integrating streaming data with the rest puts it in a class of its own.

7 hours ago, orchestra_nl said:

It's because flightsims, unlike most other applications, stresses not just one or two parts of your PC but most of them simultaneously.

Its not only graphics or CPU, but memory, harddrive (reading scenery), network (streaming scenery), input from lots of USB controllers etc. All this add to the workload of the chipset on your motherboard and/or CPU.

I can guarantee you there is no more load then when running F1 2021 with 120 FPS. I have an absolut top of the line system and the only thing that decides about a CTD or not are some MHz or mV on the GPU. 

I had constant CTD's  last summer

I tried reinstalling the C++ redistributables, interpret the event logs (in vain), change settings for and increase page file, ran hardware diagnostics tests (passed the tests flawlessly), changed to Win10 'game mode' back and forth, delete all from community folder and so on, go back to restore points etc etc..... turned out that my gfx card was simply dying and needed to be replaced,

Now I only get CTDs when i launch the aerosoft CRJ500/700 or try to launch that drone plane thingie that came with the latest update. After many searches i now suspect that the reason for the CTD with the CRJ is due to my i7 CPU being older than 3rd generation.

So in all these cases it has been a matter of aging or dying hardware ....

19 hours ago, MySound said:

I can guarantee you there is no more load then when running F1 2021 with 120 FPS. I have an absolut top of the line system and the only thing that decides about a CTD or not are some MHz or mV on the GPU. 

Does F1 2021 integrate streaming scenery?  If not, that is another potentially relevant difference.

On 12/9/2021 at 11:13 AM, MrFuzzy said:

If everything else fails, I am afraid you will have to reinstall Windows and MSFS.

Nothing helped so I reinstalled MSFS and now it works. Annoying but at least I can fly again.

I think it has to be a driver issue.  I'm getting CTDs constantly now when loading in.  The community folder isn't the problem.  Your add-ons don't just work one day then the next they don't.  Unfortunately, there's no option for me to roll back the driver.  I'll just have to wait for the next one, I guess.  This is an issue that's been going on since the dawn of time.  You'd think they'd be able to have some kind of stability check, so your stuff doesn't break all the time.

Driver roll back fixes the problems.  🙂