[P3Dv5 does not start WideServer (automatically), only after deactivating/reactivating]

Hello John (and anybody else),

I tried to use my little grey cells (like another Belgian used to say), but no reasonable explanation...

So I not only did a reinstall of P3Dv5 but of the entire computer (installed W11Pro from clean download on reformatted HD)...probably used a canon to kill a mosquito, but everything is now working like it should

Note: in the PSUIPC.log my Windows-version is still known as W8Pro Build 22621 and my system says W11Pro Build 22621.14 😉

Thanks for your time, I hope the weather is better than here in Brussels 💦

[P3Dv5 does not start WideServer (automatically), only after deactivating/reactivating]

OK, thanks John.

These kind of issues are the most awkward to solve...

It takes about 5 minutes to restart, so not a very big problem...but it remains strange.

Nevertheless, have a nice weekend

[P3Dv5 does not start WideServer (automatically), only after deactivating/reactivating]

10 minutes ago, Luke Kolin said:

Where does one download that version? It doesn't appear to be available on prepar3d.com.

Cheers

Luke

Thanks Luke, I was searching for a third pair of glasses... since I did not find the version John mentioned

 

@John: In the meanwhile, this is the logfile FSUIPC6.log.

Note1: I did not start the (SPAD.Next) WideFS-client, computer named FSVIEW, with the SimConnect connection (as a matter of fact I did, but I am programming Arduino-inputs on that one)

Note2: in the beginning of the log-file, FSUIPC claims to be on a Windows 8-computer, however it is a Windows 11 version I am running. 

[P3Dv5 does not start WideServer (automatically), only after deactivating/reactivating]

57 minutes ago, John Dowson said:

Ok, that makes sense then.

The problem is in FSUIPC not WideClient, so i don't need to see the WideClient files for the time being.

Can you add the following to the [General] section of your FSUIPC6.ini file please and show me the log generated with this:
    Debug=Please
    TestOptions=x800

Thanks John for spending time on this...

 

Made the change, result being FSUIPC6.log

No WideServer.log

[P3Dv5 does not start WideServer (automatically), only after deactivating/reactivating]

Yes, those files were when I enabled WideServer.

 

There is NO joystick connected (so no axes or buttons) to the FS-computer. So the scan CAN NOT give anything...

Already tried re-installing...grrr

All my additional hardware add-ons are connected through SPAD.Next using SimConnect (and works every time) on the computer -still- named FSVIEW (names will be changed in near future to reflect new setup-configuration with more meaningful names)

FSUIPC6.logFSUIPC6.iniWideClient.iniWideClient.log

Please note (as I said earlier), in this case, NO WideServer.log because WideWerver not running and not even started (I think so as I see on the Windows-header where normally I should see something like "Prepar3d with Wideserver: x clients connected" or "...waiting for clients to connect"  )

WideClient.log: this one comes from the FSVIEW-client to show SPAD has been detected (this log-file was NOT created while P3D was running, just to show exact same setup on other WideFS-client)

[P3Dv5 does not start WideServer (automatically), only after deactivating/reactivating]

Well, problem still there (even after putting FSUIPC6 in another directory).

If the issue/problem occurs, there is NO WideServer.log, and clients can not connect (logic because WideServer not started).

If WideServer starts (after I go through the procedure I explained), the log-file is very normal.WideServer.log.FSUIPC6.log I have included as well as this one FSUIPC6.ini.WideClient.iniand WideClient.logon the client side (note I shut down fs before client).

Thanks for your help John.

Regards,

Peter

 

[P3Dv5 does not start WideServer (automatically), only after deactivating/reactivating]

28 minutes ago, John Dowson said:

What has changed in this timeframe (or just before), if anything?

as it is my P3D-computer, I try not to touch it. If I have to install something, I do this on one of my non-fs computers

28 minutes ago, John Dowson said:

As you are using UDP on the server, you could try specifying this in the clients by adding
     Protocol=UDP
to the [Config] section of your WideClient.ini files.

tried all protocols, and I change on clients if I change on server

28 minutes ago, John Dowson said:

This is strange...I may look into this but we will see....

Ok, so it works when disabled and you enable. What happens on the next run - does it come back to the initial issue (WideClients not connecting, no 'Waiting for...' message in the FS window)?

yes, next run is exactly same problem all over again

28 minutes ago, John Dowson said:

Not finding a WideServer.log file is very strange...and it is difficult to diagnose issues without this file. The FSUIPC.log file does show that WideServer is started, but it is not clear from which test scenario this is from - and it is also not complete, i.e. FSUIPC seemed to be running when this was attached (no close).

Well, FSUIPC does create a log file (WideServer.log) when WideServer is working (i.e. when I restart P3D AND enable WideFS), but NOT when starting first time (i.e. when WideFS is supposed to start)

28 minutes ago, John Dowson said:

One thing that does strike me as slightly dodgy is your FSUIPC6 installation location - you have installed under the windows Documents folder. It is always better to choose a non-windows protected folder (e.g. C:\FSUIPC6 or C:\Prepar3D Add-ons\FSUIPC6) as windows seems to be changing access rights on windows-defined folders. So I suggest you first re-install FSUIPC6 into a different non-windows protected folder - you can skip registration and copy across your FSUIPC6.key and FSUIPC6.ini files, together with any other files you may use (e.g. *.lua, *.mcro, *.dll) from your old installation location to the new one. The Documents\Prepar3D v5 Add-ons\FSUIPC6\ folder should just be used for your add-on.xml file that allows the FSUIPC6.dll to be loaded when P3D is started.

John

Thank You John for this feedback. I never had my documents-folder protected, but as you say, one never knows what exactly windows is up to... I will have a try and give update.

 

Thanks,

Regards,

Peter

[P3Dv5 does not start WideServer (automatically), only after deactivating/reactivating]

Hello, and a good day to you. I have an awkward problem with P3Dv5 and FSUIPC6, and more specifically the WideServer part of it (note FSUIPC and WiedeServer are registered).

I have 3 WideClient-computers, connecting happily to a server with P3Dv3, and -under normal circumstances- with P3Dv5. Since a few days the WideClient-computers do not connect to FSUIPC v6.1.9 (or the WideServer). The log-file of these clients say they are waiting for a connectionWideClient.log. If I go and look to the "Add-ons"-tab while running P3Dv5 I see the FSUIPC-line and when selecting this all the usual tabs are present, and the window says that FSUIPC and Wideserver are registered, with an option to "Disable WideFS" (which presumes WideFS is running). The FSUIPC6.ini-file FSUIPC6.iniunder the heading [WideServer] seems to indicate the same thing "WideFSenabled=Yes". But WideServer is not active (in the Windows-label I used to see "...Wideserver with X clients connected" or "...WideServer is waiting for clients". This is not the case.

I then choose to "Disable WideFS" in the FSUIPC-options screen, and choose "OK". The FSUIPC-options screen disappears, and a message "Saving or reloading FSUIPC settings. Please wait...". After some hours of waiting, the message is still there.

I then force P3Dv5 to stop (via Windows and not via P3Dv5, which does not give me the hand to make a choice). I then see in the FSUIPC6.ini-file that the line "WideFSenabled=Yes" has been changed to "...=No". I restart P3Dv5 again, only this time when looking in the FSUIPC-parameters from within P3Dv5, I can choose to "Enable WideFS" (logic because of the change in the FSUIPC6.ini-file), which I do, and after a few seconds, all the WideClient-computers connect (no restarting of P3Dv5 necessary)...

I do not find a WideServer.log-file, only a FSUIPC6.log-file FSUIPC6.log.

Any ideas as to what may cause this problem ?

Thank you very much for your help.

Regards, Peter

FSUIPC6.ini WideClient.log