Good morning Dave,

Thanks for the link. We did the installation this morning, but still the same result.
Still the same problem where it is impossible to change the frequency which remains blocked at an airport which is not the one of departure. 

For your information, we tried to change country, select another plane, but it's the same problem.

I can also offer you a connection on our system, we use Anydesk, we don't speak English well, 
but with the translator we could communicate?

Sincerely.

I went back through your messages and checked the FSUIPC website.  It appears you might be using the wrong version of FSUIPC.  For P3D V3 which you said you have, you should be using FSUIPC v4, not v5.  FSUIPC v5 says it's only for P3D V4.

So, I would uninstall FSUIPC and then do a fresh install of FSUIPC v4.  Since your symptoms are all related to not being able to connect, this change will hopefully solve the problem.

Dave

There may be a mistake in what I explained but we are using P3D V4 and FSUIPC V5.157

Have you tried using FSUIPC v6?  It supports P3D V4 also and maybe it will allow you to get connected.

Dave

 

No, it's a test that we're going to do.

Hello Dave, 

We still haven't had any results despite purchasing FSUIPC6.

We've decided to test version 2 (P2ATC V2) as soon as possible
 to see if this is a problem with version 3.

I'll give you more information after this test.

 

François.

Did you try to launch p2A as administrator?

Hello Watin,

Yes, we tried and kept this option.

Thank you.

Hello Dave,

As promised, we've tested version 2, which works wonderfully with our system.

I think this situation would be interesting for the developers to fix this bug in version 3, which will certainly affect other customers.

Regarding us, what do you think we should do?

Sincerely,

Here are some common things that cause problems connecting.  You may have already tried several of these and the last one probably doesn't apply.  Check each of them and hopefully one of them will be the problem:

1. Be sure you are connected to the internet. It must be a reliable connection.
2. Be sure your installation is not corrupted.  Download a fresh copy of the P2A full version and/or update and install it. 
3. English-US Language installed and set as Primary Language, English Speech Recognition installed also.
4. Working Microphone installed and set as Default Audio Input device in Windows
5. Valid Call Sign – Try using the default call sign of Mfg: Beech; Tail Number: N431VB.  Press the Save button.
6. Try running the program in Administrator mode by right clicking on the Pilot2ATC.exe file and selecting “Run as Administrator”
7. 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
8. 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.
9. If still won't fully connect, try deleting the AppSettings.xml file.  You will lose your settings, but some users have reported that this fixed their connection issue.  The file is located at:

c:\users\<UserName>\AppData\Roaming\P2A_300\Settings\AppSettings.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.

10. If connecting to MSFS, one user reported that setting FSUIPC WASM to Enabled fixed it for them.

Edited September 13, 2025Sep 13 by Dave-Pilot2ATC

Thank you, Dave, for all this information, but I don't understand what you're telling me, because all of the points you're asking me have already been addressed in our previous discussion with you.

I get the impression that you think the problem is on our end, but I remind you that we tested version 2 of P2ATC and it works very well, and that only version 3 doesn't.

I sincerely think we should move on to the next step, which is to report the bug to the developers and obtain more relevant information in the logs.

I'm happy to participate in these tests if necessary with beta versions.

Unfortunately, we will remain on version 2 while waiting for an evolution and correction in version 3, but I hope this conversation doesn't end and that we can continue to progress together.

Sincerely,

It has to be something unique to your environment or settings because hundreds of users are running V3 with P3D, including me.  I have tried and cannot reproduce this issue with P3D, using any of the stock P3D aircraft.  

V2 working probably does rule out it being an FSUIPC or aircraft issue since both P2A version work with any version of FSUIPC.

From your descriptions and screenshots, you are partially connecting to the SIM, but not fully, which usually is caused by #s 3,4,5,8,or 9 in the list.  (Notice that I edited #9 as it previously reflected V2 AppConfig.xml file instead of V3 AppSettings.xml file)

If you could email your most recent log file after trying to connect and change frequencies to [email protected], I will have a look to see if there are any indicators of where the problem is.

I am the developer, so hopefully we can figure this out.

Dave

Hi Dave,

Thanks for the feedback. 

We'll try the actions today. 

I'm glad we have more to test. 

Fingers crossed.

Sincerely, François