I recently reinstalled FSUIPC to a different drive and had to install a beta version so it would work with FSFO Next for MSFS and now P2ATC doesn't connect to MSFS. I'm just wondering if it has something to do with installing FSUIPC to a different drive or if it's because it's a beta version?

It might be a problem with the FSUIPC beta, but generally, P2A works with any version of FSUIPC and doesn't care where it's installed, as long as it's on the same PC and is up and running when you try to connect.

I would check to be sure FSUIPC and MSFS are up and running and you are in the cockpit of the aircraft before you try and connect.

Dave

It's weird, I never had this issue before. When I try to connect it chimes like it's connected but it's not. Then I hit the connect button and it chimes and the info box says disconnected.

It should say "Disconnected" the second time because that button Connects on the first press and Disconnects on the second.

Other things than FSUIPC to check for not connecting are:

⦁    Be sure the SIM is fully up and running and not paused before you try to connect.  The cockpit must be showing.
⦁    Be sure you are connected to the internet. It must be a reliable connection.
⦁    English-US Language installed and set as Primary Language, English Speech Recognition installed also.
⦁    Working Microphone installed and set as Default Sound Input device in Windows
⦁    Valid Call Sign – Try using the default call sign of Mfg: Beech; Tail Number: N431VB.  Press the Save button.
⦁    Try running the program in Administrator mode by right clicking on the Pilot2ATC.exe file and selecting “Run as Administrator”
⦁    If it seems to partially connect but the Connect button does not turn Green, set the Weather option to a different source such as NOAA Real Time Weather and try again.
⦁    If still won't fully connect, try deleting the AppConfig.xml file.  You will lose your Config settings, but some users have reported that this fixed their connection issue.  The file is located at: 
        c:\users\<UserName>\AppData\Roaming\P2A_200\Settings\AppConfig.xml
        where <UserName> is your PC user name.  Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab.
⦁    If connecting to MSFS, one user reported that setting FSUIPC WASM to Enabled fixed it for them.
 

What messages are in the speech text box when you press it the first time?

Dave

Edited August 28, 20223 yr by Dave-Pilot2ATC

I'll try deleting the AppConfig.xml file because all of the other things are done. WASM is enabled because FSFO NEXT requires it.