.Net Frequent CTD

[Baylorguy 39]

Ok, starting to get very frustrated with P3D.  I recently did a reinstall of everything and lately I have been getting frequent CTD which all seem to be tied to .NET framework somehow.  Pasted below is the most recent one... this happened while I was flying online via vpilot with ASN, REX4 and the AXE.  Really would appreciate help.

 

See the end of this message for details on invoking 

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B

   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

   at Microsoft.FlightSimulator.SimConnect.SimConnect.RequestDataOnSimObjectType(Enum RequestID, Enum DefineID, UInt32 dwRadiusMeters, SIMCONNECT_SIMOBJECT_TYPE type)

   at cg.v()

   at bs.f(Object A_0, EventArgs A_1)

   at System.Windows.Forms.Timer.OnTick(EventArgs e)

   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5477 (Win7SP1GDR.050727-5400)

----------------------------------------

vPilot

    Assembly Version: 1.0.5260.20091

    Win32 Version: 1.0.0.0

----------------------------------------

Ninject

    Assembly Version: 3.2.0.0

    Win32 Version: 3.2.2.0

----------------------------------------

System.Windows.Forms

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)

----------------------------------------

System

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------

System.Drawing

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------

System.Core

    Assembly Version: 3.5.0.0

    Win32 Version: 3.5.30729.5420 built by: Win7SP1

----------------------------------------

Anonymously Hosted DynamicMethods Assembly

    Assembly Version: 0.0.0.0

    Win32 Version: 2.0.50727.5477 (Win7SP1GDR.050727-5400)

----------------------------------------

System.Xml

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)

----------------------------------------

System.Configuration

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)

----------------------------------------

cfr1o26e

    Assembly Version: 1.0.5260.20091

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------

Accessibility

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

----------------------------------------

System.Management

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

----------------------------------------

Microsoft.DirectX.AudioVideoPlayback

    Assembly Version: 1.0.2902.0

    Win32 Version: 5.04.00.2904

----------------------------------------

Microsoft.DirectX

    Assembly Version: 1.0.2902.0

    Win32 Version: 5.04.00.2904

----------------------------------------

ly2pqhc7

    Assembly Version: 1.0.5260.20091

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------

Microsoft.FlightSimulator.SimConnect

    Assembly Version: 10.0.61259.0

    Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)

----------------------------------------

SharpDX.DirectInput

    Assembly Version: 2.6.0.0

    Win32 Version: 2.6.0

----------------------------------------

SharpDX

    Assembly Version: 2.6.0.0

    Win32 Version: 2.6.0

----------------------------------------

System.Web.Services

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)

----------------------------------------

hhz7fgpz

    Assembly Version: 1.0.5260.20091

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------

msvcm80

    Assembly Version: 8.0.50727.6195

    Win32 Version: 8.00.50727.6195

----------------------------------------

j-sygi8u

    Assembly Version: 1.0.5260.20091

    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

 

 

[WR269 367]

Phil, have you added the ASC . DLL file to the Aerosoft Airbus?

 

Also, what aeroplane set are you using with VPILOT? There are some that will produce this type of crash.

[pmb 5,137]

I get .net errors from time to time, too. From my perspective, it seems to be indeed an issue with 3rd party addons. I flew the FSX drifter (imported to Preapr3d2.2) in the recently released ORBX Monterey yesterday and got two .net errors in a row. Next time I selected Ant's drifer along the same route without any issues.

 

I don't recall having had any .net error in 2.2 without having at least one non-Prepar3d2-certified addon active. 

 

Kind regards, Michael

[Baylorguy 39]

Phil, have you added the ASC . DLL file to the Aerosoft Airbus?

 

Also, what aeroplane set are you using with VPILOT? There are some that will produce this type of crash.

 

 

Hi Will -

 

No, have not added the .dll file (I only did a direct install) so I will do some research on that and add it.

 

The set I am using is MyTraffic Professional.

I get .net errors from time to time, too. From my perspective, it seems to be indeed an issue with 3rd party addons. I flew the FSX drifter (imported to Preapr3d2.2) in the recently released ORBX Monterey yesterday and got two .net errors in a row. Next time I selected Ant's drifer along the same route without any issues.

 

I don't recall having had any .net error in 2.2 without having at least one non-Prepar3d2-certified addon active. 

 

Kind regards, Michael

 

That seems to be my experience as well.  Sometimes I am fine and do not have one, other times like last night I put 4 hours into a flight only to have it crash at the end.  I never got these .net errors with FSX.

[pmb 5,137]

Baylorguy, on 01 Jun 2014 - 8:14 PM, said:

imes like last night I put 4 hours into a flight only to have it crash at the end.  I never got these .net errors with FSX.

FSX did not rely in any form on .net. LM started using .net in Prepar3d1 already. I just read a bit in the German Wikipedia on .net (I am not a programmer) and found the remarkable statement one of its aims being to reduce crashes. So that's the theory  :rolleyes:

 

Kind regards. Michael

[WR269 367]

 

 

Hi Will -

No, have not added the .dll file (I only did a direct install) so I will do some research on that and add it.

The set I am using is MyTraffic Professional.

 

Phil, there is a known bug in the AXE on P3D2.2, you need to add the ASC.DLL file to all your panel folders for all models you fly of the Aerosoft Airbus, be them A320 or A321, and dont forget about the Panel Fallback folder. This should fix your issue, as it is not a P3D2.2 issue per se, but the issue is with the Third Party add on.

 

If you are using VPILOT, make sure you keep updating the VMR files as it has been found that some AI models will crash P3D as soon as they get in visual range. Again, this is because the add on is not compatible (most AI aircraft were made for FS9).

 

Hope this helps you a bit.

 

Cheers,

[Baylorguy 39]

FSX did not rely in any form on .net. LM started using .net in Prepar3d1 already. I just read a bit in the German Wikipedia on .net (I am not a programmer) and found the remarkable statement one of its aims being to reduce crashes. So that's the theory  :rolleyes:

 

Kind regards. Michael

 

Ha, that is quite ironic for you and I isn't it?  Hopefully as P3D specific products get released it will help with compatibility.

Phil, there is a known bug in the AXE on P3D2.2, you need to add the ASC.DLL file to all your panel folders for all models you fly of the Aerosoft Airbus, be them A320 or A321, and dont forget about the Panel Fallback folder. This should fix your issue, as it is not a P3D2.2 issue per se, but the issue is with the Third Party add on.

 

If you are using VPILOT, make sure you keep updating the VMR files as it has been found that some AI models will crash P3D as soon as they get in visual range. Again, this is because the add on is not compatible (most AI aircraft were made for FS9).

 

Hope this helps you a bit.

 

Cheers,

 

Thanks Will for the tips.  When you say to update the VMR files, is that when you actually download the rule set?  If so I have not done that in awhile, so will be sure to do that tonight.

[Jim Young 2,356]

FSX did not rely in any form on .net. LM started using .net in Prepar3d1 already. I just read a bit in the German Wikipedia on .net (I am not a programmer) and found the remarkable statement one of its aims being to reduce crashes. So that's the theory  :rolleyes:

 

Kind regards. Michael

Not sure I understand your comments but to clarify.... Microsoft.net is included in every application installed on your computer (unless the proper version is already there). FSX uses Microsoft.net 1.1 (included in FSX Basic/Deluxe), dotnet 2.0, and 3.5. Some of the more recent addons to FSX use dotnet 4.0 and higher. According to Google, Microsoft dotnet is not backward compatible. Developers use Microsoft.net to make sure their application/addon runs in the manner they intended, including memory management (the uiautomationcore.dll is part of the Microsoft dotnet framework packages). If you do not have the version used by the developer for his application, then you should reinstall the application or go to the dotnet website and download the proper version(s). Dotnet works in connection with Microsoft Visuals C++ which also has versions that an installer will install if not already found on your system. FSX uses Microsoft Visual C++ 2005 w/SP1 and 2008. Some addons, like PMDG products are using Microsoft Visual C++ 2010. This program is also not backward compatible (per Google) so you need all versions required by the developers. Microsoft Visuals are used by developers to make sure their application/addon is installed properly in the manner they intended. Windows Update provides security updates for these products.

 

So, if you do not have the right version of these programs (and you may not if you reinstall Windows then copy the FSX/P3D installations you had before you reinstalled Windows), then you could have problems. For instance, FSX will not start up if Microsoft Visual 2005 is uninstalled from your computer.

 

It appears P3DV2.2 uses Microsoft Visual 2012 and I would assume the 4.0 or higher version of Microsoft.net. The AVSIM CTD Guide provides more information about these programs to include the method to determine which versions are located on your computer and links to the proper websites to download the proper versions.

 

Lastly, you need the 32 bit (x86) versions of these programs as FSX/P3D are 32 bit applications.

 

Best regards,

[pmb 5,137]

Thanks Jim for making this clear, I see I was wrong. I just don't recall FSX ever caring during installation if some version of .net is installed or trying to install it, which is what Prepar3d does. In addition, while I had my share of FSX crashes I don't recall .net being responsible for any them.

 

Kind regards, Michael

[Jim Young 2,356]

I really haven't either but I do know that when FSX first came out, the "computer experts" were responding to posts describing CTD's and freezes by telling them to make sure they have Microsoft Visuals 2002 and 2008 installed and Microsoft.net 2.0 and 3.5 so I did a lot of investigating a few years ago (Orbx/FTX once had a direct link to the 3.5 version on their website but now recommend the 4.0 version be installed). If the Microsoft Aces Team were still functioning and issuing upgrades, they would have updated their Microsoft Visuals and dotnets to the latest versions too. So it is important the older versions be installed for FSX. P3D should be using the latest and greatest versions but, if you are installing an older addon made for FSX, like for instance, Captain Sim stuff, their installers probably used an older version of the Microsoft Visuals and dotnets.

 

Best regards,

[mgh 89]

 

 

I just don't recall FSX ever caring during installation....

 

But then my P3D doesn't either. I run P3D and FSX  on the family PC and never ever had the problem. I simply allow Microsoft to update Windows - apart from anything I don't have enough experiience to do it myself.

[pmb 5,137]

If memory serves me right, during installation there pops up a window about checking the corresponding .net 4 and VC 10 runtimes and installing them, if required. 

 

Kind regards, Michael

[mgh 89]

 

 

If memory serves me right...

 

I don't recall such a Window.