FSUIPC closing but not closed?

[VirtualUnitedPilot]

I will be flying the Fenix a230 and every with cut out, go to check FSUIPC and it is running butt when i try to use a switch i have bound to a preset FSUIPC does not show any sort of button or anuting like it soft crashed but its still running because the Acars that i use is still connected and working FSUIPC seems to be stuck? then i manully close and open FSUIPC and it works again

FSUIPC7_prev.log ts.txt FSUIPC_WASM.log ts.txt

[John Dowson]

1 hour ago, VirtualUnitedPilot said:

i try to use a switch i have bound to a preset FSUIPC does not show any sort of button or anuting like it soft crashed but its still running because the Acars that i use is still connected and working FSUIPC seems to be stuck?

Both log files look ok and show that FSUIPC7 was running and had not crashed. When this occurs, can you operate in the FSUIPC7 main window? i.e. does Alt+F open the main window, and can you then open the assignments windows and use those? If so, can you see the assignments you have bound to the switch? Is the switch/button recognised?
The WASM log looks ok, and shows that that didn't crash. 

You do have a few reconnection attempts at start-up, although this is nothing to do with the issue you are having, To prevent these, can you please set/update to the following in your FSUIPC7.ini (in the [General] section):
    DetectToConnectDelayAuto=90
    InitialStallTime=45
    StartUpTuningDoneVersion=-1

For your issue, can you please activate logging for Buttons & Keys, Events, Extras and WAPI Debug level logging, and the next time this occurs first open FSUIPC7 and the assignments window and press the button (presumably not recognised?), then exit FSUIPC7 and send me/attach your FSUIPC7.log and FSUIPC7.ini files. Then restart FSUIPC7 and try again. Does it now work? Presume so (from what you said), but if not, please then exit MSFS and show me / attach your FSUIPC_WASM.log file.

Also please check the power settings on your USB devices and hubs, and make sure Allow the computer to turn off this device to save power (under Power Management) is disabled. Windows has a habit of resetting this setting for some reason... - 

John

Edited December 2 by John Dowson
Further info added

[VirtualUnitedPilot]

When it does happen I can open Fsuipc and go to assignments but it does not pull up the switch number or it's assignment I will screen shot it next time as well 

[John Dowson]

14 minutes ago, VirtualUnitedPilot said:

When it does happen I can open Fsuipc and go to assignments but it does not pull up the switch number or it's assignment I will screen shot it next time as well 

No need for a screenshot. This sounds like your device has gone to sleep (as the button press is not recognised) - check the USB hub properties in device manager. Otherwise, please show me those files with the logging activated.

[VirtualUnitedPilot]

I did just check and the allow the computer to turn off this device was turned on so hopefully that fixes it if not I'll send you the logs 

[VirtualUnitedPilot]

@Pete Dowson so it happened again FSUIPC is on the latest 7.5 also just realized i didnt add the other log but i did notice that it just showed hot key unregistered it didnt show sim connect close done or anything 

here is an example
  " 783734 *** EVENT: Cntrl= 66068 (0x00010214), Param= 0 (0x00000000) SPOILERS_ARM_SET
   783734 *** EVENT: Cntrl= 65957 (0x000101a5), Param= 1 (0x00000001) FUEL_SELECTOR_LEFT
   783734 *** EVENT: Cntrl= 66519 (0x000103d7), Param= 1 (0x00000001) FUEL_SELECTOR_2_RIGHT
   791171 === Hot key unregistered
   791171 === Stop called ..."

FSUIPC_WASM_prev.log

[John Dowson]

21 hours ago, VirtualUnitedPilot said:

@Pete Dowson 

Please note that Pete retired over five years ago - no point in tagging him, especially for FSUIPC7 issues.

Why did you attach a WASM log file? that just shows that MSFS was running for only 6mins12 seconds,  you didn't even start a flight, and the WASM exited when you closed MSFS, as it should.

I am not sure what your issue is, if any - first you talk about button presses not being recognised, and the title of this topic is 'closing but not closed', whatever that means.  If FSUIPC is not exiting properly please show me / attach the FSUIPC7.log file from that session and explain what you did / how you closed or exited. There really is no point on posting log extracts.

John

[zfehr]

In prior versions of FSUIPC I could open the task manager and find the IPC*** file and manually close it when FSUIPC had shut down but wouldn't allow restarting saying it was still running. With this latest version I don't find that IPC*** file running in the task manager but still get can't restart FSUIPC. Maybe there is another task running that is causing this.

[John Dowson]

Just now, zfehr said:

In prior versions of FSUIPC I could open the task manager and find the IPC*** file and manually close it when FSUIPC had shut down but wouldn't allow restarting saying it was still running. With this latest version I don't find that IPC*** file running in the task manager but still get can't restart FSUIPC. Maybe there is another task running that is causing this.

FSUIPC should always exit cleanly really, and if not you should report and show me your log file. Please activate logging for Extras, and attach a your log file if it is not closing properly.
But if its not in the task manager, its not running....

FSUIPC creates a named mutex when started and removes this when exited. It could be that the mutex is not being destroyed for some reason, which will give you the message "There is a copy of FSUIPC7 already running. This process will now exit." if trying to start it again.

There is also no point in posting about any issues if you are not attaching the files so that I can investigate. I may require additional logging and more files, but it is always a good idea to attach at least your FSUIPC7.log file when you have a problem which at least gives me some basic information that I can use....

There is one known issue that can cause shutdown issues, which is when running lua files that have a com connection, but there are also known ways to handle this.

John

 

[zfehr]

17 hours ago, John Dowson said:

FSUIPC should always exit cleanly really, and if not you should report and show me your log file. Please activate logging for Extras, and attach a your log file if it is not closing properly.
But if its not in the task manager, its not running....

FSUIPC creates a named mutex when started and removes this when exited. It could be that the mutex is not being destroyed for some reason, which will give you the message "There is a copy of FSUIPC7 already running. This process will now exit." if trying to start it again.

There is also no point in posting about any issues if you are not attaching the files so that I can investigate. I may require additional logging and more files, but it is always a good idea to attach at least your FSUIPC7.log file when you have a problem which at least gives me some basic information that I can use....

There is one known issue that can cause shutdown issues, which is when running lua files that have a com connection, but there are also known ways to handle this.

John

 

Will do.

[VirtualUnitedPilot]

Okay so I found it's just my TCA throttle is "disconnecting" as my Winwing side stick button presses are still working, but for some reason my TCA Airbus throttle just stops working with Fsuipc even though the throttle levers still work as they are set in MSFS 

[John Dowson]

On 12/14/2024 at 5:10 PM, VirtualUnitedPilot said:

Okay so I found it's just my TCA throttle is "disconnecting" as my Winwing side stick button presses are still working, but for some reason my TCA Airbus throttle just stops working with Fsuipc even though the throttle levers still work as they are set in MSFS 

I don't understand why you are reporting issues and not showing me any files so that I can take a look.  Please at least attach your FSUIPC7.log file if you are getting any issues.
If a device stops working, can you please open FSUIPC and go to the axis assignment tab and see if the devices' axes are recognised there, and also check the button assignments tab to see if your buttons are recognised.
Also try restarting FSUIPC7 - is it then recognised?

Can you also check the USB hub settings (in windows device manager) and make sure 'Allow the computer to turn off this device to save power' is unchecked/disabled for all your USB hubs and devices.