I just bought ChasePlane a few hours ago and started doing a test flight. After about 10-15 minutes of use, ChasePlane will decide to crash... Since it doesn't crash P3d (Like EZdok always did, which is the whole reason i got ChasePlane anyway), I can simply restart ChasePlane and all will be fine for another 10-15 minutes.

 

I'm running P3d v3

FSLabs a320

Here is what comes up in Event viewer:

Application: ChasePlane.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 717B896F (71600000) with exit code 80131506.

 

Faulting application name: ChasePlane.exe, version: 0.1.692.0, time stamp: 0x58ee1a56
Faulting module name: clr.dll, version: 4.6.1637.0, time stamp: 0x586fe5cd
Exception code: 0xc0000005
Fault offset: 0x001b896f
Faulting process ID: 0x24b0
Faulting application start time: 0x01d2b40897335489
Faulting application path: C:\Program Files (x86)\OldProp Solutions Inc\ChasePlane\ChasePlane.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report ID: 89320bbb-e6a1-409a-9256-219104f850e1
Faulting package full name: 
Faulting package-relative application ID: 

Faulting application name: ChasePlane.exe, version: 0.1.692.0, time stamp: 0x58ee1a56
Faulting module name: ntdll.dll, version: 10.0.14393.479, time stamp: 0x58256ca0
Exception code: 0xc0000005
Fault offset: 0x00026dc9
Faulting process ID: 0x15dc
Faulting application start time: 0x01d2b40732368c95
Faulting application path: C:\Program Files (x86)\OldProp Solutions Inc\ChasePlane\ChasePlane.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 35ea6439-c50c-44ca-9f41-1cab6d513d44
Faulting package full name: 
Faulting package-relative application ID: 

Application: ChasePlane.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at SlimDX.DirectInput.Mouse.GetCurrentState(SlimDX.DirectInput.MouseState ByRef)
   at SlimDX.DirectInput.Mouse.GetCurrentState()
   at OP_Janet_Library.CP_Inputs.cam_input_proc()
   at DynamicClass.CallSite.Target(System.Runtime.CompilerServices.Closure, System.Runtime.CompilerServices.CallSite, System.Object)
   at ChasePlane.MainWindow.highFreq_timer_tick(Int32, Int32, Int32, Int32, Int32)

Any advice?

Hi,

The next update will contain a fix that might resolve this issue.
If it does not, let me know.

Regards,
Keven

Seems to have worked, thanks!

Any time frame on the next update Kevin? I'm having the same issues with Chaseplane dropping out. It's great software, but just a tad painful when it drops.......it is only in alpha stage albeit, so patience is the key. :-)

The other "issue" I'm having is with about 15 mins of non activity, the Chaseplane view suddenly changes to an outside view, which can only be reverted back with a mouse movement. Any clues? I rather fancy it's in my settings somewhere, but at this early stage I havn't a clue where to look....... :-)