V5: ATC-windows crash VCRUNTIME140.dll

[Matty21]

That moment when someone knows more than the main posters in here 👀

[Sky_King]

@ Sky_king ,

"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....."

Who told you that?

I can't specifically identify the developer, but it is somebody that is well known and is an active participant in the internal beta process. Believe it or not, doesn't bother me.

[Martyson]

@ Sky_king ,

"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....."

Who told you that?

I can't specifically identify the developer, but it is somebody that is well known and is an active participant in the internal beta process. Believe it or not, doesn't bother me.

@ Sky_king ,

"I can't specifically identify the developer,"

Why ?

[Sky_King]

I was asked not to. And I will not be answering any further questions about this. As I said, believe it or not.

[airbader]

It's honestly inexcusable on Lockheed's part that a thread with 16,000 views has received zero input from them, and we're relying entirely on a 3PD relaying information through someone else.

I've crashed 5/7 of my past sessions thanks to this CTD. I've now stopped buying add-ons for this platform.

And 5.1, which would presumably fix the problem, is likely months away from release.

[Martyson]

@ Sky_king ,

"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....."

Who told you that?

@ Sky_king ,

Actually you said:
"Some great news -- rumor is that LM seems to have been able to reproduce this error"

[JorgenSA]

@Sky King -

All you have done here is quote a rumor, and now you are back-pedaling by not being willing to identify its source.

Frankly, I could not care who that source may be, but you would do everyone a favor by going back to him/her and telling him/her to shut up, or to present the facts publicly - preferably in this forum.

Jorgen

[JorgenSA]

@airbader:

"And 5.1, which would presumably fix the problem, is likely months away from release."

Do you have any facts to sustain that observation? Or is this just another unfounded rumor or speculation?

Jorgen

[dawgfan58]

Add me to the list of people having this issue. Calling gsx window as well as active sky causes vcruntime140.dll ctd.

[Matthew21]

+1

[JorgenSA]

Matthew,

I have something for you to try - and I do not know if this will help, but I thought it worth a shot.

In your P3D folder, go into the \redist folder, and then to the \Interface folder. In that, you should find 6 folders. Go through all of them and their subfolders, and when you see a Simconnect.msi, run it. There should be a total of 6 of these. In my case, one of these aborted installation, and another said it was already installed, but 4 just ran.

If you can try that and see if it helps with the infamous VCRUNTIME140.dll, it would be greatly appreciated.

Jorgen

[Matthew21]

Matthew,

I have something for you to try - and I do not know if this will help, but I thought it worth a shot.

In your P3D folder, go into the \redist folder, and then to the \Interface folder. In that, you should find 6 folders. Go through all of them and their subfolders, and when you see a Simconnect.msi, run it. There should be a total of 6 of these. In my case, one of these aborted installation, and another said it was already installed, but 4 just ran.

If you can try that and see if it helps with the infamous VCRUNTIME140.dll, it would be greatly appreciated.

Jorgen

Will try it and report back.

[Matthew21]

Ran all 6 only one I had an error with is the debug one saying something about contact support

[JorgenSA]

OK, how does the sim run now?

Jorgen

[Matthew21]

OK, how does the sim run now?

Jorgen

I shall try it and report back