Sign in to follow this  
Kaarel Hauk

P3D V3 CTD's caused by vPilot, SimConnect or RAAS?

Recommended Posts

Dear Community,

I have been getting these CTD's in P3D v3 during at least every second long haul flight where the sim just closes itself in an instant. This has happened only with PMDG's 777 - as I don't fly much of anything else I can't say that this is only 777 related. 

I have read about cases where people have extended thei PFD's and their sim would crash but I have not been able to determine such pattern. Most recent crach being on descent to RJAA clicking nothing and one before that pulling to gate at VHHH after a flight from EGLL and switching to external view. Now initally I figured this was a vPilot issue but now I am not so sure and when you look at my error log you will see why. Never had this issue in v2.5 and I am out of ideas.

So here's what I got immediately after crash.

https://drive.google.com/file/d/0B-glOgs-jmbMd0dKRDJoRkctbGM/view?usp=sharing

Which contains this:
"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 bo.x()
at by.h(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.8669 (QFE.050727-8600)

----------------------------------------
vPilot
Assembly Version: 1.1.5678.20264
Win32 Version: 1.1.5678.20264

----------------------------------------
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.8662 (QFE.050727-8600)

----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8663 (QFE.050727-8600)

----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.8674 built by: QFE

----------------------------------------
Anonymously Hosted DynamicMethods Assembly
Assembly Version: 0.0.0.0
Win32 Version: 2.0.50727.8669 (QFE.050727-8600)

----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------
lze1sbuh
Assembly Version: 1.1.5678.20264
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

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

----------------------------------------
zx3u1gls
Assembly Version: 1.1.5678.20264
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------
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.3.0
Win32 Version: 2.6.3

----------------------------------------
SharpDX
Assembly Version: 2.6.3.0
Win32 Version: 2.6.3

----------------------------------------
System.Web.Services
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------
wzktgt6s
Assembly Version: 1.1.5678.20264
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------
msvcm80
Assembly Version: 8.0.50727.9185
Win32 Version: 8.00.50727.9185

----------------------------------------
hscuevf3
Assembly Version: 1.1.5678.20264
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

----------------------------------------
Newtonsoft.Json
Assembly Version: 6.0.0.0
Win32 Version: 6.0.8.18111

----------------------------------------
System.Runtime.Serialization
Assembly Version: 3.0.0.0
Win32 Version: 3.0.4506.8674 (QFE.030729-8600)

----------------------------------------
System.Xml.Linq
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.8674 built by: QFE

----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)

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

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

In the event log I found the following. Don't know what to make of it. Is it RAAS or vPilot or something else?

https://drive.google.com/file/d/0B-glOgs-jmbMVWVfNmhxX1dJa1U/view?usp=sharing

https://drive.google.com/file/d/0B-glOgs-jmbMSXFQZHp0SHRqS0E/view?usp=sharing

V3 is the sim of my choise despite this and FSUIPC provides a good contingency with saving PMDG panel state but sill I would like to find a solution to this.

Everyones help is very much appreciated!

Best Regards,
Kaarel
 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

vPilot crashed because P3D crashed, not the other way around.

 

Cheers!
 

Luke

Share this post


Link to post
Share on other sites

Thanks, Luke!

 

From what I provided is there any indication on why P3D might have crashed. I have included screens from Event viewer which has RAAS and Simconnect errors. Don't know what to do about that though.

Kaarel

Share this post


Link to post
Share on other sites

Doubt it's RAAS.  We have a huge user base in the tens of thousands.  Reports of RAAS issues are almost nill.

Share this post


Link to post
Share on other sites

Hard to guess.

 

Have you disabled any Services in Windows?

 

Some people, in an effort to eek out every bit of performance in their computer, sometimes start shutting down Windows services, and this of course plays havok with various programs.

Share this post


Link to post
Share on other sites

do you have Simconnect 60905 installed? "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\redist\Interface\FSX-RTM\retail\lib\SimConnect.msi"

Share this post


Link to post
Share on other sites

Hard to guess.

 

Have you disabled any Services in Windows?

 

Some people, in an effort to eek out every bit of performance in their computer, sometimes start shutting down Windows services, and this of course plays havok with various programs.

No I haven't.

 

 

do you have Simconnect 60905 installed? "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\redist\Interface\FSX-RTM\retail\lib\SimConnect.msi"

I have the one from the FSX-SP2-XPACK folder. Figured it would be a more up to date version. Might this be causing the issue?

Share this post


Link to post
Share on other sites

The error says "failed to connect to 60905", SP2 is 61259.

 

P3D only installs esp.simconnect: 1.0.20.0, you should also have simconnect RTM, SP1, and SP2 installed.

Share this post


Link to post
Share on other sites

Generally, you shouldn't have to install the legacy SDKs.

 

If there was a problem with the SDK, RAAS would not connect to Flight Simulator, and you would see an error in the RAAS log file.

Share this post


Link to post
Share on other sites

We install legacy simconnect versions because various addons might communicate with various versions, and will fail with a connect error if the correct version simconnect is not present on the system. Some addons written specifically for P3D might use esp.simconnect: 1.0.20.0, and users of P3D and these addons need take no further action.

However many addons written to work with FSX might use 60905, 61242, or 61259. Those that are written recently to work with FSX+A, Gold, SE, or P3D v2/3 often utilise SP2 61259, for example the PMDG 777 and 737 for P3D. Some addons may also work with FSX Standard or Deluxe on SP1 61242, which also work with P3D. Some even work specifically with original version RTM 60905. Generally it's best to install all three legacy versions as they say in the PMDG instructions:


"
1) Navigate to this folder:
<P3D root folder>\redist\FSX-RTM\lib

2) Run the SimConnect.msi installer file inside the folder.

3) Navigate to this folder:
<P3D root folder>\redist\FSX-SP1\lib

4) Run the SimConnect.msi installer file inside the folder.

5) Navigate to this folder:
<P3D root folder>\redist\FSX-SP2-XPACK\lib

5) Run the SimConnect.msi installer file inside the folder.


Once you have all six steps completed, you should be all set!
"


This is is the list of simconnects that should be found on the system:

microsoft.esp.simconnect: 1.0.20.0, Simconnect.dll: 1.0.195.0
microsoft.flightsimulator.simconnect: 10.0.60905.0, Simconnect.dll: 6.2.60905.0
microsoft.flightsimulator.simconnect: 10.0.61242.0, Simconnect.dll: 6.2.61355.0
microsoft.flightsimulator.simconnect: 10.0.61259.0, Simconnect.dll: 6.2.61637.0

Share this post


Link to post
Share on other sites

We install legacy simconnect versions because various addons might communicate with various versions, and will fail with a connect error if the correct version simconnect is not present on the system. Some addons written specifically for P3D might use esp.simconnect: 1.0.20.0, and users of P3D and these addons need take no further action.

 

However many addons written to work with FSX might use 60905, 61242, or 61259. Those that are written recently to work with FSX+A, Gold, SE, or P3D v2/3 often utilise SP2 61259, for example the PMDG 777 and 737 for P3D. Some addons may also work with FSX Standard or Deluxe on SP1 61242, which also work with P3D. Some even work specifically with original version RTM 60905. Generally it's best to install all three legacy versions as they say in the PMDG instructions:

 

 

"

1) Navigate to this folder:

<P3D root folder>\redist\FSX-RTM\lib

 

2) Run the SimConnect.msi installer file inside the folder.

 

3) Navigate to this folder:

<P3D root folder>\redist\FSX-SP1\lib

 

4) Run the SimConnect.msi installer file inside the folder.

 

5) Navigate to this folder:

<P3D root folder>\redist\FSX-SP2-XPACK\lib

 

5) Run the SimConnect.msi installer file inside the folder.

 

 

Once you have all six steps completed, you should be all set!

"

 

This is is the list of simconnects that should be found on the system:

 

microsoft.esp.simconnect: 1.0.20.0, Simconnect.dll: 1.0.195.0

microsoft.flightsimulator.simconnect: 10.0.60905.0, Simconnect.dll: 6.2.60905.0

microsoft.flightsimulator.simconnect: 10.0.61242.0, Simconnect.dll: 6.2.61355.0

microsoft.flightsimulator.simconnect: 10.0.61259.0, Simconnect.dll: 6.2.61637.0

Thank you very much, Steve! I will definitely give it a try and report back.  :smile:

Share this post


Link to post
Share on other sites

It's worth trying since the error suggests something is trying to invoke simconnect with 60905. If it's not installed, or something's wrong with it, then you may get those errors popping up at any time. It's possible you've got it installed already and some program using that version happens to fail through itself or some other program stopping it. At least if you got all the versions installed, they're there for when you try out any addons that might use them. And there's no harm having as many versions as you got file name extensions, makes no difference. If there's an error reported with any version of simconnect, it's because it's maybe not installed, or some program is using it incorrectly.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this