I've been using Pilot2ATC for some time now, I use it every flight with MS FS2020 and I fly almost every day. Today it stopped fully connecting to the sim. Connect box does not turn green anymore. I've tried a lot of things, searched through the foruns, found a list of eight things to check but could not solve the problem. I have even re-installed the software, but it did not help.

I've been monitoring P2A logs and everytime I click connect, this is the output:

Loading Joystick Devices - 4 devices loaded.
Loading Joystick Devices - 4 devices loaded.
Loading Joystick Devices - 4 devices loaded.
Loading Joystick Devices - 4 devices loaded.
Joystick Device number 3 successfully activated.
Joystick Device number 3 successfully activated.
Joystick Device number 0 successfully activated.
Joystick Device number 0 successfully activated.
Pilot2ATC_2020.exe	Information	0	SAPI does not implement phonetic alphabet selection.	   at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at System.Diagnostics.TraceEventCache.get_Callstack()
   at Microsoft.VisualBasic.Logging.FileLogTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message)
   at System.Diagnostics.TraceInternal.TraceEvent(TraceEventType eventType, Int32 id, String format, Object[] args)
   at System.Speech.Recognition.RecognizerBase.Initialize(SapiRecognizer recognizer, Boolean inproc)
   at System.Speech.Recognition.SpeechRecognitionEngine.get_RecoBase()
   at P2A_2020.ATCListener.LoadPilotGrammar()
   at P2A_2020.ATCListener.Init()
   at P2A_2020.frmP2AMain.c2124c4ff01169d49362f23ceb404afd0()
   at P2A_2020.frmP2AMain.c6da96e2c3dc97ecb14521624b5c07984()
   at P2A_2020.frmP2AMain.c6f50794713ca1994f16f21230b6819d6(Object cb25b07786a6e786dea76cf87175f59f0, EventArgs cb4d4bf05d278f00a41fc902f6c5d26a2)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at A.c4f7f2103942aab5c40ccc705b2e009a9.c39e4a2c7012e9e0ba9055469c605637a()	""	13580	1	1968810948688
No controller assigned 01:48:09
Error in ATCListener SetResponderType
System.ArgumentNullException: Value cannot be null.
Parameter name: source
   at System.Linq.Enumerable.Distinct[TSource](IEnumerable`1 source)
   at P2A_2020.ATCListener.SetResponderType()
SIM Version Num: 13; SIM Version: P3D
SIM Rate Changed: 1

I think the problem might be here:

Error in ATCListener SetResponderType
System.ArgumentNullException: Value cannot be null.
Parameter name: source
   at System.Linq.Enumerable.Distinct[TSource](IEnumerable`1 source)
   at P2A_2020.ATCListener.SetResponderType()

I compared this log with the old logs, and this error was not logged before.

Any ideas of what could it be?

 

Thanks for the report.  I found the bug causing this error message and fixed it for the next release.

In the meantime, try starting at a different airport.  It would appear this has something to do with the program not finding valid Com frequencies.  The other thing to try is setting the radios in the cockpit to a valid local frequency before connecting.

Dave

Thanks Dave,

 I'll try that and report back.

 

Setting the radio in the simulator to a valid frequency before connecting solved the problem. Curious is that the airport I am departing from (SBKP) have several frequencies listed in Pilot2ATC (info screen).

 

This regularly occurs to me, too with the same error logged. But not when connecting initially but several times over the north atlantic while in a transatlantic flight. Reconnecting manually works then always. I hope that's the same bug and it will be fixed in the next release.

Best regards, Alexander