Installing Pilot2ATC to work with MSFS 2020

[Bedders1983 0]

Hello Dave, i have just sent the settings.xml file to admin, how long will it take and thankyou for doing this i apprehciate it, what happens now then Dave?

Regards

Edited September 5, 2020 by Bedders1983

[Worgi 0]

HI,

 

Buyed now! With the Paypal Account from my Wife haha 😛

 

Thanks for your effort!

Daniel

[Petraeus 147]

Are we restricted to NOAA weather?

[WashkraenK 0]

Hello Dave and Hello Pete

I am writing you guys from the north of germany. I am a big fan of Dave's great pilot2atc. I used it for a long time and still with X-plane 11 on a notebook via widexp while the sim is running on my powerful main-computer. This one I powered up with new hardware for a lot better performance in X-Plane 11 and MSFS 2020. When I heard that there is a way to get pilot2atc connected with msfs 2020 I directly tried to get it working. Dave wrote that we need WideFS so I bought it from simmarket. I also bought accidentally FSUIPC4(perhaps later there will be a way to get a discount from Pete on FSUIPC7 when it is released). On my Sim-PC I installed the FSUIPC7beta and on my notebook I installed the WideFS7. In both firewalls I allowed FSUIPC7 and WideFS to pass through. I even  opened the ports 8002 and 9002 in my router portforwarding-settings. Sadly I get no connection and I cannot find out why. It is very difficult for me as a non native english speaking guy to find out by reading Pete's Manuals what I do wrong. When I open WideFS7 there is a only grey window and in the title it says: WideClient FS98 - Waiting for a connection. So perhaps can you both help me to get it working? I really need your help!  

[Dave-Pilot2ATC 875]

Pete will have to answer this one.  The FSUIPC7 beta for MSFS2020 does not include a WideFS, so I don't know if the separately available WideFS 7 is compatible.

Dave

[Dave-Pilot2ATC 875]

I would certainly recommend using Real Weather in MSFS2020 and NOAA Weather in P2A to keep the weather in sync in the two programs.  

[DocPadds 15]

6 hours ago, Dave-Pilot2ATC said:

Pete will have to answer this one.  The FSUIPC7 beta for MSFS2020 does not include a WideFS, so I don't know if the separately available WideFS 7 is compatible.

Dave

It is, he includes info on how to put your WideFS license in the key file for FSUIPC

[Pete Dowson 558]

22 hours ago, WashkraenK said:

On my Sim-PC I installed the FSUIPC7beta and on my notebook I installed the WideFS7. In both firewalls I allowed FSUIPC7 and WideFS to pass through. I even  opened the ports 8002 and 9002 in my router portforwarding-settings. Sadly I get no connection and I cannot find out why. It is very difficult for me as a non native english speaking guy to find out by reading Pete's Manuals what I do wrong. When I open WideFS7 there is a only grey window and in the title it says: WideClient FS98 - Waiting for a connection.

Assuming you bought a registration for WideFS and entered it into your FSUIPC7.KEY file as in the instructions, then there's some access problem. But you'll need to ask on the FSUIPC support forum and supply log files -- FSUIPC7.LOG, WideServer.LOG and WideClient.LOG.

FSUIPC7 is 3 complete versions later than FSUIPC4 and 14 years later. There can be no discount really.

Incidentally, it is John Dowson's product, not mine.

Pete

 

[WashkraenK 0]

Thank you both for the quick answers. I'll keep trying to get it to work. Maybe I can do it. Or maybe somebody else will write here how he did it. Thanks in advance!

[david87116 0]

Hello, so for some reason MFS2020 seems to crash whenever I start FSUIPC 7 exe. Any idea what it could be?. It worked for one flight then all of a sudden it just crahses, I launch pilot2ATC then MFS2020 and FSUIPC7. I can get to the world map to pick the airports but when I hit ready to fly abd it starts to load it crashes. I dont know if this log file works, so sorry if this isnt helpful or if im not supposed to paste this here

 

Checking the Registrations now ...
User Name="MSFS Tester"
User Addr="Time Limited 311020"
FSUIPC7 Key is provided
WIDEFS7 not user registered, or expired
       16 System time = 07/09/2020 16:26:17
       16 FLT path = "C:\Users\dace8\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\"
       47 -------------------------------------------------------------------
       63 Registered default HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
       94 FS path = "E:\msx\"
       94 ---------------------- Joystick Device Scan -----------------------
       94 Product= TWCS Throttle
       94    Manufacturer= Thrustmaster
       94    Vendor=044F, Product=B687 (Version 1.16)
      125    GUIDs returned for product: VID_044F&PID_B687:
      125       GUID= {AE690EF0-B560-11EA-8002-444553540000}
      125       Details: Btns=14, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z65535
      125 Product= T.16000M
      125    Manufacturer= Thrustmaster
      125    Vendor=044F, Product=B10A (Version 5.0)
      125    GUIDs returned for product: VID_044F&PID_B10A:
      125       GUID= {AE67D670-B560-11EA-8001-444553540000}
      125       Details: Btns=16, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255
      125 -------------------------------------------------------------------
      125 Device acquired for use:
      125    Joystick ID = 2 (Registry okay)
      125    2=TWCS Throttle
      125    2.GUID={AE690EF0-B560-11EA-8002-444553540000}
      125 Device acquired for use:
      125    Joystick ID = 0 (Registry okay)
      125    0=T.16000M
      125    0.GUID={AE67D670-B560-11EA-8001-444553540000}
      125 -------------------------------------------------------------------
      203 LogOptions=00000000 00000001
    27063 Simulator detected
    96766 SimConnect_Open succeeded
    96766 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
    96766 MSFS version = 11.0.282174.999
    96766 Initialising SimConnect data requests now
    97938 Aircraft loaded: running normally now ...
   103735 User Aircraft ID not supplied -- trying default
   153891 E:\msx\Official\OneStore\asobo-aircraft-kingair350\SimObjects\Airplanes\Asobo_KingAir350\aircraft.CFG
   154125 flights\other\MainMenu.FLT
   157172 System time = 07/09/2020 16:28:54, Simulator time = 19:27:00 (20:27Z)
   157172 Aircraft="Beechcraft King Air 350i Asobo"
   167078 -------------------- Starting everything now ----------------------
   191813 E:\msx\Official\OneStore\asobo-aircraft-c172sp-as1000\SimObjects\Airplanes\Asobo_C172sp_AS1000\aircraft.CFG
   191813 Sim stopped: average frame rate for last 32 secs = 153.9 fps
   191813    Max AI traffic was 1 aircraft
   191813 -------------------------------------------------------------------
   192516 Aircraft="Cessna Skyhawk G1000 Asobo"
   193735 Planned flight from KEWR to KJFK
   193735 C:\USERS\DACE8\APPDATA\LOCAL\PACKAGES\MICROSOFT.FLIGHTSIMULATOR_8WEKYB3D8BBWE\LOCALSTATE\MISSIONS\CUSTOM\CUSTOMFLIGHT\CUSTOMFLIGHT.PLN
   194422 C:\Users\dace8\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
   279985 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B
   279985 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B
   282063 MSFS no longer running - exiting
   282063 === Hot key unregistered
   282063 === Stop called ...
   282078 === Closing external processes we started ...
   283078 === About to kill any Lua plug-ins still running ...
   283219 === Closing global Lua thread
   284235 === About to kill my timers ...
   284438 === Restoring window procs ...
   284438 === Unloading libraries ...
   284438 === stopping other threads ...
   284438 === ... Button scanning ...
   284531 === ... Axis scanning ...
   284641 === Releasing joystick devices ...
   284641 === Freeing macro memory
   284641 === Removing any offset overrides
   284641 === Clearing any displays left
   284641 === Calling SimConnect_Close ...
   284844 === SimConnect_Close done!
   284844 === AI slots deleted!
   284844 === Freeing button memory ...
   284844 === Closing my Windows ...
   284844 === Freeing FS libraries ...
   285844 === Closing devices ...
   285844 === Closing the Log ... Bye Bye! ...
   285844 System time = 07/09/2020 16:31:03
   285844 *** FSUIPC log file being closed
Minimum frame rate was 28.8 fps, Maximum was 178.9 fps
Average frame rate for running time of 152 secs = 118.3 fps
Maximum AI traffic for session was 194 aircraft
Traffic deletions 0 aircraft
Memory managed: 1 Allocs, 1 Freed
********* FSUIPC Log file closed ***********
 

[kkaybe 0]

I don't get any replies or responses from the ATC in MSFS2020, would be nice if somebody could create an install & setup video for MSFS20

[Petraeus 147]

I've connected, got ATIS, filed the plan, but then get no answer to my request for clearance. Any thoughts?

[Dave-Pilot2ATC 875]

Have a look at the first post in this thread.  I just added a video that Clumsy made that should help with the setup.

Dave

[Dave-Pilot2ATC 875]

If you are connecting, but not able to get a response from ATC, then there are some other things you can try.

1. SWITCH SETTINGS: Check to be sure the Power indicator in the bottom left of the main P2A screen is  green.  If not, then you need to turn on the battery switch and avionics switch in the aircraft, or if that doesn’t turn it green, check the 2 options “Ignore Battery Switch” and “Ignore Avionics Switch” in the Config P2A Setup panel.
2. VALID CALL SIGN: Make sure you are using a valid call sign by changing it to the default Mfg: Beech; Tail Number: N431VB and pressing the Save Button.  You can send me a screenshot of this page and I will let you know if there is a problem with the call sign.
3.  VALID FREQUENCY: Be sure you have a valid frequency showing in the Active frequency display.  Open the Radio Panel and check that the frequency selected has a valid controller assigned.  Try swapping the active and standby frequencies a couple of times.
4. PTT BUTTON: Use the PTT button on the main screen to eliminate the possibility of it being the Joystick button setup as the issue
5. VALID PHRASES: Make sure the phrase you are using is appropriate for the controller.  “Say Altimeter” should work with all controllers, so use it.
6. VOLUME SETTINGS: Check the Windows Volume Mixer and be sure Pilot2ATC volume is turned up. (While P2A is running, rIght click on the speaker icon in the task bar and select Volume Mixer).  Also check the volume of the voices in P2A Config.  On the Communications tab of the Sound dialog, be sure "Do Nothing" is checked for when Windows detects Communications activity.
7. HEADSET AS DEFAULT PLAYBACK AND RECORDING DEVICE: If you have a headset mic set as the default Recording/Audio Input device, be sure and set the Headset as the Default Playback/Audio Output device.  Some users have had their microphone not working because  they set their Speakers as the Playback device.  
8. DEFAULT COMMUNICATIONS DEVICE: If using a headset as the default Playback/Recording device, be sure it is not also being used as the Default Communications Device.  This assignment of multiple duties seems to cause a problem.  Likewise, be sure the microphone is not assigned to any other duties besides the default audio input device.
9.  GRAMMAR HELP SCREEN AND DIAGNOSTICS: Try using the Grammar Help screen.  
   1. Press the Grmr Help button to the right of the Flight Plan
   2. Pess the Practice button 
   3.  Take a screenshot of the resulting Message box with the connection information and email to me 
   4. Try saying "Say Altimeter" with no other words.  It should be recognized.  Let me know the result.
   5. If not being recognized, press the "Replay" button and see what your voice sounds like.  If no sound, then your voice is not getting through to Pilot2ATC.
10. SOUND DRIVERS AND ADD ON PROGRAMS - Many PCs come with Sound Add On programs from the manufacturer that are run at startup.  Some of these programs may "Capture" the microphone and prevent Pilot2ATC from hearing it.  Also, some addons may have such features.  Check to be sure there are not other sound programs running.  Also be sure that you have the latest Audio Drivers for your Microphone installed.
     

[Petraeus 147]

4 hours ago, Dave-Pilot2ATC said:

Check to be sure the Power indicator in the bottom left of the main P2A screen is  green.  If not, then you need to turn on the battery switch and avionics switch in the aircraft, or if that doesn’t turn it green check the 2 options “Ignore Battery Switch” and “Ignore Avionics Switch” in the Config P2A Setup panel.

Many thanks. That was the problem. Although all the avionics in the MSFS A320 are all switched on, P2ATC doesn't recognise that fact.

Edited September 8, 2020 by Petraeus