Steam New Big Picture Mode "Test Input Devices" Breaks Controller Functionality.

[Fromlostdays]

First, my setup:

Windows PC
Wireless Xbox Elite Series 2
Steam

There's an option under the New Big Picture UI under Settings/Controller called Test Input Devices.

I clicked "Begin Test" because of some other controller problem I was having, and then I clicked Setup Input Devices.

This allows you presumably to rebind your controls. However, since I did this, only the A and B buttons will register as inputs. It seems to let you go through the binding process with all the buttons, but after, only A and B work rendering the UI unusable, and is also affecting games launched from Desktop Mode. No other buttons will register.

I'm pretty sure this is a bug, but anyone have any idea how to fix in the New Big Picture Mode? Like does steam maybe store this info in a file I could just delete and revert steam back to default controls?

Oddly enough, opting out of the Beta fixes the problem for me right now.

[slouken]

Do the buttons register if you go back into "Test Input Devices"? If not, are you able to restart the "Setup Input Devices" process and get working input again?

[Fromlostdays]

No, yes and no. Again, I can only vouch for this to be true when I'm using Beta versions, but if I do the whole process over again... when I'm actually binding the buttons they seem to work (example: it'll ask for X I'll press X and it will seemingly accept it as a button press during the binding process, this behavior never changed). But when it's over and its showing green indicators that the buttons are bound, only A and B light up and no other button on the controller will respond at all to either the UI or games. I've done the rebinding process at least a dozen times.

Edit: I thought of a better way more succinct way to explain the above paragraph. I can say the only time any button, trigger analog etc. works in steam is during the binding process itself. Before and after, only A and B work, no matter how many times I do it or what I try to bind the buttons to... if that makes it more clear.

I'm really thinking about it, and I was having trouble with the elite paddles at the time and that's what had me tinkering in the settings. But I'm almost positive that the first time I Setup Input Devices, I set A and then B and then there's the option to "Skip with A" meaning skip the bind and I may have skipped the rest realizing this wasn't going to help me with the paddles. So I may have done this to myself.

I say that because if there's a bug it might be the skipping of binding buttons that triggered it. My assumption was that if I skipped a binding, it would stay as it was already bound... but I guess what could have happened is that I instead bound all of the rest of buttons to A and they are locked there somehow. Because I can't rebind anything now.

So if I were checking on the backend, I'd check:

that pressing A to skip a binding during that process is actually leaving the current binding.

that pressing A to skip a binding isn't unintentionally binding buttons to A.

that there is some measure or way to revert to default in the event someone dumb like me messes it up.

As its working for me now without the beta checked I'm hesitant to test further because I freaking love this new UI and don't want to break it again haha, but if I can help let me know.

[slouken]

Oh yeah, if you skip a binding the assumption is that your controller doesn't have that control and so it's left unbound. All you have to do is use a mouse to go back in and start the binding process over again.

[Balderick]

It would be cool if we could save controller layout as individual name like old define layout ui > preferences

then we know our own custom controller layout is being used and not the auto generated one created by Steam Input

Should i be trying to rely on newbigpictures controller layout ui? or is define layout from large mode still supposed to be functional too? Today the old one is FUBAR, though was working sweet as with 23rd Jan update after it being wonkly for months


all of these things seem broken in that newbigpicture uses differentr named controller layout configs compared to what large and oldbigpicture modews use - there seems to be conflicting or mismatching configs. Expected behaviour is Steam Input just to use the configs i tell something seems more hardcoded with newbigpicture

I think the new ui is not clear enough that new controller layout config is being made. We should be able to tell steam input which supported controller type we want to save that layout as too. Especially for controllers that support multiple modes or for third party licenced devices like PS type steering wheel used on pc. ref: https://github.com/ValveSoftware/steam-for-linux/issues/8293#issuecomment-1269535289

Additionally if "you skip a binding the assumption is that your controller doesn't have that control and so it's left unbound. " why is there no provision to add buttons that are missing?

Where is the "clear" button to leave everything unbound?

[Fromlostdays]

Opprinnelig skrevet av slouken:

Oh yeah, if you skip a binding the assumption is that your controller doesn't have that control and so it's left unbound. All you have to do is use a mouse to go back in and start the binding process over again.

I appreciate that but, thats exactly what doesn't work. I've rebinded it multiple times activating it with the mouse, it always ends with just A and B working. I certainly must have tripped some kind of bug. That's why I was asking where the bindings were stored so maybe I could delete the file and revert it back to normal, because rebinding is definitely broken in the betas for me. Its as if its stuck on that first rebind indefinitely. Nothing I can do will change it.

[Balderick]

Have you tried using the Define Layout ui from oldbigpicture or large mode?

It is pretty much broken for me too, as of today.
What controller type are you using?

For me MS Xbox One S controller (gen2 xboxone) and Thrsutmaster eSwap X Pro (gen3 xboxone) are working with more than A and B

Check controller.txt and controller_ui.txt log files. When i had controller locked to no input yesterday i could see some kind of lizard mode config was being told to load by Steam Input. Possibly because of the recently added

Opprinnelig skrevet av Valve:

Big Picture Mode

• Hide the cursor when in gamepad-navigation mode in Big Picture

But yesterdays or todays hotfix fixed it. Desktop config now gets loaded like expecetd after exiting newbigpicture. Just exiting a game in newbigpicture is another scenario gamepad-navigation config maybe trying to load and steam input looses all input to controller.

[Fromlostdays]

Opprinnelig skrevet av Balderick:

Have you tried using the Define Layout ui from oldbigpicture or large mode?

It is pretty much broken for me too, as of today.
What controller type are you using?

For me MS Xbox One S controller (gen2 xboxone) and Thrsutmaster eSwap X Pro (gen3 xboxone) are working with more than A and B

Check controller.txt and controller_ui.txt log files. When i had controller locked to no input yesterday i could see some kind of lizard mode config was being told to load by Steam Input. Possibly because of the recently added

Opprinnelig skrevet av Valve:

Big Picture Mode

• Hide the cursor when in gamepad-navigation mode in Big Picture

But yesterdays or todays hotfix fixed it. Desktop config now gets loaded like expecetd after exiting newbigpicture. Just exiting a game in newbigpicture is another scenario gamepad-navigation config maybe trying to load and steam input looses all input to controller.

I just saw this and, as a result, reinstalled the beta. Controller issue does seem to be fixed now, at least, my controller is once again working to navigate the Big Picture UI and working in game again.

I'm hesitant to test anything else right now, as its working, but if it stops I'll try these suggestions.

Xbox Elite Series 2, in terms of controller.

In terms of "Steam looses all input to the controller" on exiting a game, it does that to me too. But, at least in my case, it wasn't losing input, it was that the entire steam window (big picture) was somehow losing focus in windows when exiting games. All I had to do to fix it was to click steam with the mouse once to focus it. It isn't a perfect solution for a couch gamer like me, but I was thinking I'd write an AHK script to refocus steam after a while if the problem continued.

Thanks for the heads up!

[The Detective Columbo]

Opprinnelig skrevet av slouken:

Oh yeah, if you skip a binding the assumption is that your controller doesn't have that control and so it's left unbound. All you have to do is use a mouse to go back in and start the binding process over again.

Not only is the bug described by OP still present, but with the removal of "Define Layout", all known workarounds are patched out. My Steam install is basically half-broken since 'controller games' are unusable.

[Watermelon {JESUS IS LORD}]

Opprinnelig skrevet av slouken:

Oh yeah, if you skip a binding the assumption is that your controller doesn't have that control and so it's left unbound. All you have to do is use a mouse to go back in and start the binding process over again.

i want to thank valve employees for dealing with the toxicity in this place, you guys are the best and trying your hardest to work out the bugs based on user reports, many thanks

[-VG- Napster]

Opprinnelig skrevet av slouken:

Do the buttons register if you go back into "Test Input Devices"? If not, are you able to restart the "Setup Input Devices" process and get working input again?

Steam has so many options to configure controllers and play around with buttons and triggers yet iam not able to find any way to actualy input test the changes i made

for example iam tuning the left trigger of a controller to be more sensitive or vise versa there is no way to input test and actualy see how it would react.