marco chan

It works. Thanks a lot. Actually, I am also looking into that device. One interesting observation is that the device seem only appears when fsuipc is in auto-run mode via the MSFS exe.xml. When manually starting fsuipc or restarting the program, that device disappears from the JoyScan file.

okay. Attached is the JoyScan file. Thanks for your help. FSUIPC7.JoyScan.csv

Hi John, In this case, any suggestion to avoid this happen again? Since the name of controller are randomly missing. Although the log file can able to show the name as normal... Or is any option/flags can be add to let the program mapping the letter only base on the GUID and ignore the controller name? Thanks. 109 ---------------------- Joystick Device Scan ----------------------- 109 Product= Alpha Flight Controls 109 Manufacturer= Honeycomb Aeronautical 109 Serial Number= B0D62D1726183B00 109 Vendor=294B, Product=1900 (Version 2.32) 109 GUIDs returned for product: VID_294B&PID_1900: 109 GUID= {DA65E8F0-62FA-11EB-8001-444553540000} 109 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0 109 Product= WINWING SKYWALKER Metal Rudder Pedals 109 Manufacturer= Winwing 109 Serial Number= 3F8640B2A416E331A3160002 109 Vendor=4098, Product=BEF0 (Version 1.8) 109 GUIDs returned for product: VID_4098&PID_BEF0: 109 GUID= {A47B9AE0-E55C-11EE-8001-444553540000} 109 Details: Btns=15, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R65535,U65535,V65535,X0,Y0,Z0 109 Product= Bravo Throttle Quadrant 109 Manufacturer= Honeycomb Aeronautical 109 Serial Number= A6F52D091D2D3B00 109 Vendor=294B, Product=1901 (Version 1.5) 109 GUIDs returned for product: VID_294B&PID_1901: 109 GUID= {90950270-68C6-11EB-8001-444553540000} 109 Details: Btns=48, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z1023 109 Product= Controller (XBOX 360 For Windows) 109 Vendor=28DE, Product=11FF (Version 0.0)

Hi Support, It seems that there is a bug related to the automatic letter assignment feature. Originally, I configured the letter assignment in the FSUIPC file as follows: [JoyNames] A=Bravo Throttle Quadrant A.GUID={90950270-68C6-11EB-8001-444553540000} B=Alpha Flight Controls B.GUID={DA65E8F0-62FA-11EB-8001-444553540000} C=WINWING SKYWALKER Metal Rudder Pedals C.GUID={A47B9AE0-E55C-11EE-8001-444553540000} Here is the FSUIPC file I extracted when the bug occurred. As you can see, the control "{90950270-68C6-11EB-8001-444553540000}" was originally supposed to be mapped to the letter "B". However, the program created a letter "D" with the same GUID instead of mapping it to "B". This issue is not limited to the alpha flight control but happens randomly with every controller. Incorrectly mapping to another letter causes all key bindings to be lost. Could you please advise on how the support team can investigate and resolve this bug? [JoyNames] A=Bravo Throttle Quadrant A.GUID={90950270-68C6-11EB-8001-444553540000} B=Alpha Flight Controls << MISSING JOYSTICK >> B.GUID={DA65E8F0-62FA-11EB-8001-444553540000} C=WINWING SKYWALKER Metal Rudder Pedals C.GUID={A47B9AE0-E55C-11EE-8001-444553540000} 0= 0.GUID={DA65E8F0-62FA-11EB-8001-444553540000} 1=WINWING SKYWALKER Metal Rudder Pedals 1.GUID={A47B9AE0-E55C-11EE-8001-444553540000} 2=Bravo Throttle Quadrant 2.GUID={90950270-68C6-11EB-8001-444553540000} D= D.GUID={DA65E8F0-62FA-11EB-8001-444553540000} Also attached the log file for your reference. FSUIPC7.log