Sky Blue Flyer

I'm sure my scenario is pretty rare but an update as you suggest would make it fool proof. Thanks for taking the time to look at this John. best Martin

Yes I agree John it is strange because although the install log shows the correct steam location for the usercfg.opt, if you look at the fsuipc7.log whenever I ran fsuipc7 it was looking for the store usercfg.opt defined FS install location 47 System time = 25/02/2024 17:54:29 47 FLT UNC path = "\\MGS-SIMPC1\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\" 47 Allowing calibration when not assigned with 'Send direct to FSUIPC Calibration' 63 ------------------------------------------------------------------- 78 Preset file 'C:\FSUIPC7\myevents.txt' not found [info only] 78 13965 Calculator Code presets have been loaded and are available for use 110 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 125 FS UNC path = "E:\MSFS\Packages\" Once I realised there were some legacy Store version files inc the usercfg.opt from a previous installation pointing to the old package folder location. I pointed it to the new package folder location and everything was then fine. Obviously I couldnt leave it like that so I removed the Store legacy files, reinstalled fsuipc7 and it correctly identified the steam usercfg.opt and FS UNC path. FSUIPC7 did what it supposed to once the confusion of having a steam and a legacy store version of the usercfg.opt was rectified. kind regards Martin

Solved - I appear to have legacy msfs files in a microsoft store version of msfs even thogh I am now using a Steam version so I have two usercfg.opt files. FSUIPC7 was looking at the legacy usercfg.opt for the package location which was still pointing at the old location. After I updated the location in thus usercfg.opt file the WASM module was found. Not sure why fsuipc7 was looking here as everything plays nicely when I load the normal steam msfs. It all works now so am happy.

Hi John I am having trouble loading the WASM Module after moving my MSFS installation to a new M2 drive on my sim pc. I updated the Usercfg.opt with the new MSFS folder location and MSFS loads and runs normally except for no WASM Module. A quick look at the fsuipc7.log seems to show that the FS UNC Path is still showing the old MSFS installation folder path and not the new one. I have tried re-installing fsuipc7 (I'm on the latest version) but the FS UNC path is unchanged. How can I update this please? fsuipc7.ini, fsuipc7.log and installfsuipc7.log files attached. regards Martin FSUIPC7.ini FSUIPC7.log InstallFSUIPC7.log

Hi John Thank you for the revised beta .exe file. I have just tested it with success. I set all three [Program} entries in the .ini file with both the READY option and varying DELAY time options and all three worked perfectly, i.e. the programs started in DELAY time order after the FS main screen appears, a departure location selected, custom flight loads and 'Ready to Fly' is initiated. Thus can clearly be seen from the attached log file. For info, I did also test without the 'Ready' option. Each of the programs started with the respective 'Delay' options but before the FS initiated. Which is fine for most, but I require ProSim to start after FS starts. Thanks for your help with this John. Will your modified fsuipc7.exe be incorporated into the next release? FSUIPC7.ini FSUIPC7.log

Hi John I tried without the 'READY' option for 2 of the executables and inserted a 'DELAY' option, fsuipc7.ini file attached. The first executable with 'READY' and no 'DELAY' option started on FS start. The other 2 did not start either on FS start or 'Ready to Fly'. Log file attached as requested. FSUIPC7.ini FSUIPC7.log [Edit 1] A bit of further info after more testing John. It seems that any changes in the fsuipc7.ini (in the Programe section) require a pc reboot to become effective. I tried adding the changes without a reboot and it didn't work. After I rebooted I did get some success as follows. So, with the 'ready' option included, any delay time inc default does not work at all and the program starts on FS start. Without the 'ready' option and 'delay' included, the programme doesnt start on FS start but does start when 'ready to fly' is clicked after selecting departure. However not with the delay seconds, either as "=n" or default. Just to confirm, whenever I make a change to the [program] options in fsuipc7.ini I have to reboot the pc for the changes to be effective otherwise there is no change to behaviour.

Hi John I have installed the 7.3.25 beta exe and I am not getting any delay write back to fsuipc7.ini. However I am still unable to get the delay function to work. I have tried using "DELAY" which I believe has a default 10 secs. and also tried with the syntax in the advanced manual i.e."DELAY[=10]" Without success. I did try removing the parentheses but again no joy. If I remove the "DELAY" function completely the .exe start immediately so the 'run' syntax is correct. FSUIPC7_prev.log FSUIPC7.ini

Hi John Thanks for getting back to this and for the beta. I will give this a try this evening and report back. Regards Martin

That's great John, no rush. Thank you.

Just a bit of feedback John following more testing. I spoke too soon and I am still getting a "Delay=x" writeback to the fsuipc7.ini file after which the exe files do not then start as before. If I remove the 'Delay' function from each of the strings it works and there is no writeback and has continued to work perfectly during numerous startups. The problem by elimination appears to be the Delay function. I am happy to leave it out as the 3 prosim programs work fine when started simultaneously. regards Martin

I updated to latest supported version of fsuipc7 and changed the WideClient.ini to kill and everything worked as it should. I am yet to check if the fsuipc7.ini file was written back to but at least the programs were all started and closed. Thanks for your help on this one John

Thanks John. I'll update to the latest version of fsuipc7 first then try the changes you recommend to the Program section of the ini. I do always close fsuipc7 before making changes to the ini file. Strange that the extra line keeps being inserted. Similarly I'll try the WWideClient ini changes and report back. I will remove the ipc reads & writes from future logging. One final thought, I am starting msfs2020 from within addon linker rather than from within Steam or using the fsuipc msfs bat file. Would this make a difference?

Hi John Sorry for the late feedback. I have checked the fsuipc7.ini entries and amended the WideClient.ini with the suggested [User] entries checked against the WideFS Technical document. I now have had a chance to test the new configuration and am happy to report that the 3 programs in the [User] section are starting when the WideServer connection is made. There does however remain a problem with the fsuipc7.ini programs starting. The first in the [Program] list starts but not the second and third. Interestingly you will see from the attached fsuipc7.ini file that a delay line is always written to the [Program] entry despite being deleted each time I check the fsuipc7.ini file. Could this be linked to start problem that I am seeing? Also I am not seeing the 3 x WideClient started programs close when Wideserver disconnects. Am I missing something? Thanks in advance John for your time looking at this. FSUIPC7.ini FSUIPC7.log WideClient.ini WideClient.log WideServer.log

I see now, thanks John. I made the mistake of assuming that the same format for commands for the fsuipc.ini and wideclient.ini would apply. Once I used the correct syntax from the WideFS Technical document it worked perfectly. Lesson learnt. Thanks again

I cant seem to get programs to start on my client PC running WideFS7 using the Run or RunIf commands. I am doing the same thing on the main MSFS sim pc using the same syntax and it works fine. I am showing that WideClient connects on both the server and client when I spawn at gate and other software on the client pc requiring fsuipc is working correctly. I am trying to get various ProSim modules to start on both the msfs server and client pc's when msfs starts. I have attached logs Any help would be greatly appreciated. FSUIPC7.ini WideClient.ini FSUIPC7.log WideClient.log WideServer.log