sisoffi Posted May 13, 2020 Report Posted May 13, 2020 Hi, why in these two ini the programs that start automatically are not closed forcibly (use the kill function) by fsuipc? I also tried with close, but nothing to do, they start regularly but are not closed at the close of prepar (both v4 or v5) [Programs]Run1=READY,KILL,C:\OpusFSI_v6\P3DSERVER.EXERun2=READY,KILL,C:\Users\MD80_VISUAL\Documents\Mobiflight\MFConnector.exe thanks
Pete Dowson Posted May 13, 2020 Report Posted May 13, 2020 5 minutes ago, sisoffi said: why in these two ini the programs that start automatically are not closed forcibly (use the kill function) by fsuipc? I also tried with close, but nothing to do, they start regularly but are not closed at the close of prepar (both v4 or v5) [Programs]Run1=READY,KILL,C:\OpusFSI_v6\P3DSERVER.EXERun2=READY,KILL,C:\Users\MD80_VISUAL\Documents\Mobiflight\MFConnector.exe I don't know. FSUIPC merely tries to use the normal TerminateProcess call to kill the process it created for the program. If that returns an error it will be logged. Did you look in the log? If there's no error logged then FSUIPC has effectively been told that the TerminateProcess succeeded. Possibly those two programs don't react well to forced closure, possibly leaving threads running? Possibly the program actually running is a process created by the one which FSUIPC has started. If it has such an initialisation program then I'm afraid FSUIPC has no way of tracking that. Pete
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now