MSFS WideClient CloseReady not working

[bcars]

Using MSFS2020 (Steam MSFS version = 11.0.282174.99) and Fsuipc7(Version 7.5.4) on primary pc,,   WideClient (version 7.16) on 2nd pc

I have setup the main fsuipc [wideserver] with AutoShutdown=Yes  ( or Apps)  and the wideclient with autoshutdown=yes  ( or app, or appOnly)

On both fsuipc and wideclient I have setup to run a program when MSFS is ready:

[Programs]
RunIf1=READY,HIDE,CLOSE,D:\Prosim737-V3\RunProsim.exe
wideclient.ini
[User]
....
RunReady1=D:\Prosim737-V3\RunProsim.exe
CloseReady1=Yes        ( or Yes, D:\Prosim737-V3\RunProsim.exe

On the fsuipc7/msfs PC everything works fine. The program gets started at the appropriate time ( msfs ready) and closes when MSFS is shutdown
On the wideclient PC the program gets start at appropriate time, however it never gets closed.
Running wideclient with debug I can when wideclient gets the shutdown signal from the wideserver, however it doesn't do anything with it.
It doesn't close the started program nor does it close the wideclient window. 
I have to manually close the wideclient window(, then it closes the launched RunReady program.

(WideClient log excerpt....
797 e:\apps\visualstudioprojects\fsuipcwpfautoprosimmonitor <M1:L0:C1:H310>
797 E:\Apps\VisualStudioProjects\FSUIPCWPFAutoProsimMonitor\runprosim.exe <M1:L0:C1:H310>
....
 91625 Received shutdown offset code = DCBA <M1:L1:C1:H311>
 91625 FS closing down (param=DCBA), disconnecting <M1:L1:C1:H311>
 91625 ********* Interim performance summary ********* <M1:L1:C1:H311>
 91625 Total time connected so far = 76 seconds <M1:L1:C1:H311>

The wideclient window now shows not connected ( trying to reconnect) and continues in that mode until I close the wideclient window.

I must have some sort of configuration mismatch or setting that is not correct, but have tried several combinations. Even tried using a CloseAppsHotKey

Logs and ini settings attached.

 

WideFS-NoShutdown.zip

[John Dowson]

Can you check what the actual process name of the prosim process on your client PC is called (using TaskManager) - runprosim.exe may start an exe with a different name. If that is the case, you need to put the actual process name in the CloseReady1 entry, e.g.

CloseReady1=Yes,"<processName>.exe"

From the technical guide:

Quote

Another option, which may be needed with applications which start off as one process (the named EXE in the "Run" line), but then create another process (i.e. run another EXE) of which, of course, WideClient is then unaware. If it is that new process which needs closing, WideClient needs to be told its name. You do this by adding the EXE name (or the whole pathname if there's likely to be any ambiguity), to the Close parameter, after the "Yes", "Kill" or "Last" part.

Also, please try using the Last and Kill keywords (instead off Yes).

John

N.B. Note I am an holiday now and away from my flight PCs so cannot look into this in more detail at the moment (and I don't use or have prosim!).

[bcars]

Hi John

It is a single process. A program i wrote.

It launches a batch job( cmc /c) to startup prosim. When it closes, it launches a 2nd batch job. Pretty simple,

Has config that has the name of a program or cmd to launch at startup, and one to run when it closes. As I said, the same process runs fine on fsuipc7 on  sim computer.

You could substitute Notepad as the program for wideclient. I'll try kill or last

[John Dowson]

3 hours ago, bcars said:

It launches a batch job( cmc /c) to startup prosim. When it closes, it launches a 2nd batch job. Pretty simple,

Has config that has the name of a program or cmd to launch at startup, and one to run when it closes. As I said, the same process runs fine on fsuipc7 on  sim computer.

It may be an issue if its starting other programs, but if its working in FSUIPC it should really work in WideClient. Is it the same program, starting the same  programs as on FSUIPC? If not, you could try that as a test, to make sure.

3 hours ago, bcars said:

You could substitute Notepad as the program for wideclient.

I;m pretty sure that would work - WideClient hasn't changed for many years and this would have been reported earlier (many time!) if this wasn't working. But I will double check this, but, as I said, I cannot do anything now until I am back from mu holidays, in September.

3 hours ago, bcars said:

I'll try kill or last

Ok - let me know how that goes. However, if you use kill, I don't see how your program could run the the 2nd batch job on closing....

Why don't you use FSUIPC / WideClient to start the ProSim modules? Or are you doing it this way to run the 2nd batch script on close?

John