These are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
[Solved] Simulator detected but not connecting
FSUIPC7, 7.5.6 with MSFS2020 installed via Steam. I selected the FSUIPC startup option of using exe.xml.
Started MSFS, and I see FSUIPC icon appear in taskbar. Open it up, see "Simulator detected" and wait for it to try to connect. I waited for a few minutes with no change, exited out of FSUIPC. Restarted FSUIPC (with MSFS still running, at the main menu). Left it for a few minutes and exited.
I've read the FAQ entry on adjusting the .ini file entries, but that seems to suppose that (1) FSUIPC is started by MSFS and (2) it eventually connects successfully. Attaching the 2 log files ("_prev" is the first run started via exe.xml)
If FSUIPC7 cannot obtain a connection, then this is usually due to another (badly behaved) add-on taking up all the available connections.
You can try two things:
1. Increase the number of available connections. To do this, increase all of the MaxClients entries in your SimConnect.xml file. This file will be under your AppData\Roaming\Microsoft Flight Simulator folder.
2. Move the FSUIPC7 entry in your EXE.xml file up so that it is the first launch item in this file.
Several add-ons were known to cause such issues, but I thought most of these would have been fixed by now. To determine what is taking all your connections, I would need to see an SimConnect.log file. If you want me to check this. see the following FAQ entry on how to generate a SimConnect log file: https://fsuipc.com/community/fsuipc-faq-other/
John
Thanks for the reply!
I only had 1 other addon in the exe.xml, for a Logitech/Saitek button box. I disabled it. Same behaviour from FSUIPC. I enabled Dev mode and I saw some entries in SimConnect inspector, attached.
I enabled logging, log file attached.
Why does that image show two copies of the FSUIPC WASM module?
Your log file shows only 3 simconnect connections in use:
> 4.11852 [320, 1]Open: Version=0x00000005 Name="SI FS2020 Bridge" > 4.12055 [321, 1]Open: Version=0x00000005 Name="FSUIPC.LVAR.WASM" > 4.12485 [322, 1]Open: Version=0x00000005 Name="MobiFlightWasmModule"
Your MaxClients parameter is set to 64, so that should be plenty.
Are you by any chance running MSFS with Admin privileges? If so, you need to set FSUIPC7 to also run with admin privileges.
If that is not the issue, I have no idea why FSUIPC7 cannot connect.
When you run MSFS, how long does it take for MSFS to arrive at the main menu?
Can you run MSFS, and when it starts FSUIPC7, exit FSUIPC7. Then when MSFS arrives at the main menu, manually start FSUIPC7. Can it connect? If not, exit FSUIPC7, and then run it again with Admin privileges - can it connect then?
The double-entry of FSUIPC in the screenshot is just because I clicked on the down arrow to show all entries; so, the second FSUIPC is the first in the entry list.
I don't think MSFS is running as Admin? I did the usual insall via Steam for it. Starting MSFS20 using a steam:// shortcut, it takes 54 seconds to get to the main menu. The FSUIPC splash screen appears at 38 seconds.
I closed FSUIPC and restarted it manually as Admin. Left it running for a minute to generate a couple of connection attempts. Same behaviour.
I'll attach the log file from the manual-as-Admin attempt.
Is it using sockets or named pipes? Could this be a firewall issue?