Hi Dave, since a few days, I am getting an error that the sim connection failed to open. It further says that it cannot find FSUIPC running on this machine eventhough it is installed (actually I am running version 7.216). I tried to run P2A (Beta m) with the latest FSUIPC version 7.31 but things did not solve. I never had this before. Do you have any idea how to solve this. Thank you.

Regards Roland

 

 

I suspect that FSUIPC is either not installed correctly or is not being started automatically.  Depending on how you install it, you may have to start it manually.

I would reinstall and be sure it is set to start when you start MSFS.

On 3/10/2022 at 5:37 AM, Truij said:

ince a few days, I am getting an error that the sim connection failed to open. It further says that it cannot find FSUIPC running

I've encountered this error as well. Used to work fine, but a few weeks ago, P2A stopped recognizing FSUIPC as running, even when I could confirm it was indeed running. FSUIPC starts with the sim automatically, and I can see it running in my system tray. But P2A tells me it isn't running. 

My solution to this is simple. While in MSFS, hit ALT+F to bring up FSUIPC. In FSUIPC, I hit File > Exit to close it. Then I reopen it, and P2A finds it without issue. 

Thank you for your answers. As I start MSFS with the FSUIPC desktop shortcut, I assume that FSUIPC is installed correctly. I did a reinstall of version 7.3.1. and have the same problem. See attached the answer from Jon Dowson: FSUIPC Exception - FSUIPC7 MSFS - The simFlight Network Forums

 

 

 

 

 

Hi, I am on a flight from LEBL to LSZH and have been disconnected already 2 times from P2A shortly before overflying LFMN. I can reopen FSUIPC and continue with P2A calling the controller and I am guided again. But this is not as it should be.

Pilot2ATC accesses FSUIPC every second or so.  If it finds FSUIPC is not running, then it throws that error.

If FSUIPC is running, P2A will not throw that error.

It's possible that FSUIPC is being knocked out by MSFS or a lack of memory or some other resource.

Dave

On 3/12/2022 at 1:52 AM, Truij said:

As I start MSFS with the FSUIPC desktop shortcut, I assume that FSUIPC is installed correctly.

I do the same and can 100% confirm FSUIPC is loaded and working. However, P2A refuses to see it until I shut FSUIPC down and restart it manually. Not sure why that is exactly.

Unlike you though, it never disconnects on me. This only occurs upon initially connecting with P2A. Once I go through the process of reloading FSUIPC, I have no further issues. I suspect you have something else going on.

I am doing it a different way from you guys by the looks of it.

I launch MSFS directly (without the FSUIPC shortcut) and in turn, halfway through MSFS loading it launches FSUIPC. No issues with connections.

23 hours ago, skypilotYTS said:

launch MSFS directly (without the FSUIPC shortcut) and in turn, halfway through MSFS loading it launches FSUIPC. No issues with connections.

That's exactly what I do. FSUIPC hooks itself into the sim's exe.xml file and starts with MSFS - partway through the MSFS loading. 

This used to work just fine for me initially but then just stopped, and now I have to use the workaround I described above to get P2A to recognize it. 

Had the same problem. You should check first the InstallFSUIPC7.log (located where you installed FSUIPC. Maybe you'll find an error related to the EXE.xml file (like I do). Checked the EXE.xml. Mine was coruppted (maybe after installing VDGS (from noolearo)). Deleting the EXE.xml and reinstalled FSUIPC and reinstalled the VDGS Addon (Mandatory for iniBuild EGLL and some freeware Airports with VDGS) fixed it. FSUIPC now starts during startup of MSFS like before.

Thank you for this information. Indeed I installed the VDGS addon with the NZAA scenery (Flightbeam Studios) and my internet security software blocked the installation of said adddon. I will check this the next time when I update FSUIPC. The good news is that I have had no disconnections anymore since I updated to public beta 2n of P2A and reinstalled FSUIPC version 7.3.1. If it will happen again, I will try the suggested check of the EXE.xml. Thanks to all of you for your contributions.