FSUIPC7 and Gamesir controller

[LukaszMusiol]

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

[John Dowson]

14 hours ago, LukaszMusiol said:

however after 10 minutes of not using the controller, it goes off and disappears from Windows devices.

This sounds like windows is putting the device to sleep. To prevent this, you need to uncheck the 'Allow the computer to turn off this device to save power' in the Power Management settings of your USB Hubs in the' Device Manager. Windows also has a habit or resetting these settings.

[LukaszMusiol]

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.

[John Dowson]

If FSUIPC7 doesn't see the device again, then its not getting any notification from windows. Not sure if there is much I can do about this, and I am not going to add anything automatic to do this other than what it does at the moment, which is re-scan when windows informs it of a new device being connected or re-connected.

I could add an additional FSUIPC control that, when activated, will re-scan for devices. You could then assign this new control to a keypress when the Tarantula loses connection. Would this be ok?

By the way, you posted in the main support forum. For any/all issues with FSUIPC7, can you please use the specific FSUIPC7 support sub-forum. I will move this post.

John

[LukaszMusiol]

Hi.

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

Luk

Edited December 9 by LukaszMusiol

[John Dowson]

@LukaszMusiol Please try the attached version, 7.5.1a (beta). In this version I have added an additional control "Rescan Connected Controllers" (1157).

John

FSUIPC7.exe

[LukaszMusiol]

It's working perfect. Thank You very much

[John Dowson]

👍😎

[LukaszMusiol]

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

[John Dowson]

Could you please set a custom log value (Log->Custom) of x200000, also set logging for Buttons & Keys, and show me your log file and JoyScan.csv file the next time you get this issue.
Also, please check your key assignment for this, and make sure you have checked No repeats!. It could be repeating which is causing issues updating the files...

John

[LukaszMusiol]

 This time it was quick
  

FSUIPC7.JoyScan.csv FSUIPC7_prev.log

[John Dowson]

12 minutes ago, LukaszMusiol said:

 This time it was quick

What was quick?
The log file you attached shows no errors and that FSUIPC exited normally as MSFS had exited.
Please provide more information when you post - what did you do and what happened?

Also check your GameSir-Dongle is in a correct port - if its USB2, male sure its in a USB2 port and if its USB-3 make sure its in a USB3 port.

 

[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.

[John Dowson]

19 hours ago, LukaszMusiol said:

What I meant was that the error appeared quickly, because it usually appears every 2-3 flights.

But the message before this was that you were getting a CTD with FSUIPC7, The log file you attached was NOT from a CTD.
And if the error was that the controllers weren't recognised, I don't see a key-press assignment triggering a recan.
Did you do that? You log shows some keys being pressed, but nothing that triggers a rescan, and the sim was shutdown after 83 seconds:

Quote

    71531 KEYDOWN: VK=18, Waiting=0, Repeat=N, lParam=540540929 (0x20380001), Shifts=4
    71531 .. KeyDown received from FS but not programmed 
    71593 KEYDOWN: VK=13, Waiting=0, Repeat=N, lParam=538705921 (0x201C0001), Shifts=4
    71593 .. KeyDown received from FS but not programmed 
    71687 KEYUP: VK=13, Waiting=0, Shifts=4, lparam=3759931393 (0xE01C0001)
    71687 .. KeyUp received from FS but not programmed
    71797 KEYUP: VK=18, Waiting=0, Shifts=0, lparam=3224895489 (0xC0380001)
    71797 .. KeyUp received from FS but not programmed
    83343 MSFS no longer running - exiting

And it looks like your device was not detected by FSUIPC7 when it was initially started:

Quote

      250 ---------------------- Joystick Device Scan -----------------------
      250 -------------------------------------------------------------------
      250 -------------------------------------------------------------------
      250 ---------- Making INI JoyNames Section ----------
      250     JoyID Used= INI 0000, REG 0000
      250 -------------------------------------------------
      250   Checking and assigning Joy Letters as needed
      250    Rewriting this entry without the "MISSING" annotation
      250 Controller (GameSir-Dongle)
 

There are also various messages like this:

Quote

    31343 ***** A device has been attached!
    31422 ***** A device has been attached!
    31437 ***** A device has been attached!
    31437 ***** A device has been attached!
    31437 ***** A device has been attached!

so it looks like the device is continually connecting for some reason.
Check for any driver updates for this device. It is not a standard windows HID-joystick type device, and it looks like the connection between the device and the wifi dongle isn't very stable...

Can you please give details and what happened and what you did the next time you attach any files. May be worth doing this with the logging console window open as well (Log -> Open Console...) so that you can see the messages logged in real-time.