You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 1, 2024. It is now read-only.
Hi all, just wanting to discuss some observations before opening issue. The gist is ds4windows is not connecting to Thrustmaster usb devices, Thrustmaster eSwap X Pro and Thrustmaster T500 RS racing wheel.
Enabling verbose logging confirms the devices can be seen but are not connected.
XinputChecker can see joysticks button and analog triggers with good layout for eSwap X Pro.
This is a duplicate of #2793 as the same end result is same - no controller gets detected like expected. Though manifests slightly differently as no controller ever gets detected for me.
I also think this thread is directly related to why T500 RS never gets detected either. #2589
AS ds4windows does not seem to be finding the raw capable drivers like expected.
eSWap X Pro
eSWap Pro shows up as two different devices in legacy control panels devices and printers page. One eSwap X Pro controller and the other being XINPUT-cpmpatible-device.
Capabilities are found at #2793 (comment)
eSwap X pro uses tmgipbus service
Device USB\VID_044F&PID_D012\000075FA1D167830 was started.
Driver Name: oem11.inf
Class Guid: {05f5cfe2-4733-4950-a6bb-07aad01a3a84}
Service: tmGipBus
Lower Filters:
Upper Filters:
whereas three devices show up for XINPUT-compatible-game-controller
and events tab shows latest entry for HID-compatible-game-controller as
Device HID\VID_045E&PID_02FF&IG_00\8&7b375b2&0&0000 was started.
Driver Name: xinputhid.inf
Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}
Service:
Lower Filters:
Upper Filters: xinputhid
T500 RS
T500 RS uses same container for two HID devices so shows up in Devices and Printers using legacy control panel (and Device Manager) as one device.
HID-compliant-game-controller capabilities are
with the USB Input Device capabilities looking like
Going to Events tab in device properties for HID-compliant-game-controller the device is seen as starting without using any service
Device HID\VID_044F&PID_B65D\6&2f4d0af5&2&0000 was started.
Driver Name: input.inf
Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}
Service:
Lower Filters:
Upper Filters:
whereas the USB Input Device starts with HidUSB
Device USB\VID_044F&PID_B65D\5&521a615&0&3 was started.
Driver Name: input.inf
Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}
Service: HidUsb
Lower Filters:
Upper Filters:
which ds4windows should be able to detect as simple generic gamepad or ds3 controller to emulate xbox or ds4 controller bombu
All this was when no driver/software bundle for T500 RS was installed from Thrustmaster. The same is seen with proprietary software installed though that device is seen as an Entertainment device in Multimedia Devices section of legacy control panels's devices and printers page. I uninstalled it as it uses custom joy.cpl config for testing device layout and ffb funstions.
After finding ds4windows and sdl-gamepad-mapper worked amazingly well for working around and fixing issues seen in steam runtime due to sdl and other issues when using 8Bit Do Pro2 in A mode (macos mode) on windows was hopeful ds4windows could help me out for getting steam input to detect T500 RS.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all, just wanting to discuss some observations before opening issue. The gist is ds4windows is not connecting to Thrustmaster usb devices, Thrustmaster eSwap X Pro and Thrustmaster T500 RS racing wheel.
Enabling verbose logging confirms the devices can be seen but are not connected.
XinputChecker can see joysticks button and analog triggers with good layout for eSwap X Pro.
Using USB Device Tree Viewer sees eSwap X Pro as connected -
New Text Document (3).txt
and T500 RS as connected -
New Text Document (3).txt
This is a duplicate of #2793 as the same end result is same - no controller gets detected like expected. Though manifests slightly differently as no controller ever gets detected for me.
I also think this thread is directly related to why T500 RS never gets detected either. #2589
AS ds4windows does not seem to be finding the raw capable drivers like expected.
eSWap X Pro
eSWap Pro shows up as two different devices in legacy control panels devices and printers page. One eSwap X Pro controller and the other being XINPUT-cpmpatible-device.
Capabilities are found at #2793 (comment)
eSwap X pro uses tmgipbus service
whereas three devices show up for XINPUT-compatible-game-controller
and events tab shows latest entry for HID-compatible-game-controller as
T500 RS
T500 RS uses same container for two HID devices so shows up in Devices and Printers using legacy control panel (and Device Manager) as one device.
HID-compliant-game-controller capabilities are
with the USB Input Device capabilities looking like
Going to Events tab in device properties for HID-compliant-game-controller the device is seen as starting without using any service
whereas the USB Input Device starts with HidUSB
which ds4windows should be able to detect as simple generic gamepad or ds3 controller to emulate xbox or ds4 controller bombu
All this was when no driver/software bundle for T500 RS was installed from Thrustmaster. The same is seen with proprietary software installed though that device is seen as an Entertainment device in Multimedia Devices section of legacy control panels's devices and printers page. I uninstalled it as it uses custom joy.cpl config for testing device layout and ffb funstions.
After finding ds4windows and sdl-gamepad-mapper worked amazingly well for working around and fixing issues seen in steam runtime due to sdl and other issues when using 8Bit Do Pro2 in A mode (macos mode) on windows was hopeful ds4windows could help me out for getting steam input to detect T500 RS.
Is this all really a WGI issue?
Beta Was this translation helpful? Give feedback.
All reactions