"Missing joystick"

[Kimchi]

With 7.5.4. i have assigned all buttons. After a restart my joystick does not work anymore and i see this message in the INI file: 

 

[JoyNames]
0=Sim Pedals
0.GUID={A8155120-4715-11F0-8004-444553540000}
1=TCA Q-Eng 1&2
1.GUID={72C59D80-4798-11F0-8007-444553540000}
2=
2.GUID={D0105350-4797-11F0-8006-444553540000}
3=usb pad
3.GUID={A81689A0-4715-11F0-8013-444553540000}
A=Sim Pedals
A.GUID={A8155120-4715-11F0-8004-444553540000}
B=TCA Q-Eng 1&2
B.GUID={72C59D80-4798-11F0-8007-444553540000}
C=Saitek Pro Flight X-56 Rhino Stick << MISSING JOYSTICK >>
C.GUID={D0105350-4797-11F0-8006-444553540000}
D=usb pad
D.GUID={A81689A0-4715-11F0-8013-444553540000}
E=
E.GUID={D0105350-4797-11F0-8006-444553540000}

I have deleted and re installed FSUIPC - deleted the old INI and started from scratch but whatever i do, the joystick fails to work unless i re assign all buttons during the flight. 

Can you help me Peter, Thanks in advance

 

[John Dowson]

Peter retire > 5 years ago now.

It looks like the name  has disappeared from the registry entry for your Saitek X-56 stick. Can you please attach your files - your ini, log and JoyScan.csv files and I will take a look.

John

[Kimchi]

Im so sorry John for calling you Peter. I appologize. 

I have de-installed the Logitech X56 software and re installed the software. I see the X56 in my devices and printers. Within FSUIPC im able to bind buttons to the joystick but the device name entry stays empty. 

Hopefully i have included all right documents

FSUIPC7.ini FSUIPC7.JoyScan.csv

Edited July 27 by John Dowson
events.txt file removed

[Kimchi]

Hi John, I want to thank you for the help!

 I thought about sticking the Logitech Joystick into another USB port. And now i see that my USB Pad is missing, which was detected before. 

 

FSUIPC7.ini FSUIPC7.JoyScan.csv

Edited July 27 by John Dowson
evetnts.txt file removed

[John Dowson]

Please don't attach the events.txt file (I have removed those) - that is the file that holds the presets, is installed by the installer and doesn't change.  It was the FSUIPC7.log file that you should also attach.

On 7/27/2025 at 12:33 PM, Kimchi said:

 I thought about sticking the Logitech Joystick into another USB port. And now i see that my USB Pad is missing, which was detected before. 

Did you change the USB port for the USB pad? Or is it in the same hub as another device, or was the logitech joystick connected to the same hub as the UDB pad? If using hubs, are they powered?

Your joyscan csv shows the device is detected twice, with the same GUID, but with different vendor and product ids:

Quote

,,, HIDscanning completed

N, x00, x0417, x0130, , -1, -1, 0, {NULL}, {NULL}, {A81689A0-4715-11F0-8013-444553540000}, Y, N
N, x00, x28DE, x11FF, , -1, -1, 0, {NULL}, {NULL}, {A81689A0-4715-11F0-8013-444553540000}, Y, N
 

,,, REGscanning completed

N, x00, x0417, x0130, usb pad, -1, 3, 0, {NULL}, {A81689A0-4715-11F0-8013-444553540000}, {A81689A0-4715-11F0-8013-444553540000}, Y, Y
N, x00, x28DE, x11FF, , -1, 3, 0, {NULL}, {A81689A0-4715-11F0-8013-444553540000}, {A81689A0-4715-11F0-8013-444553540000}, Y, Y

Not sure why its doing this - looks to be a strange usb issue - especially as this was previously the problem with your logitech joystick but now its with the UDB pad. You could try ignoring that dodgy entry with the empty name by adding:
    IgnoreDevice=0x28DE,0x11FF
to the [JoyNames] section of your FSUIPC7.ini file.

If that doesn't work, please show me the files again, but include the FSUIPC7.log and no the events.txt file (if you cannot see the log file, it is because you have windows explorer set to hide the extensions of known log files - change this setting).

John
 

[Kimchi]

Hi John, I have solved it and I'm getting too old for this...

Last week i changed my GPU from a 3060ti to a 9070xt and disconnected all USB cables. Reconnecting them i made a colour mistake and put the USB pad on the same hub as the Logitech X56 which draws too much power. By looking GOOD with a LIGHT i saw the mistake and now everything works again. 

 

So sorry for taking your time on this. Next time i will do more research myself. Thanks for the help!!

[John Dowson]

It did look like a USB hub power issue and the cable re-organisation is important information that wasn't included in your original posts.

Anyway, no problem - and  thanks for the update,

John

[Kimchi]

Hello John, sorry to bother you again but the problem remains. I have reorganized all devices on the various USB ports and in the device manager there are no more errors. I can open all device game properties and every device is working flawless. 

Yesterday evening i deleted the joyscan plus the ini file and started FS 2020. After putting the PMDG 737-800 on the taxispot i openend the Joyscan file and everything looked normal. I openend the INI file and everything looked normal. I started to bind all keys from three devices and after i was done i tested them all and everything worked flawless. I created a copy of the joyscan file and the ini file. I shutted down the PC and went to bed. 

Today i started FS 2020 and put the PMDG 737-800 on the runway and i noticed that buttons gave weird commands that i did not programmed the evening before. I openend up the INI and yet again i saw the Joystick is missing error. I dont know what to do anymore. 

 

Can you have a look again? Thanks for the help!

 

FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log

[John Dowson]

The problem seems to be this entry in the registry, which has the same GUID as your TCA Q-Eng 1&2 device:

Quote

N, x00, x28DE, x11FF, , -1, 1, 0, {NULL}, {72C59D80-4798-11F0-8007-444553540000}, {72C59D80-4798-11F0-8007-444553540000}, Y, Y

This seems to be a phantom xbox controller and I think is related to steam. Try ignoring that device, i.e. add
 IgnoreDevice=0x28DE,0x11FF
to the [JoyNames] section of your FSUIPC7.ini file.

I have added this for you in the ini attached below if you would like to download and try that.

Note this is what I also advised earlier when you had the same issue (see above). 

John

FSUIPC7.ini

P.S. See this thread from this comment onwards on this issue: 

 

Basically it only seems to happen when FSUIPC7 is auto-started by MSFS and when a Steam installation is being used.

Edited August 12 by John Dowson
P.S. added