September 24, 20178 yr After today's update to v0.3.144 I got the following error on exit of P3D V4: Application: ChasePlane.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at <Module>.SimConnect_CallDispatch(Void*, Void (SIMCONNECT_RECV*, UInt32, Void*), Void*) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(Microsoft.FlightSimulator.SimConnect.SignalProcDelegate) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveMessage() at OP_Janet_Library.CP_SimConnect.A(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at System.Windows.Application.Run(System.Windows.Window) at ChasePlane.App.Main() Faulting application name: ChasePlane.exe, version: 0.3.144.0, time stamp: 0x59b9c8b7 Faulting module name: SimConnect.dll, version: 10.0.61637.0, time stamp: 0x46fad5b6 Exception code: 0xc0000005 Fault offset: 0x00001f8b Faulting process id: 0x9bc Faulting application start time: 0x01d335798ece16a6 Faulting application path: D:\OldProp Solutions Inc\ChasePlane\ChasePlane.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll Report Id: 67e3f0bb-bb16-450c-89d2-fbea3bfe3d7b Faulting package full name: Faulting package-relative application ID: Cheers, Rob.
September 25, 20178 yr Commercial Member Interesting one, thanks for the info! Keven Menard Technical Director, //42.
March 28, 20188 yr Since I have installed Chaseplane in the beginning of this year, I am getting CTDs of P3Dv4 more often when in the past. If I then go to the event viewer, it is reporting a crash of Framework v4.0.30319, followed by a crash of terrain.dll, panel.dll or atc.dll. So far I didn't found a solution for these CTDs. Could this be in connection with Chaseplane? Is Chaseplane requiring Framework v4.0.30319? Would Chaseplane work without Framework Framework v4.0.30319? Regards, Arndt Arndt Laube P3Dv4.5 and P3Dv5 Brunner CLS-E Yoke & Rudder, 2x Logitech Throttle, several GoFlight modules Intel i7 9700K, 16 GB RAM, Geforce 1080Ti, monitors 3840 x 2160 and 1360 x 768
Archived
This topic is now archived and is closed to further replies.