Trust GXT 1230 SWITCH bluetooth mode

[Simo75]

Hi, is it possible to add the gamepad in question ? Unfortunately at present I do not believe it is in the database. :( In PC mode (with its doongle) it sees it as x360 but obviously no motion control. Thanks in advance.

[Simo75]

Steam log:

[2023-05-29 19:31:10] Local Device Found type: 057e 2009 path: \?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002057e_pid&2009#9&369dcb5e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} serial_number: 0c6b30896325 - 0

[2023-05-29 19:31:10] Manufacturer: Nintendo

[2023-05-29 19:31:10] Product: Wireless Gamepad

[2023-05-29 19:31:10] Release: 0

[2023-05-29 19:31:10] Interface: -1

[2023-05-29 19:31:10] Switch: Bluetooth

[2023-05-29 19:31:10] !! Steam controller device opened for index 1.

[2023-05-29 19:31:10] Steam Controller reserving XInput slot 1

[2023-05-29 19:31:13] Switch: failed SetIMUSensitivity

[2023-05-29 19:31:13] Switch: detected 3rd-party controller

[2023-05-29 19:31:13] Switch Controller calibration:

[2023-05-29 19:31:13] Sensor 0: bias -688, sensitivity 4.0000 [2023-05-29 19:31:13] Sensor 1: bias 0, sensitivity 4.0000 [2023-05-29 19:31:13] Sensor 2: bias 58, sensitivity 4.0000 [2023-05-29 19:31:13] Sensor 3: bias 0, sensitivity 2.0000 [2023-05-29 19:31:13] Sensor 4: bias 0, sensitivity 2.0000 [2023-05-29 19:31:13] Sensor 5: bias 0, sensitivity 2.0000 [2023-05-29 19:31:13]

[2023-05-29 19:31:13] BYieldingQueryAccountsRegisteredToController

[2023-05-29 19:31:14] CClientJobFetchPersonalizationFileID - AutoCloud

[2023-05-29 19:31:19] Controller device closed after hid_read failure

[slouken]

Does it work with testgamecontroller/testgamepad from the SDL test programs?

[Simo75]

Does it work with testgamecontroller/testgamepad from the SDL test programs?

Sorry, link for the tester ? This gamepad via bluetooth seems transparent to the system, it is correctly associated but it ends there.

[slouken]

SDL/test/testgamecontroller.c

[slouken]

SDL 2.0 is now in maintenance mode, and all inactive issues are being closed. If this issue is impacting you, please feel free to reopen it with additional information.