V5: ATC-windows crash VCRUNTIME140.dll

[Perfectflight]

VCRUNTIME140 ERROR
IF ONE OF YOU MAKES THE ERROR, IT CAN HELP SET TEXTURE RESULATION TO 1024X1024.
THIS CHANGE I DIDN'T HAVE ANY CRASH.
AN ADDON REPLACED THIS SETTING AND WHAT HAPPENED - CRASHED

[JorgenSA]

Another possible solution is to install Visual Studio 2019 from Microsoft.

Be sure to install ALL components - there's a lot of them....

Jorgen

[airbader]

VCRUNTIME140 ERROR
IF ONE OF YOU MAKES THE ERROR, IT CAN HELP SET TEXTURE RESULATION TO 1024X1024.
THIS CHANGE I DIDN'T HAVE ANY CRASH.
AN ADDON REPLACED THIS SETTING AND WHAT HAPPENED - CRASHED

This has nothing to do with it. Coincidence.

[Sky_King]

Another possible solution is to install Visual Studio 2019 from Microsoft.

Be sure to install ALL components - there's a lot of them....

Jorgen

Jorgen -- is it necessary to install all of the development tools (like for Azure, etc) or just the .NET components in the first section?

[JorgenSA]

Frankly, I am not sure on how much to install. I installed everything except the tools for developing mobile phone apps (Android etc.).

Jorgen

[Grand_Pubah]

I wonder what the odds are that LM will be able to fix this problem soon. Seems like overkill to install every Visual C++ piece of software. Everything else runs perfect on my PC, don't want to start installing things without knowing which version is the issue. But I am sick of these crashes.

[airbader]

I wonder what the odds are that LM will be able to fix this problem soon. Seems like overkill to install every Visual C++ piece of software. Everything else runs perfect on my PC, don't want to start installing things without knowing which version is the issue. But I am sick of these crashes.

It's just the two .DLLs that you need. I don't know why that guy is saying there's "a lot" to install. Also, it doesn't permanently fix the issue anyway, so it's a moot point.

[Grand_Pubah]

You're talking about the 2015-2019 C++ right?

[Martyson]

I wonder what the odds are that LM will be able to fix this problem soon. Seems like overkill to install every Visual C++ piece of software. Everything else runs perfect on my PC, don't want to start installing things without knowing which version is the issue. But I am sick of these crashes.

@ Grand_Pubah,

Do a screenshot of what you have installed.

[Grand_Pubah]

I installed Visual-C-Runtimes-All-in-One-Jul-2020, which claims to be updated as of June 2020. The link is below if you need it. It seems if I install it before a flight I at least can make it through a short one, haven't tried a long flight yet. I don't remember having this problem before HF2.

https://www.techspot.com/downloads/6776 ... ckage.html

[Sky_King]

Some great news -- rumor is that LM seems to have been able to reproduce this error so, hopefully, they should come out with a fix soon.

Finally!

[airbader]

Some great news -- rumor is that LM seems to have been able to reproduce this error so, hopefully, they should come out with a fix soon.

Finally!

Well, I hope the rumor is true because this CTD just ruined yet another flight for me.

[Matty21]

Can 100% confirm this is gsx I just had it on pushback it happens every fifth flight I attempt

[JorgenSA]

Great, Matty - have you talked to the developers about this?

Jorgen

[Sky_King]

Virtuali has posted that the issue is on LM's side since there apparently continues to be an issue with the simconnect semi-transparent menu windows that affects both default ATC and GSX. Herre is what he posted on the FSDT support forum:

Starting quote:

"Sorry, but that's not the case. The problem is confirmed to be caused by a bug in the standard semi-transparent Simconnect menu window which is also used by the default ATC, and it has been confirmed multiple times ( there's a very long thread on LM forum about this ) by multiple users it can happen even with NO add-ons installed, no GSX and just with the default ATC.

You are probably mislead assuming "it happens only with GSX", only because you are probably using the GSX menu more often. Because, if you followed the thread on LM forum, it's not something as easy to reproduce as "just" calling a menu. Sometimes you must call it many times, sometimes you must fly the sim for a while, but sometimes it happens randomly.

Many users mistakenly assume "it's GSX", but that's just because GSX uses that menu a lot, so the chances for a crash are higher but, again, it's not GSX, it's the sim itself. GSX is only sending a 100% STANDARD Simconnect command to create a menu, which is exactly the same in FSX, P3D1, 2, 3, 4 and 5, nothing has changed in the V5 SDK and the code to call it is EXACTLY the same and we are not required to do any changes to it, because the API is identical.

And of course, the problem has been reported to LM, which are looking into it."

End of Quote.

In my case, I don't have any issues with GSX but have significant issues with the default ATC which causes a vcruntime error almost every flight at random times. As I posted in my earlier post here, LM has now confirmed that they can reproduce the error and all of us are awaiting a fix.....

Hope this helps.

SK