Jump to content
The simFlight Network Forums

katoema

Members
  • Posts

    77
  • Joined

  • Last visited

Posts posted by katoema

  1. 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

  2. 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

     

     

  3. 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?

    21 hours ago, John Dowson said:

    netsh int tcp set global autotuninglevel=disable

    Martin

  4. 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

     

  5. 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

  6. 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.

  7. 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

  8. @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

  9. @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

  10. @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

  11. 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.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.