WideFs not connecting

[eziocin]

Hi,

after many years of successful use of WideFs and FSUIPC, all of a sudden, in the last few weeks I am not able to connect Widefs unless I restart FSUIPC. 

This is what happens: I launch MSFS2020 and at some point FSUIPC also starts. Then once I have loaded the flight and the aircraft is at the departure gate, I run Widefs Client on the networked laptop, but it hangs with the message "Waiting for a connection". In order to establish the connection I need to shut down and restart FSUIPC (no need to restart MSFS as well) , and then I can connect Widefs without any issue.

I don't know if this is part of the same problem, but I have Spad.next and vPilot launched automatically by FSUIPC, and although they both start and load correctly they shut down as soon as I load the flight. The only reason I am mentioning this is because this issue has come out concurrently with the WideFs issue...never had problems like these in many years of flawless use of FSUIPC, Spad and vPilot.  

Running MSFS on Win11, latest build, and FSUIPC latest version

Any indication on how to solve this issue would be greatly appreciated.

Thanks a lot in advance

 

Ezio

[John Dowson]

1 hour ago, eziocin said:

I run Widefs Client on the networked laptop, but it hangs with the message "Waiting for a connection".

It is not actually hanging is it, its just waiting for a connection, no? Does it connect automatically when you restart FSUIPC, or do you have to also restart the WideClient?

Can you please show me / attach your FSUIPC7.log and WideServer.log files, both from when it initially fails to connect (and after you have exited FSUIPC7) and also from after when you restart it and it connects.

[eziocin]

Thanks John for the quick answer. Yes, your point is correct..it doesn't hang..it is waiting for a connection...I usually shut down Wideclient before restarting FSUIPC and then restart WideClient after I restart FSUIPC, but I will check if leaving it running it reconnects automatically. I will send you the log files as soon as I am back home.. that is Sunday late evening ... 🙂

have a nice week end

 

Ezio

[CXA007]

Interestingly enough after years of no problems, tonight the exact same thing is happening to me, 

I was on a fairly old version of FSUIPC/WideFS so I upgraded to the newest version and still no connection. 

Its happening on both my remote computers. So it must be an issue on the main FSUIPC computer. Tried removing it from Windows Firewall, and next start it prompted to add it back which I did for both Public and Private networks. Still Nothing. 

Here is what the WideClient log file shows

 

********* WideClient Log [version 7.16] Class=FS98MAIN *********
Date (dmy): 28/02/25, Time 20:07:32.153: Client name is THINKCENTRE
      204 LUA: "C:\WideFS7\Initial.LUA": not found
      219 Attempting to connect now
      219 Trying to locate server: Need details from Server Broadcast
      219 Failed to connect: waiting to try again
     1250 Attempting to connect now
    22719 Trying to locate server: Need details from Server Broadcast

   156672 ****** End of session performance summary ******
   156672 Total time connected = 0 seconds
   156672 Reception maximum:  0 frames/sec, 0 bytes/sec
   156672 Transmission maximum:  0 frames/sec, 0 bytes/sec
   156672 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

   156672 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

 

[CXA007]

deleted as not relevant..

 

Edited March 1 by CXA007

[John Dowson]

This issue is continually getting reported, and my answer is always the same. Please see one of the other many posts on exactly the same issue:

...etc

Basically read the documentation and follow the advise there, and also check out the many posts on exactly the same issue.

 

[CXA007]

Thanks John, 

I did actually go looking last night as my time zone is behind you and the original poster, and I knew it would be morning before I got an feedback. 

I discovered, Windows forced the 24H2 update on me yesterday which most like started this. So I found the topics around that and still could not make things work. 

After some head scratching I went back to using the FSUIPC Batch file to start MSFS. Doing that WideServer would show a connection, however on the secondary PC. Windows was reporting WideFS had stopped working and gave me the wait for force stop window. Several system cold reboots and still same issue. So I gave up and went to bed.. 

This morning everything worked fine first try 🤷‍♂️... Possibly the 24H2 update hadn't finished installing well I was trying to correct the issue..      

Edited March 1 by CXA007

[John Dowson]

52 minutes ago, CXA007 said:

This morning everything worked fine first try 🤷‍♂️... Possibly the 24H2 update hadn't finished installing well I was trying to correct the issue..      

👍

[eziocin]

On 2/28/2025 at 12:53 PM, John Dowson said:

It is not actually hanging is it, its just waiting for a connection, no? Does it connect automatically when you restart FSUIPC, or do you have to also restart the WideClient?

Can you please show me / attach your FSUIPC7.log and WideServer.log files, both from when it initially fails to connect (and after you have exited FSUIPC7) and also from after when you restart it and it connects.

Hi John,

as promised here I am with the FSUIPC and WideClient Log files.

You will find attached three files:

FSUIPC7@3Mar_Start1.log      this is the log following the initial FSUIPC start with MSFS which in turn started also vPilot and Spad.next

FSUIPC7@3Mar_Restart.log     this is the log relevant to the manual restart of FSUIPC after I shut it down keeping MSFS2020 running (before I shut FSUIPC down Spad.next had shut down without any action on my side, and vPilot was still working)

Wideclient.log         this the log relevant to WideClient on the networked laptop. Note that I did not shut it down when I restarted FSUIPC, and upon the FSUIPC restart the connection was immediately found.

I am running the 24H2 Win11 build but this issue had started before 24H2 was released and installed on my PC

 

Thanks for your help

Ciao

Ezio

 

WideClient.log

FSUIPC7@3Mar_Start1.log FSUIPC7@3Mar_restart.log

[John Dowson]

Note that I also need to see the WideServer.log files for issues with WideFS...

However, it should be obvious why it didn't connect the first time you ran FSUIPC7 if you look at your log file:

Quote

...
      453 Auto-started via EXE.xml with DetectToConnectDelayAuto=30, InitialStallTime=15
     3297 Simulator detected
     3297 Run: "C:\Users\xxxx\AppData\Local\vPilot\vPilot.exe -host"
     3438 Run: "C:\Program Files\SPAD.neXt\SPAD.neXt.exe"
    33891 Trying to connect...
    48891 **** SimConnect open event not received in required time limit: Re-connecting now...
    49109 Trying to connect...
    64109 **** SimConnect open event not received in required time limit: Re-connecting now...
    64328 Trying to connect...
    85219 Failed on SimConnect_Open for AI Traffic Client, return = 0x80004005
   324250 === Hot key unregistered
...

FSUIPC7 never connected to MSFS and the WideServer was never started. Note that, by default, WideServer is not started until FSUIPC7 is connected and you have an aircraft loaded and ready-to-fly.

The first thing you need to do is to delay the start of SPAD,next and vPilot until at lease FSUIPC is connected top the FS (i.e. add the CONNECTED keyword). vPilot could be started even later, using the READY keyword.

Once that is corrected, try again and take a look at your log file. If you see the following message:
       48891 **** SimConnect open event not received in required time limit: Re-connecting now...
then you should adjust the DetectToConnectDelayAuto ini parameter. Please see the section Auto-tuning of initial start-up ini parameters in the Advanced User guide, or the following FAQ entry: 

John

 

[eziocin]

John,

thank you. I modified the FSUIPC.ini file to add the CONNECTED (Spad.next) and READY (Vpilot) on the RUN instructions,  and to adjust the DetectToConnectDelayAuto as per the link you provided (the value now set for me is 86). Now everything is working well.

Thanks a lot for your help   

Ezio