Steam Is Not Detecting Thrustmaster T500 RS Like Expected

[Balderick]

ISSUE: Steam Input does not list any detected devices after connecting Thrustmaster T500 RS to pc like expected.

OS: win 10 22h2 running Feb 9th build beta client

STEPS: Connect Thrustmaster T500 RS to pc and then view steam controller settings from large mode.

RESULT: Steam Input does not detect any input device.

EXPECTED: Steam Input should detect generic gamepad where i can use Definne Layout and set as ps3 type controller. Other steam user confirms Steam Input sees their Logitech G20 steering wheel and pedals as "usb game controllers" in latest Steam stable client.

MORE INFO: https://steamcommunity.com/groups/SteamClientBeta/discussions/1/3496509339514880438/
Have tried latest beta and stable steam clients. Have had discussion open for several months which has been completely ignored by Valve devs and get told to make my own thread when trying to add to other discussions with similiar issues.
Steam auto blkacklists Thrustmaster T500 RS due to hardcoding by Valve, which completely breaks end user configurability through steam input.
All Valve need to do is remove pid/vid for TM T500 RS from their blacklist and add them to whitelist for the new "usb game controllers" type controller as this appears to be a new supported controller type. Logitech G20 wheel and pedals gets detected as "USB Game Controllers" controller type for other steam user.
https://steamcommunity.com/sharedfiles/filedetails/?id=2933200699

[Balderick]

Steam is detecting Thrustmaster T500 RS which is confirmed in Steam log controller.txt

[2023-02-12 22:13:26] Local Device Found
  type: 044f b65e
  path: sdl://1
  serial_number:  - 0

[2023-02-12 22:13:26]   Manufacturer: 

[2023-02-12 22:13:26]   Product:      Thrustmaster T500 RS Racing wheel

[2023-02-12 22:13:26]   Release:      0

[2023-02-12 22:13:26]   Interface:    -1


[2023-02-12 22:13:28] Local Device Found
  type: 044f b65e
  path: sdl://1
  serial_number:  - 0

[2023-02-12 22:13:28]   Manufacturer: 

[2023-02-12 22:13:28]   Product:      Thrustmaster T500 RS Racing wheel

[2023-02-12 22:13:28]   Release:      0

[2023-02-12 22:13:28]   Interface:    -1


[2023-02-12 22:14:24] Exiting workitem thread



[2023-02-12 22:14:27] Opted-in Controller Mask for AppId 0: 2

[2023-02-12 22:14:27] BYieldingMarkControllerConfigsInUse

[2023-02-12 22:14:28] Local Device Found
  type: 044f b65e
  path: sdl://1
  serial_number:  - 0

[2023-02-12 22:14:28]   Manufacturer: 

[2023-02-12 22:14:28]   Product:      Thrustmaster T500 RS Racing wheel

[2023-02-12 22:14:28]   Release:      0

[2023-02-12 22:14:28]   Interface:    -1

What is forcing "interface -1" and does that confirm it gets blacklisted so does not get listed as detected device in controller settings graphical user interface?

There is no pid/vid set in blacklist section of config.vdf.

[Balderick]

Pretty sure this is part of the jig saw puzzle
https://github.com/libsdl-org/SDL/commit/f741adc86c8f5e7fc5c1863cf0d5e08b899d6209

"T500RS" appears to be typo

[Balderick]

Why is Steam not detcting t500 RS whhel and pedals if it is whitelisted in SDL source code?
ref: https://github.com/libsdl-org/SDL/commit/f741adc86c8f5e7fc5c1863cf0d5e08b899d6209

why cant i use steam sdl to map wheel and wheel base buttons to a ps2 or ps3 controller type like what used to be expected behaviour?

sdl3 seems to add better ffb options for steering wheels but i do not want that. Just simply want proprietyary software to do that in games and want steam sdl to map buttons only to a controller layout that is created by end user purely for big picture navigation out with game session..

So frustrating to know Valve broke this on purpose and can fix it with very little effort.

[Balderick]

Can somebody please share insight in to what the SDL_IsJoystickProductWheel section of SDL_joystick.c does or what its intended purpose is?
https://github.com/libsdl-org/SDL/commit/f741adc86c8f5e7fc5c1863cf0d5e08b899d6209
Why is Steam SDL completely ignoring Thrustmaster T500 RS so that it does not even show as detected device?, which imo is not expected behaviour as it breaks the ability of using define layout to save buttons on wheel and wheel base as ps controller type so it can be used for big picture navigation like how it used to work.

Steam SDL has also stopped showing ps button prompts for all controllers that are not detected by Steam Input as a ps controller type, even when playstation configs are the only option set in general controller settings and/or define layout is used to save layout as ps3 type controller and playstation configs only option set - so even if i did get Thrustmaster wheel and pedals detected like expected there are other issues preventing me from using Steam SDL to anyhwhere near like expected. I used to be able to use Steam Input to configure everything myself and steam sdl just feels like it is now hardcoded and broken because the hardcoding i snot how i would configure things to my liking and needs.
slouken did not seem to acknowledge this as a problem in another thread made by other steam user recently afterr asking for more info. which may explain why it has never been fixed.


imo i do not need sdl to know that thrustmaster t500 rs is a wheel as i depend on proprietary drivers to use T500 RS in games that natively support that whhel.


I feel Valve are breaking the steam experience on steam for windows just to benefit steam for linux users, knowing sdl 3 brings better support for ffb on devices like wheels makes the t500 rs not showing as detected device even more alarmingly unexpected behaviour..

I do not need sdl to manage the ffb on t500 rs since my choice of platform is supported by manufacturer through proprietary drivers, am sure if steam for linux users better understood how to configure steam sdl they would want working wheel buttons in big picture ui and in games too. WE all should be able to configure sdl more but we cant if steam sdl does not show t500 rs as a detected device forcing us to rely on purely proprietary drivers and those only.

Why cant i use staem sdl to get working controller in big picture ui and switch steam input OFF for game befor elaunching it so i can use steam sdl and my wheel to their full potential?

Can somebody make a pull request for removing T500 RS from SDL_IsJoystickProductWheel please? as the logitech g2* wheel shown in screenie above does get detected but it does not seem to be listed in SDL_IsJoystickProductWheel
Why does logitech g2* wheel get detected as usb game controllers? expected behaviour is it gets detected as generic controller.

imo Valve need to start providing more documented changes in changelogs so steam users can point to exact updates that brought the changes far more easily.

i no longer know or understand expected behaviour and it is making steam feel even more broken, flaky and bug ridden. Everything used to be way more configurable and intuuitive compared to the steam experience today..


Why am i even having to rely on sdl github repos issues and changelogs to make sense of this and not getting support from Valve or steam community?

[Balderick]

ds4windows can not detect Thrustmaster T500 RS's HID compliant game controller device either. DS4Windows detects device but can not see it as connected like what windows device manager and joy.cpl sees. Recent firmware update for T500 RS makes it show as Media device and Entertainmant device category only in legacy control panels devices and printers section.. No HID compliant controller device ever gets shown in devices section like with older firmware versions. Device manager confirms both hid compliant game controller and thrustmaster t500 rs racing wheel are connected and working properly


When using leagcy control panel to access joy.cpl noticed message below category section of control panel window saying "this device can work faster if usb 3.0 is used" and not sure if this causes device/s to get detected with different hid/vids when using usb 3

When using usb 3 with latest firmware on T500 RS windows sees HID compliant game controller and Thrustmaster T500 RS Racing wheel (USB) devices.


with hardware id's for HID compliant game controller
https://steamcommunity.com/sharedfiles/filedetails/?id=2942272518
and capabilities for HID compliant game controller
https://steamcommunity.com/sharedfiles/filedetails/?id=2942271196

Joy.cpl gives warning (firendly reminder) joy.cpl should never be run for T500 RS device with game running - as it loads different mapping for HID compliant game controller for testing ffb effects
https://steamcommunity.com/sharedfiles/filedetails/?id=2942271723

Did recent firmware updates for T500 RS break steam input and sdl support?

I just want the hid compliant game controller detected so wheel base and buttons can be maapped as simple gamepad with no axis saved as ps3 type controller through define layout. Just like old steam. Pretty sure my old defined layouts for T500 RS HID compliant game controller that were uploaded years ago should still be in steam cloud somewhere though appreciate we were never allowed to share those configs, intnded purpose was to help keep database of supported controllers updated.

No need to force SDL_IsJoystickProductWheel for T500 RS at this breaks steam input from being able to apply basic_gamepad and other simple controller layouts for steam bpm ui navigation since it gets hidden from Steam Input

The expected behaviour imo with sdl isjoystickwheel is T500 RS gets detected as usb steering wheel and all axis and buttons and ffb are all configurable through steam input ui's

Steam not detecting T500 RS is not game breaking issue but is a reminder of how broken steam input is.

[Balderick]

Using https://gitlab.com/ryochan7/sdl2-gamepad-mapper to detect T500 RS and make sdl config for simple gamepad config just using buttons on wheel and wheel base

0300d9d04f0400005eb6000000000000,Thrustmaster T500 RS Racing wheel PS2 gamepad buttons,a:b5,b:b4,x:b3,y:b2,back:b6,guide:b12,start:b7,leftshoulder:b9,rightshoulder:b8,leftstick:b10,rightstick:b11,dpup:h0.1,dpleft:h0.8,dpdown:h0.4,dpright:h0.2,platform:Windows,
crc:d0d9,

Now just need steam to show T500 RS as detected device like it used to for that config to load.

[tintingaroo]

May be a different situation for the T500 but current behaviour for me with an un-defined gamepad is that it requires setting up/defining new BPM side. Prior to that, old BPM shows no devices detected.

Is new BPM offering you the Begin Setup option? (Menu > Settings > Controller)

[Balderick]

"No controller detected" so cant access test input device ui from nbpm.

Have tried pressing ps button and start/select to try and see if it triggers the unhide thing but simply cant get Steam to apply a steam ui config

similar things happens with ds4windows - cant connect to device even though it sees the decice, interestingly same issue occurs with Thrustmaster eSwap X Pro controller in ds4windows

Could be WGI thing relating to Thrustmaster firmware/software/drivers. Software gui for T500 RS is a custom joy.cpl config
https://steamcommunity.com/sharedfiles/filedetails/?id=2942271723

Some recent changes have been made to sdl source code relating to WGI
https://github.com/libsdl-org/SDL/commit/110e4e133453cc4f9c466a6312f7f52d02eff516
https://discourse.libsdl.org/t/sdl-use-wgi-instead-of-xinput-for-windows-10-uwp-apps/33730

and libusb-whitelist discussion seems relative
https://github.com/libsdl-org/SDL/pull/6014

[kw_lxxi]

Originally posted by Balderick:

Steam is detecting Thrustmaster T500 RS which is confirmed in Steam log controller.txt

[2023-02-12 22:14:27] Opted-in Controller Mask for AppId 0: 2

[2023-02-12 22:14:27] BYieldingMarkControllerConfigsInUse

[2023-02-12 22:14:28] Local Device Found
type: 044f b65e
path: sdl://1
serial_number: - 0

[2023-02-12 22:14:28] Manufacturer:

[2023-02-12 22:14:28] Product: Thrustmaster T500 RS Racing wheel

[2023-02-12 22:14:28] Release: 0

[2023-02-12 22:14:28] Interface: -1[/code]

What is forcing "interface -1" and does that confirm it gets blacklisted so does not get listed as detected device in controller settings graphical user interface?

There is no pid/vid set in blacklist section of config.vdf.

Same thing is happening to me. I have Warthog throttle and joystick, and T16000 pedals...
throttel and pedals are visible on steam, but not the joystick.
But in the controller.txt the 3 of them are there, and the 3 of the with the same lines (release 0, interface -1)... so is not about "interface -1"