November 16, 20232 yr Hi fellow simmers, I am at a loss here. The P2A app will not connect to the sim. I am an experienced user of MSFS and FSUIPC (Or at least I thought I was) I am new to P2A though, but I have been reading the setup guide and watched several Youtube videos to get it right. Here is what I've done sofar: 1. Downloaded the latest versions of both P2A and FSUIPC for MSFS. (P2A ver. 2.6.4.2_x64 and FSUIPC ver. 7.3.25) 2. Assigned a callsign in Config (NAX229). 3. Assigned buttons for PTT and SayIt in Config. 4. Imported a valid OPS flightplan from Simbrief. 5. Verified that FSUIPC is connected to the sim. Being in my aircraft at an airport. (The title for the FSUIPC window reads: Simulator is available: Connected) Pushing the Connect button in P2A does not produce a "green" connect verification. But pushing it twice gives a "Simulator Disconnected" message in the lower right on the P2A screen. - Don't have a registered version of FSUIPC. - Haven't made any config related changes in MSFS. - I believe I don't need a WebSocket Server in FSUIPC. - I believe that the FSUIPC config file does not need to be changed. What am I doing wrong here? Edited November 16, 20232 yr by mortenha69 ----------------------------------------------- Morten Haughom Greetings from the sticks! N70° 22' 23 - E031° 06' 02 Vardø, Norway
November 16, 20232 yr Author Being Impatient for a reply, I am going to attempt a complete reinstall of P2A. It is a long time since I installed this add-on. Let's see what happens 🙂 ----------------------------------------------- Morten Haughom Greetings from the sticks! N70° 22' 23 - E031° 06' 02 Vardø, Norway
November 16, 20232 yr Commercial Member If that does not work, try a different call sign. The one you have does not look correct. Select Airline, then enter NAX in the Airline Code box. Then the Callsign should read NOR Shuttle. Then enter the flight number, 229, in the Flight/Tail number box. If that doesn't do it: ⦁ 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 ⦁ Try running the program in Administrator mode by right clicking on the Pilot2ATC.exe file and selecting “Run as Administrator” ⦁ If connected but the radios aren’t working, check the Battery and Avionics switches on or the “Ignore battery” and “Ignore Avionics” options are checked in P2A Config ⦁ 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. Dave
November 16, 20232 yr Author Yes! It worked! Cannot really point to any reason. The only thing I can think of is possible Microsoft WIN10 updates that made this happen. Purchased the add-on in late April but never used it. Anyway, looking forward to use P2A, really exiting 🙂 Thanx Dave! Edited November 16, 20232 yr by mortenha69 ----------------------------------------------- Morten Haughom Greetings from the sticks! N70° 22' 23 - E031° 06' 02 Vardø, Norway
Archived
This topic is now archived and is closed to further replies.