LukaszMusiol

What I meant was that the error appeared quickly, because it usually appears every 2-3 flights. Description of problem: After the pad came out of sleep (around the time of descent, because I'm slowly getting ready to land) I used it normally without any problems. As soon as I approached the landing I used the button to Rescan Connected Controllers (I use one of the axes for brakes because I don't have pedals. This is how it looks in .ini files [Axes] PollInterval=10 RangeRepeatRate=10 0=AV,256,F,66387,66388,0,0 -{ TO SIM: AXIS_LEFT_BRAKE_SET, AXIS_RIGHT_BRAKE_SET }- ) and FSUIPC close itself. I'll try to test it a bit more and see if the situation repeats itself in the next flights.

This time it was quick FSUIPC7.JoyScan.csv FSUIPC7_prev.log

Hello I have a small problem with FSUIPC and version 7.5.1a When pressing the key responsible for "Rescan Connected Controllers", sometimes FSUPIC just close itself. I am attaching the log and the description of the error from the system management. <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2024-12-16T09:11:53.9258458Z" /> <EventRecordID>60232</EventRecordID> <Correlation /> <Execution ProcessID="17352" ThreadID="4032" /> <Channel>Application</Channel> <Computer>DESKTOP-51KL16M</Computer> <Security UserID="S-1-5-21-1665299327-551092579-4021449343-1001" /> </System> - <EventData> <Data Name="AppName">FSUIPC7.exe</Data> <Data Name="AppVersion">7.5.0.1</Data> <Data Name="AppTimeStamp">6756b1ef</Data> <Data Name="ModuleName">ntdll.dll</Data> <Data Name="ModuleVersion">10.0.22621.4541</Data> <Data Name="ModuleTimeStamp">e7035eba</Data> <Data Name="ExceptionCode">c0000005</Data> <Data Name="FaultingOffset">000000000009fcf3</Data> <Data Name="ProcessId">0x2ec0</Data> <Data Name="ProcessCreationTime">0x1db4f8e0badb27a</Data> <Data Name="AppPath">D:\Gry\FSUIPC\FSUIPC7.exe</Data> <Data Name="ModulePath">C:\windows\SYSTEM32\ntdll.dll</Data> <Data Name="IntegratorReportId">f34d036e-f7f7-4e4c-8e3a-f177a5b10315</Data> <Data Name="PackageFullName" /> <Data Name="PackageRelativeAppId" /> </EventData> </Event> FSUIPC7_prev.log

It's working perfect. Thank You very much

Hi. Yes. That would be great. Thank You very much. Luk

Hello. I tried your suggestion, but unfortunately it didn't help. I tried my previous controller again and there were no problems with it - even after putting it to sleep it didn't disappear from the list of connected devices and both MSFS2024 and FSUIP7C saw it without a problem after turning it on again. With the new controller I noticed that when it turns off the wi-fi dongle works all the time and blinks trying to establish a connection, but after waking up the pad the control works fully in MSFS2024 but FSUIPC7 doesn't see it again. For now I found a partial solution to the problem. I connected the new controller with a cable - that solved the problem.

Hello I bought a new controller Gamesir Tarantula Pro, but unfortunately I have a problem activating it in FSUIPC in MSFS 2024 when he goes offline. After starting the game everything works fine, however after 10 minutes of not using the controller, it goes off and disappears from Windows devices. After turning it on, it automatically appears in the device manager, but it is not detected automatically by FSUIPC and I have to manually activate it by going to settings, e.g. axis and clicking ok. Is it possible to add some option that would rescan the devices and automatically make them visible again in FSUIPC? I had no problems with the previous controller because even though it turned off after some time it was still visible in the device manager. I will be grateful for your help