VirtualUnitedPilot

This can be closed it's a hardware/driver issue

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

@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

Thank you very much

FSUIPC7.iniThe inputs work for a moment then once i turn the plane on it just doesnt execute the inputs FSUIPC7.log FSUIPC7_prev.log FSUIPC_WASM.log FSUIPC_WASM_prev.log

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

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

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

But I never had an issue until this last update

FSUIPC closing due to VCRUNTIME140.dll is closing/ crashing due to the runtime dll Faulting application name: FSUIPC7.exe, version: 7.4.1.8, time stamp: 0x67249226 Faulting module name: VCRUNTIME140.dll, version: 14.40.33810.0, time stamp: 0x119a1ae6 Exception code: 0xc0000005 Fault offset: 0x00000000000111fb Faulting process id: 0x0x510 Faulting application start time: 0x0x1DB312B2A5F579D Faulting application path: C:\FSUIPC7\FSUIPC7.exe Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll Report Id: 753c71fb-7141-4ea8-8753-a784f94c8efc Faulting package full name: Faulting package-relative application ID: Fault bucket 1431409791881010632, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: FSUIPC7.exe P2: 7.4.1.8 P3: 67249226 P4: VCRUNTIME140.dll P5: 14.40.33810.0 P6: 119a1ae6 P7: c0000005 P8: 00000000000111fb P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b750c422-655d-4e5d-8b6b-499907239d3e.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6fd06e61-ec11-4728-8118-8c1d661694ae.tmp.WERInternalMetadata.xml WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20240808_1_EC_0_inject.etl \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f6d13544-23a2-4b48-9427-cea5b779a059.tmp.etl WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.28e648ae-b010-47cc-8de1-cb8fdd9855ff.tmp.etl \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.39f8cfe7-d209-4d49-ae8e-173d41cfe350.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.874972a4-ef54-4a6a-82f1-8aa26968eb77.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.db4cc2c2-a477-4a68-bd69-3921f9c8ef95.tmp.xml These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FSUIPC7.exe_17b5b4f92717d5a4b7691c71f1d85556b4ee46_83a1d1a4_14f67d2f-023c-43d2-aec9-d5d86fcd112e Analysis symbol: Rechecking for solution: 0 Report Id: 753c71fb-7141-4ea8-8753-a784f94c8efc Report Status: 268435456 Hashed bucket: 4d578bf522c87356f3dd639f2d155dc8