Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
As a workaround, try switching off Xbox or PS4 configs for your device in Big Picture > Settings > Controller Settings so that global Big Picture config is not trying to scroll using any pedals, if you haven't already. Means you need to use KB and mouse or use controller of different type to wheel and pedals
Or
Just launch games on desktop using large mode and remove Big Picture bugs from the equation!.
Have not been able to use Big Picture global config to use Thrustmaster buttons for Big Picture navigation for more than a year. Need to double check on that actually! Am in habit of just using controller or KB + m for Big Picture navigation due too old bugs. In fact I in habit of using large mode to launch games without Big Picture because of long standing bugs with Big Picture! Lol
Steering wheels are Steam Input second class citizens. Not many Steam users use wheel and pedals so are low on priority list, I'm afraid.
Still fully functional in games if Steam Input is configured appropriately.
Sharing a workaround may help others, until Valve fix bug and they can only do that if they can reproduce. I know they struggle to reproduce many issues/bugs I and others have been reporting with steering wheels for years now.
Thanks for confirming that is expected behaviour, for wheels in general. I too am seeing unexpected behaviour with axis and wrong mappings with current Steam client beta and stable Steam client. Having trouble getting games to use wheel and pedals like expected. Thanks for tips on how to switch Big Picture global config
In the past have found no layout being mapped as being un expected behaviour because it broke steam o0verlays and Big picture navigation! lol Mapping a layout (without pedal axis being involved - just buttons on wheel base and paddle shifters) helped with getting wheel and pedals working with Big Picture so that steam overlay and game ui could be navigated using buttons on wheel, Just left the joystick mappings completely blank and did not map any pedal axis to controller layout bindings. Doing that will save making a custom Big Picture global config and achieve the same thing. Six and two threes. Nice to have a choice.
When using Steam stable client, m + KB, Shield Controller (Xbox type controller), Thrustmaster T500 RS wheel and pedals (PS3 type controller) with fully updated win 10 pro what I see is
https://youtu.be/RlKYC1S-B38
For me it was having no layout assigned to wheel base buttons that prevented use of wheel base buttons for use in Big Picture by letting global config be applied like expected. Assigning layout fixes.
Dpad and left stick down need tweaking in global desktop and big picture configs. Scrolling is not working like expected in global configs with any controller I use. Struggle to manually configure the button press and release times for getting a proper scrolling effect.
With global desktop config in some windows apps there is double input as something is mapping triggers on Xbox controller to scroll when Steam Input is applying mouse clicks.
I keep forgetting to save and keep loosing my custom Steam Input configs so am in habit of using mouse to use for dragging scroll bar at side of window instead of using broken scroll.
Can't manage saved layouts for controllers like expected, you can see Steam Input referring to my older saved layout when it "renames" RS T500 to T500 RS in the video. Maybe i saved layout as different type of controller.
Additional to defining layout, tweaking global configs and windows settings to fix scroll Steam Input still needs configured for game. Ànd device prioritization is a problem.
There are a few more related issues which I'll try and open new threads for.
EDIT: Was reproducing in stable what i was seeing in beta client. After opting out and back into Steam client beta have got everything working like expected, in fact better than expecetd. Facepalmed when i got scroll working in desktop config and used the new "Hide" feature to "prioriytise" input device. Even have working PS3 controller prompts for first time ever with Thrustmaster buttons too lol. Been a lot of updates today.