5 hours ago, Bobsk8 said:

So you can't use Track IR anymore??

Yes you most certainly can. I only use Track IR, wont fly without it. Flights of 1-6 hours in real time using any aircraft including A32NX. No CTD’s. Track IR is perfectly compatible with MSFS including SU 5 with Hot fixes.

Edited August 21, 20214 yr by RaptyrOne

1 hour ago, RaptyrOne said:

Yes you most certainly can. I only use Track IR, wont fly without it. Flights of 1-6 hours in real time using any aircraft including A32NX. No CTD’s. Track IR is perfectly compatible with MSFS including SU 5 with Hot fixes.

I know that, I use it all the time. I was asking  if the person having CTDs had to stop using his.... ?????

Edited August 21, 20214 yr by Bobsk8

Hello everyone,

I also experienced this error earlier today when modifying some options in the game settings to improve FPS and it gave me these 2 errors (one at a time) when starting the game and it wouldn't get past the splash screen because it didn't even show the main menus (a tragedy).

"0xc0000005" & "VCRUNTIME140.dll"

What I remembered the last thing I did was that I activated DirectX 12 (beta) and from then on, it was only CTD.

Not being able to load properly the game to modify that parameter to DirectX 11, I had to look for the configuration file (I remember in Prepar3D it was in "appdata" folder and it was called "prepar3d.cfg"), so I had to look for a file similar that the MSFS2020 (steam edition) could had and I located it in the following path:

"C:\Users\YOU_USERNAME\AppData\Roaming\Microsoft Flight Simulator"

The file that I opened and modified with notepad is called:

"UserCfg.opt"

There I searched and found the property called: "PreferD3D12", it was with a value of "1" (one), I changed it to "0" (zero), I saved the changes and I ran the game again.

Bingo, I was finally able to play again without any CTD.

That was my story, I hope it can help someone, who like me, suffered in finding the solution after several hours of trial and error, I was able to solve.

Courage to all those who continue to have this disastrous nightmare of CTD's, have a prompt solution and can enjoy such a wonderful simulator.

Regards.

Access Violation is an extremely general error that can happen for a variety of reasons. In MSFS, these types of errors usually happen when doing specific things, such as loading a particular addon or starting a flight in a specific location. If it's repeatable like that, it probably isn't caused by faulty hardware (unless specific files are corrupted due to a faulty SSD or similar). More likely it's a stack or buffer overflow, null pointer or other faulty code in the sim. This is either due to a bug in the core application code, or poor handling of errors in addons.

In general, error handling in MSFS leaves a lot to be desired. Properly coded software should handle exceptions and errors gracefully and throw an informative error message. Dumping the user back to the desktop without any useful error message or error logs is very bad programming practice. The sim should be able to catch the exception and ideally also provide some information on what caused it in the first place. When you get these errors in MSFS, you're stumbling in the dark and can only really solve it by trial and error (keep changing stuff randomly until you stumble on something that fixes the problem).

I started getting them when I added a bunch of freeware scenery to the Seattle area combined with the OrbX stuff. 8 times out of 10, the sim would CTD while loading. Basically if the progress bar made it past the initial "bump", CPU usage will go up and the sim will start loading properly. If it doesn't make it past this initial "bump", it will CTD. A log file showing exactly what happens during this stage of loading and what the last step was before crashing would be exceedingly helpful.

Edited March 14, 20224 yr by JimmiG

On 3/14/2022 at 5:05 AM, JimmiG said:

In general, error handling in MSFS leaves a lot to be desired. Properly coded software should handle exceptions and errors gracefully and throw an informative error message. Dumping the user back to the desktop without any useful error message or error logs is very bad programming practice.

Bang on.  CTDs would be so much easier to diagnose and fix if we actually had some useful information.

I have a feeling that the lack of decent error handling is a legacy of FSX, where the quest for performance was all encompassing. Perhaps as Asobo replaces more and more legacy FSX code, error handling will improve. I'm sure they would love to get anonymized error reporting and/or telemetry sent back to the mother ship.

...jim

 

Follow this...

 

https://forums.flightsimulator.com/t/ctd-fix-info/471880

3 hours ago, JimBrown said:

I have a feeling that the lack of decent error handling is a legacy of FSX, where the quest for performance was all encompassing. Perhaps as Asobo replaces more and more legacy FSX code, error handling will improve. I'm sure they would love to get anonymized error reporting and/or telemetry sent back to the mother ship.

...jim

 

There is no legacy code in MSFS20. It is an all new engine for MSFS20

6 hours ago, udidwht said:

There is no legacy code in MSFS20. It is an all new engine for MSFS20

You mean the god awful traffic AI is all new state of the art and only by pure conincidence is exactly the same as in FSX? Or the ATC?

1 hour ago, Fiorentoni said:

You mean the god awful traffic AI is all new state of the art and only by pure conincidence is exactly the same as in FSX? Or the ATC?

It isn't FSX code that is for sure. Does it need work yes. This sim is barley 1.5 years in.

4 hours ago, Fiorentoni said:

You mean the god awful traffic AI is all new state of the art and only by pure conincidence is exactly the same as in FSX? Or the ATC?

I asked how much of AI, ATC is legacy code but nobody seemed to know. Hopefully will get improved in the future or more 3rd party programs become available.

4 hours ago, icewater5 said:

I asked how much of AI, ATC is legacy code but nobody seemed to know. Hopefully will get improved in the future or more 3rd party programs become available.

I hardly remember FSX ai but MSFS reminds me of it, that says a lot. As for the ATC I think some phrases are a word-by-word copy from FSX, so maybe they didnt use the code but the did use the phraseology.
I am sure AI will be fixed, shouldn't be too hard to bring it to the level of P3D at least. As for ATC I think that won't change, it's been 20 years that there has been no real progress; they will eventually fix those annoying bugs but that's all. Also VATSIM is "too" popular to really be forced to improve upon the AI ATC.