Delighted to report that Plan-G now works very well in both P3D and FSX. Many thanks Tim. Excellent job.

Spot on, thanks Tim. In my attempts to overcome the crashing problem I had left the connection set to "Pipe". I have now changed back to IPv4 and the above message has gone.

I am now getting this when I run Plan-G with P3D, Tim. Does it off a clue as to how I may solve the problem please? I select OK and everything works fine in P3D but crashes in FSX. Perhaps I should be building a database for FS9 which I have not done so far?

G'day Tim, following on advice that you gave another member, I have done a reinstall of the three SimConnect files in  the winsxs folder but I can not get Plan-G to run in FSX. It crashes as soon as I connect. Working fine in  P3D. Any other ideas please? Thanks, Mac

G'day Tim, is there a "best practice" method of dual installing Plan-G to both FSX and P3D on two different drives please? I can get Plan-G working just fine in P3D but not FSX at the same time. Many thanks, Mac

Restoring certainly works, Tim. Have done that three times already. However the next time I open P3D, which is on a different drive, Plan-G works in P3D but crashes the next time I run FSX, with P3D closed of course. A registry conflict of some sort perhaps because there does not seem to be any Plan-G files on the P3D drive?

But you are not going to tell me how I can break the SimConnect by simply opening and closing P3D, right?

Still working hard to try and solve this one Tim. I went back to basics.  Backed up a solid installation of FSX including Plan-G, REX-E, Saitek etc. all installed on drive C:\. Reformatted drive G:\ and did a clean reinstall of P3D. Opened P3D and closed it again. Went back to FSX opened it and once again Plan-G crashes as soon as I connect to FSX.

The thing that beats me Tim, is that if I then go back to P3D and open Plan-G it does NOT crash and follows the aircraft OK.

Here logs, help please. Mac

Faulting application name: PlanG.exe, version: 2.0.5.493, time stamp: 0x4d836f53
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319
Exception code: 0xe0434352
Fault offset: 0x0000b9bc
Faulting process id: 0x1ac4
Faulting application start time: 0x01cd46b56a330a61
Faulting application path: C:\TA Software\Plan-G v2\PlanG.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: adf2737e-b2a8-11e1-959a-50e549e6624d

Application: PlanG.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
   at System.RuntimeMethodHandle._InvokeMethodFast(System.IRuntimeMethodInfo, System.Object, System.Object[], System.SignatureStruct ByRef, System.Reflection.MethodAttributes, System.RuntimeType)
   at System.RuntimeMethodHandle.InvokeMethodFast(System.IRuntimeMethodInfo, System.Object, System.Object[], System.Signature, System.Reflection.MethodAttributes, System.RuntimeType)
   at System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, Boolean)
   at System.Delegate.DynamicInvokeImpl(System.Object[])
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
   at System.Threading.ExecutionContext.runTryCode(System.Object)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(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 MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.InvokeImpl(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 PlanG._Main.Main()

Sorry Tim, I spoke too soon. Worked perfectly for an hour then went back to crashing on Connect.

I seem to have discovered that two completely separate Plan-G installations fixes the problem. I have aimed via the Options --> Locations the two copies to the two different drives one with FSX and the other with P3D.  I also have two different start Icons on my Task Bar.

Cheers, Mac

Thanks Tim. I have FSX and P3D on two separate drives. Plan-G is working in P3D but crashing in FSX. Crazy ...

Your assistance please. I have installed P3D but have not yet run the program. Now every time I try to connect Plan-G in FSX it crashes. Should also mention that I have tried FS Connection Option at SimConnect, FSUIPC and Auto. It was working fine on Auto. Application Log follows:

Application: PlanG.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
   at System.RuntimeMethodHandle._InvokeMethodFast(System.IRuntimeMethodInfo, System.Object, System.Object[], System.SignatureStruct ByRef, System.Reflection.MethodAttributes, System.RuntimeType)
   at System.RuntimeMethodHandle.InvokeMethodFast(System.IRuntimeMethodInfo, System.Object, System.Object[], System.Signature, System.Reflection.MethodAttributes, System.RuntimeType)
   at System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, Boolean)
   at System.Delegate.DynamicInvokeImpl(System.Object[])
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
   at System.Threading.ExecutionContext.runTryCode(System.Object)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(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 MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.InvokeImpl(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 PlanG._Main.Main()

Ok I found it thanks.

Thanks, where do I find the program, Tim.

In the meantime I managed to get this file which was referenced in a crash

<?xml version="1.0" encoding="UTF-16"?>
-<WERReportMetadata> -<OSVersionInformation>
<WindowsNTVersion>6.1</WindowsNTVersion> <Build>7601 Service Pack 1</Build> <Product>(0x3): Windows 7 Home Premium</Product> <Edition>HomePremium</Edition> <BuildString>7601.17640.amd64fre.win7sp1_gdr.110622-1506</BuildString>
<Revision>1130</Revision>
<Flavor>Multiprocessor Free</Flavor> <Architecture>X64</Architecture> <LCID>1033</LCID> </OSVersionInformation> -<ProblemSignatures> <EventType>APPCRASH</EventType>
<Parameter0>fsx.exe</Parameter0>
<Parameter1>10.0.61637.0</Parameter1>
<Parameter2>46fadb14</Parameter2>
<Parameter3>ai_player.dll</Parameter3>
<Parameter4>10.0.61637.0</Parameter4>
<Parameter5>46fadb57</Parameter5>
<Parameter6>c0000005</Parameter6>
<Parameter7>00037489</Parameter7> </ProblemSignatures>
-<DynamicSignatures> <Parameter1>6.1.7601.2.1.0.768.3</Parameter1>
<Parameter2>1033</Parameter2>
<Parameter22>0a9e</Parameter22>
<Parameter23>0a9e372d3b4ad19135b953a78882e789</Parameter23>
<Parameter24>0a9e</Parameter24>
<Parameter25>0a9e372d3b4ad19135b953a78882e789</Parameter25> </DynamicSignatures>
-<SystemInformation> <MID>7767AEA9-F80A-48F5-AD6C-B402AA5D4C1A</MID> <SystemManufacturer>Gigabyte Tecohnology Co., Ltd.</SystemManufacturer> <SystemProductName>X79-UD5</SystemProductName> <BIOSVersion>F3</BIOSVersion> </SystemInformation> </WERReportMetadata>

Tim,

I did another uninstall via the Win7 Control Panel, reinstall and build the Database. Now things seem to be working OK again. Certainly there have been no new crashes in the last fifteen minutes.

Mac