[Steam Input] Button Chord configuration ignores disabled Xbox Configuration Support

[Aemony]

ISSUE
Steam acts upon the Steam Button Chord configuration whenever you hold down a controller button and press the Xbox Guide Button on the controller.

It does this despite the following:
* Xbox Configuration Support is disabled.
* Guide Button Focuses Steam is disabled.
* Xbox Controller have been deregistered from my Steam account.
* Multiple restarts of the Steam Client.
* Upgrade to Beta/Downgrade to Stable.
* Steam does not have focus.

CONTROLLER
Xbox One Wireless Controller (regular wireless, aka non-Bluetooth)

OS
Windows 10 Version 1703 (OS Build 15063.540)

STEPS

1. Disable "Open Game Bar using this button on a controller: [GUIDE]" in Windows 10.
   
2. Hold down the Guide Button on the controller.
   
3. Move the right analog stick around to move the mouse around. Or press LB to right click, RB to left click, right stick UP to send Volume Up or right stick DOWN to send Volume Down.

RESULTS
My mouse moves around and I can interact and send keyboard and mouse commands using my Xbox Controller.

EXPECTED
Nothing should happen at all! I've disabled all of those things in Steam and Big Picture Mode so Steam should leave my controller alone!

WORKAROUND
Enabling Open Game bar using this button on a controller: [GUIDE] prevents this from happening.

[Aemony]

Minor update: The issue is that the Steam Button Chord configuration that can be accessed despite Xbox Configuration Support being disabled in Big Picture Mode.

I've updated the topic and opening post to better reflect the issue.

Edit: Just to be clear: It doesn't matter if you're in Big Picture Mode or in the Windows desktop. Steam acts upon the Button Chord configuration anywhere as long as the Guide button is being held down, despite the disabled Xbox Configuration Support.

[Aemony]

Another Steam user reported that this is intended and is not a bug. Let me just shoot down that notion for anyone who shares it: Holding the Guide button for 6 seconds turns off wireless Xbox controllers.

Think about that for a minute.

Even if it were intended (and I really doubt that it is), any attempts of actually using the Chord configuration in any meaningful way with a wireless Xbox controller will turn the controller off within seconds. Further on, any attempts to /turn off/ a wireless Xbox controller will result in the mouse cursor moving or volume changing if the analog sticks are slightly outside of the deadzone area (which mine usually are).

Ergo, it makes no sense for that function to begin with.

Another minor note: Guide + Y (turn off controller) doesn't even work for wireless Xbox controllers, if someone though about mentioning how that is easier than holding down the Guide button for 6 seconds.

[Aemony]

Another workaround is using this DLL proxy to forcefully prevent Steam from making use of the Guide button: http://steamcommunity.com/groups/bigpicture/discussions/1/846939071346659003/?tscn=1447541997#c35221031602951514

[Aemony]

This still happens, just saying...

[angelar]

Your problem is this isn't a bug, which is probably painfully obvious two years later.

[Aemony]

Цитата допису angelar:

Your problem is this isn't a bug, which is probably painfully obvious two years later.

Even if Valve might see it as a "feature", that does not stop me from viewing it as a bug.

I, for one, expect an application to respect my settings. If "Xbox Configuration Support" is supposed to dictate whether Steam's controller configuration support for Xbox controllers is enabled or not, then it follows that with that setting disabled, Steam should not mess with the controller.

None the less, I've learned to prevent Steam from completely messing with the guide button by allowing Windows 10 to use it instead (which doesn't actually use it when the game bar is disabled), aka the "Open Game bar using this button on a controller: [GUIDE]" setting, as well as by removing all pre-default bindings from the guide button chord configuration.

I expect Valve will eventually solve this bug. Going by their track record, I expect an official fix to arrive sometime in the next 3-8 years.

I mean, we're still waiting for that option to prevent the Guide button from opening Big Picture.

Thank god we have Microsoft and the community available to fix what Valve does not.

[lukaself]

Hey!

This is still happening... why the hell is this still a thing?

I have kids at home and four wireless gamepad and they managed to delete folders on my desktop just by playing with them and hitting random keys... and this behaviour can't be disabled anywhere, I just wasted the last two hours looking for an option in steam and reading the forums. I suspected it was the steam controller settings because of course it was, it's not the first time it caused me issues, or the second.

At any rate, thank you for the workaround Aemony - I don't understand why anyone would consider this a feature and not a bug... this not in steam beta by the way, I'm using the main build.

All gamepad support is disabled :
https://imgur.com/S3C8JnW
Even SBP confirms that the desktop configuration is disabled
https://imgur.com/45CQGV7

...which was awfully confusing since it was actually the chord feature acting up, this is obviously why it took me so long to even find this thread.

[putnamto]

still a problem.

how is it a feature when i disable it and it still brings up BP when i use the guide button to turn off my controller?

[JackHoliday]

Guys try this:
Steam settings -> Controller -> Guide Button Chord Configuration -> Browse Configs and apply "Gamepad" config from "Templates" menu.

[ReptilianWorldOrder]

This bug is still live and well but I might not be for much longer cause this is gonna give me an aneurysm


Even the disable checkboxes don't do anything half the time. Hell the freaking "don't show notifications for profile switches in desktop mode" doesn't even stop the notifications for me most of the time.

All the settings are conflicing and overwriting the other settings and its total chaos where none would exist in the absence of interference.

Just let me kill steam chord. Let me disable it from even trying to hijack the controller at any time.

[It's Me LuiLui]

Цитата допису JackHoliday:

Guys try this:
Steam settings -> Controller -> Guide Button Chord Configuration -> Browse Configs and apply "Gamepad" config from "Templates" menu.

. . . Hello from the year 2020 . . . I want to confirm that this worked for me. Thank you.

[TicTac]

Thanks, I've had this issue and didn't understand why for the longest. Didn't assume Steam be the cause of all of it, but here we are.

[UncleYar]

This kept triggering on its own even though I wasn't pressing the guide button. Turns out playing a game with Steam's on-screen keyboard covering part of the screen with no obvious way to remove it isn't much fun.

I'll try the "Gamepad" config (basically the equivalent of unbinding every button in the Guide Button Chord settings. But Steam really needs to provide an option to turn this off. And fix this bug, it's madness.

[Autositz]

This bug is still in the client.

Valve will never fix this bug because Valve prefers to add useless "FEATURES" instead of fixing bugs in the vital part of the ecosystem.. the Steam Client

[civicsarecool]

Цитата допису Aemony:

Another Steam user reported that this is intended and is not a bug. Let me just shoot down that notion for anyone who shares it: Holding the Guide button for 6 seconds turns off wireless Xbox controllers.

Even if it were intended (and I really doubt that it is), any attempts of actually using the Chord configuration in any meaningful way with a wireless Xbox controller will turn the controller off within seconds. Further on, any attempts to /turn off/ a wireless Xbox controller will result in the mouse cursor moving or volume changing if the analog sticks are slightly outside of the deadzone area (which mine usually are).

Ergo, it makes no sense for that function to begin with.

I'm using a new Xbox Series wireless controller.

Using the Chord function to move the mouse from the controller works, but like the above says, it's annoying to use because holding the Xbox button turns the Xbox controller off after ~10 seconds. To use the mouse without turning the controller off, I have to constantly keep pressing and holding the Xbox button.

For the Xbox controller, it seems like holding the Xbox button to turn the controller off is a feature of the controller itself and cannot be changed. If holding the Xbox button to turn off the controller could be changed to turn off the controller with a different combo of buttons (perhaps Xbox button + Right Trigger + Left Trigger for 5 seconds) or could be disabled all-together, the Chord configuration would be more useful in Desktop mode.