CTD V5 HF1 vcruntime140.dll

[fluffyflops 1,858]

On 10/21/2020 at 12:11 AM, micstatic said:

Not a fix. Turns out Lockheed Martin will have to make a Fix 

have found you are only getting this issues since gsx was updated as below ??

Thats whats ive found.... I never until then had crash using gsx.  ever.

 

September 23rd, 2020   

• NEW: The Couatl scripting engine is now a 64 bit application in P3D4/5.
• NEW: The Couatl scripting engine is now a native P3D Simconnect client.
• NOTE: If you have issues with the 64 bit version, and would like to go back to use the previous 32 bit version in P3D4/5, change the Path tag in the Documents\Prepar3d Addons\ADD-ON.XML file:
  
  Addon Manager\couatl64\couatl64_P3D.exe
  
  change it to:
  
  Addon Manager\couatl\couatl.exe

 

[BerndB 349]

On 5/10/2020 at 3:47 PM, pgde said:

I am getting this error also. Non-ORBX user. Reinstalling Visual Studio didn't fix it. Seems to always happen randomly when ATC calls me (like to change frequencies, etc). 

This is a known issue of V5 which is LM aware of. They try to fix this with next update. This is related to every transparent SimConnect Window as it´s used by ATC, GSX and some other add-ons.

What wondered myself is that my V5 was running always stable without CTD unless some of the last WIN10 updates came along, there where also updates of NETFramework and other stuff updated. From then on i got on every singel flight a VCruntime CTD only at arrival at the gate when GSX tried to call for debording. I tried the following:

1. i de-installed SimConnect and also ASconnect (AktiveSky)

2. i did run a repair installation of every single VCruntime version.

3. I installed SimConnect an ASconnect again.

Then the CTD didn´t happen again for the last 150 hours of flying.

Then this week, a new Win10 update came along and i have again this VCruntime CTD.🤔

Edited October 23, 2020 by BerndB

[thepilot 577]

Indeed related to any application that uses said window. Have sadly had this CTD twice, once with ActiveSky, once with default ATC. Absolutely no rhyme or reason to it, happens (seemingly) completely at random. Most important fix for V5.1 in my opinion...

[micstatic 4,319]

agree.  Infuriating to go thru a cold and dark and get vatsim clearance etc.  then boom gone. 

[chapstick 2,757]

And it looks like no 5.1 this week. Closing in on 5 months since this was reported to LM.

[KL Oo 700]

Yeah - the biggest concern with this issue is that its been actively discussed on the LM forums and widely reported however I'm yet to see any acknowledgement of the issue from LM. I realise @virtuali made comment on his forums that LM were aware of the issue but I don't recall seeing anything from LM themselves.....

Fingers crossed they are actually going to do something about it. This should have been fixed in a HF. As was said above - its anyoing spending an hour setting up from C&D only to have a crash when requesting taxi or push back.....

 

[fluffyflops 1,858]

8 hours ago, KL Oo said:

Yeah - the biggest concern with this issue is that its been actively discussed on the LM forums and widely reported however I'm yet to see any acknowledgement of the issue from LM. I realise @virtuali made comment on his forums that LM were aware of the issue but I don't recall seeing anything from LM themselves.....

Fingers crossed they are actually going to do something about it. This should have been fixed in a HF. As was said above - its anyoing spending an hour setting up from C&D only to have a crash when requesting taxi or push back.....

 

theres plenty of bugs as we all know because they rushed it and released too early... lets take my top 3 for example 

1.atc window ctd --  doesnt it effect Militay ,  ?  probably not much

2. the full screen glitch when you run a program within p3d  (fstramp for example)    --  doesnt it effect Militay ,  ?  definatley not 

3. the text dialogue box stutter  (when using the fsl and you want to show pedal sticky warning)  --  doesnt it effect Militay ,  ?  definatley not 

So with those 3 in mind the proof will be in the pudding in 5.1 if any of them has been looked at or if the "we love the simmmer"  and the  "Ive met Mr So and So at the conference and hes a very nice man" line that simbol goes on about actually means anything.  I hope it does but I highly doubt it.  It they do fix all 3 of those bugs which are well known, then Ill quite happily eat my words.  Im that confident they wont fix them, neither deep down do they care about "simmers"

My gut feeling after seeing how LM cant be bothered with simmers that use their forumns, its been shown they use "work for free lackies" to do their leg work and then give them a beta copy,  and then rarely come on the LM forumns to help

I imagine they are working with their account managers to assure they keep their corporate customers happy.  And now with the advent of ms2020 and they see the "community" making Godzilla mods, and faffing around with a Neo that cant fly in a straight line , how can you blame them, theres no money in Godzilla mods and teenagers, but there is in defence contracts.

 

[KL Oo 700]

15 minutes ago, fluffyflops said:

theres plenty of bugs as we all know because they rushed it and released too early... lets take my top 3 for example 

1.atc window ctd --  doesnt it effect Militay ,  ?  probably not much

2. the full screen glitch when you run a program within p3d  (fstramp for example)    --  doesnt it effect Militay ,  ?  definatley not 

3. the text dialogue box stutter  (when using the fsl and you want to show pedal sticky warning)  --  doesnt it effect Militay ,  ?  definatley not 

 

Ah yes - I forgot bout the green message bar bug. You'd think that would be a simply thing to fix .... but I'm not a programmer....

16 minutes ago, fluffyflops said:

those 3 in mind the proof will be in the pudding in 5.1 if any of them has been looked at or if the "we love the simmmer"  and the  "Ive met Mr So and So at the conference and hes a very nice man" line that simbol goes on about actually means anything.  I hope it does but I highly doubt it.  It they do fix all 3 of those bugs which are well known, then Ill quite happily eat my words.  Im that confident they wont fix them, neither deep down do they care about "simmers"

My gut feeling after seeing how LM cant be bothered with simmers that use their forumns, its been shown they use "work for free lackies" to do their leg work and then give them a beta copy,  and then rarely come on the LM forumns to help

I also find their lack of comment (or recent appearance on the public forums) disappointing. It wouldn't take more than a few minutes to pen a post in the 15 page thread about the SimConnect window issue to simply say "Yes, we're aware and we're working on a fix"...