MSFS updated, FSUIPC can not connect to Simconnect

[RacsLee]

*** Moved from main support forum to FSUIPC7 support sub-forum ***

Hello Everybody,

today morning I got an update for MSFS, and it seems, FSUIPC can not connect to SimConnect. Reinstalled FUSIPC, but nothing changed.

Added my log, do you have any idea?

Thank you very much

 

FSUIPC7.logFetching info...

Edited Friday at 07:49 AM by John Dowson
Moved to FSUIPC7 support forum

[John Dowson]

First, please use the FSUIPC7 sub-forum for all issues/questions on FSUIPC7, not the main forum. I have moved your post.

  On 6/13/2025 at 4:14 AM, RacsLee said:

today morning I got an update for MSFS, and it seems, FSUIPC can not connect to SimConnect. Reinstalled FUSIPC, but nothing changed.

Expand  

Which version of MSFS - 2020 or 2024? Or do you get this issue with both?
I have checked with both versions here and do not see any issues, so it is something specific to your system.

If FSUIPC cannot connect to MSFS, this is usually because there are no SimConnect connections available. This can only happen if something else has taken / used all the available connections. Are you running any other 3rd-party/simconnect applications? Do you have the Fenix aircraft installed?

The first thing to do is to reboot and try again. If you get the same issue check your EXE.xml (location is in the InstallFSUIPC7.log if you do not know where this is) and see if any other applications are being started. If so, try re-ordering them so FSUIPC7 is started first.

If this is due to another simconnect application using up all available connections, then you need to determine what application this is. To do this, you can enable SimConnect logging - see the following article on how to do this: 

 

The log file will show each connection, and should tell you if one or more of your clients is behaving badly and taking up all the connections - there are several known clients that have done this over the years (e.g. Fenix bootstrapper).

If you have not done so already, it is also a good idea to increase the number of SimConnect clients allowed, by setting the MaxClients parameter to 128 (default is 64) in your SimConnect.xml file (whose location is the same as for the SimConnect.ini file described in that post I referenced above).

John

 

 

[RacsLee]

Hello John,

Thank you for your help, I'm using MSFS 2020 with Fenix, will try your tips and write the result.

[John Dowson]

  On 6/13/2025 at 11:03 AM, RacsLee said:

I'm using MSFS 2020 with Fenix, will try your tips and write the result.

Expand  

Ok, thanks, If using the Fenix, it could be the FenixBootsrapper - issues with simconnect connections when using this aircraft have been reported before - see 

If there is anything in your EXE.xml for the fenix, try moving that to after the FSUIPC7 entry, although I doubt this will help as FSUIPC does not try to get a connection until .the DetectToConnectDelayAuto has passed, which is set to 60 seconds. If there is an entry for the FenixBootstrapper in the EXE.xml, you could try setting the Disabled property to True (temporarily) to see if that helps.
You could also try removing the Fenix from your WASM folder (temporarily) to see if that fixes the issue.
But its the SimConnect.log file that will tell you which add-on is misbehaving.

John

[RacsLee]

Thank you, I moved FSUIPC to starting first, and changed the MaxClients to 128. Now Everything is working well.