katoema

OK John, this time the new exe was able to install in the same folder. When I launched the sim, FSUIPC7 did not start. With MSFS running I manually launched FSUIPC7 and noted in the toolbar that it it was meant to auto start. Wide Server was enabled but the clients were not connected. I had two other PCs running in order to check the Wide Clients and both were not connected. I let MSFS and FSUIPC7 run and eventually after 1-2 minutes the Clients connected. I will try again later and if I have the same result with FSUIPC7 not automatically launching I will revert back to you again. Thanks Martin

Morning Pete, the grey cells are affecting my memory, but can you clarify if I should make a fresh FSUIPC7 folder, place the new exe in it and copy across files and folders that I have already - to have some continuity with with previous versions? Martin

The issue is that the exe dated 08/01/2021 is refusing to be deleted in order to place the latest exe in the folder. Thus it cannot launch. Martin

Thanks John, just noted I have v7.0.4 9th January 2021. Will update with your link. Martin NB: that link will not work as it says: This action can't be completed.

John, in the toolbar, options, it is ticked for auto-connect to FS and ticked to exit with FS. Loaded = launched Since you automated to launch/connect to MSFS last year I have not had any issues and I use FS several times a day - more so now as I am helping with the E135 Heli development. Yes, I have noted that the FSUIPC7 banner loads when you press to fly, but that is not doing it now. Now the WideFS is not enabling and not connecting to a client when I enable it manually. Martin

OK, I have now loaded MSFS and FSUPIC7 several times and it does not load automatically. Also I have to enable WideFS each time. Martin

Thanks, John. I'll monitor over the next few loads, perhaps I missed something. Martin

Update: I started FSUIPC.exe on its own, without starting MSFS. In looking at the toolbar along the top I noted WideFS was showing "enable"! Pressing it and restarting FSUIPC I now have a connection on a client PC. The issue must be in the enable/disable as indicated to John by what MS asked me to do. Therefore having enabled reversed that instruction may have remedied what was required. However, a physical change was necessary in the FSUIPC7 toolbar. Does that seem logical to you? Martin

Pete, I and my wife have scoured all the computers and WD backup devices for anything that resembles what we are looking for, with no success. It has also not been possible to find the WideServer.dll! The last working WideClient.log which provides details from the server - it is the server details that we cannot find. If you can provide a pointer as to where: folder, file name etc to look for, this may help. Martin

Pete, It is not a case of not wanting to do this, but I am having difficulty to find the information required. The PC that I am looking at is relatively new and when I moved everything to do with MSFS, including FSUIPC7, there are the folders where this information should be are just not located within them. When I have the information I will supply it. Thank you for your patience. Martin

John, everything had been working with no issues. It was only after following the different steps given by MS that I noted that WideFS was not working, once MSFS was restored. The computer was rebooted several times, in following MS's instructions. Of course everything was closed down overnight. Reading through the WideFS User Guide I note there are many items now with W10 v20H2 that I cannot see in the system info any IP addresses or workgroups, etc on the server PC.

Our network sees every PC, Laptop and other devices and can read and open documents from another computer, so this represents that the network configuration is working. The Server log is at the time it stopped yesterday. Martin WideClient.ini WideServer0.log

Sorry for delay, I attach the WideClient log, but as you see it is for today because of trying to connect. WideClient0.log

This is bizarre, the WideClient log for Sandpiper is dated 07/09/2020, yet since September 2020 I have used Wideclint on that PC several times per week!

WideClient0.log

Tried on Sandpiper as I use that to connect to PlanG. This computer I am writing from I will use when Sandpiper is not on - hence WideFS is not working on any. Only one client was on last night - Sandpiper. I have rest to normal, but still no connection Martin

Last night I found I could not get past "Welcome, Set Your Experience - Checking For Updates": loading does not go past this. In response I got this in an email from MS which was part of a longer procedure: "· netsh int tcp set global autotuninglevel=disable" I mention this because of the last log, attached as it mentions "TCP" I cannot now get Wiide Client to show on other computers. How can I get it back please? Martin WideServer.log

John, I use the cfbw, stable and dev models and have reverse thrust on all of them, with no issues. Martin

@John Dowson I placed the bat file D:\FSUIPC7\MSFSwithFSUIPC7.bat into the Custom FS start EXE: address box of the MSFSAddon Linker app and it started and launched MSFS and FSUIPC7 and the preset I selected. And, to boot, the MSFS Jump Starter to reduce loading time. One happy simmer here now and thank you for your direction. Martin

@John Dowson I have sent a PM to the author, as he set up my link, because I do not use the full intro for MSFS, as it misses this out and reduces the time it takes to launch MSFS. All MSFSAddon Linker undertakes is to create symbolic links from the Community folder to a folder called "MSFS Addons" and this is where all the "Community" items are held. You can then create presets which, in essence, will only launch what is in that preset. At present I select the preset, but use the MSFS/FSUIPC icon to undertake the launch and can only launch what the preset is tricking what is "in" the Community folder. You are correct that MSFS/FSUIPC7 should be able to be launched by MSFSAddon Linker (this is undertaken from being set up from the options box in the app). The author has to look at MSFS/FSUIPC7/FSJumpstarter to provide me with the correct solution. Martin

@John DowsonHello John. OK I can clarify that you can select whatever in MSFSAddon Linker, but if you start MSFS directly from the MSFSAddon Linker app, FSUIPC7 does not launch. However, if you select whatever in the MSFSAddon Linker that you want to run, you must launch from the new MSFS/FSUIPC7 desktop icon and everything will run as you have selected i.e., MSFS, FSUIPC7 and what you have selected in MSFSAddon Linker. It will be up to the author of MSFSAddon Linker to test how it can be used directly I will copy this response to him. Thanks Martin

Today, I noticed a new icon on my desktop for what I thought was just the starting of FSUIPC7. I was amazed that it started MSFS and FSUIPC7 together. I have the boxed Premium Deluxe version, which uses MS Store. Glad for one side that this works, but now I wonder how this will affect MSAddon Linker and the presets, as I usually launch MSFS via that app, so not to install everything in the Community folder! Martin When you start with MSFSAddon Linker, FSUIPC7 does not show that it is launched, BUT when you select Fly it shows up in the BRH corner in the "hide"box.

Hi, I have the same issue with the paid version. Thanks Martin After 2 reboots of computer and 2 restarts of MSFS. FSUIPC7 seems to be working correctly: I getting reverse thrusting. FSUIPC7.log FSUIPC7.ini

Have now purchased!👍 Thanks Martin

OK! Thanks.