Valve released a new Steam Deck Beta update that includes a useful tweak to its Xbox controller detection.

There's a bit of a problem with modern Xbox controllers and Bluetooth, where they won't properly connect up with SteamOS / Linux unless they've gone through a firmware update. I've seen a lot of support requests about this issue over the years and so it's good to see Valve highlight it directly. While it's a Steam Deck Beta Client update, it should apply to other SteamOS devices too.

all 54 comments

sorted by: hot top controversial new old
[–] 16 points 11 months ago (7 children)

It's hard to fault Steam's controller layer, but I really wish they finally found a way to parse gyro data from third party controllers without having to run them on Switch mode. That goes for Microsoft and their own drivers. At this point it's weird to keep pretending the Windows controller APIs are supposed to work on their first party Xbox controllers only.

  • source
  • hideshow 7 child comments
  • [–] 8 points 11 months ago* (last edited 11 months ago) (6 children)

    It's not possible as xinput doesn't support gyroscopes, the controller simply doesn't report that data. The "Switch" mode is setting it to be a mostly standard HID/DirectInput device so that all of those inputs can be accessed, but that requires something (Steam Input) to sit between the controller and the game to map the inputs together, and the game has to also support non-xinput controllers - otherwise you are just mapping them back to xbox inputs. The exception is a game that support directinput... well, directly. Like sim racers etc.

    There is now the option of going "hardware" Steam Input as well, as is done by the HORIPAD for Steam, but it is something the controller has to do.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 2 points 11 months ago* (5 children)

    Yes, I'm aware, that's why I'm calling out it's weird that XInput doesn't support gyro, because we're a long way away of it being just based on Xbox controller support and a whole bunch of other controllers with a whole bunch of other features now go through it. If MS doesn't want to add gyro that's up to them, but Windows supporting it natively is way overdue. Of course at that point older controllers would probably need a firmware update, but hey, we'll cross that bridge when we get to it.

    In practice the situation we're having is games are defaulting to Xinput and relying on Steam Input as an intermediate layer for additional features, so the end result is that gyro is... not NOT supported, but often not acknowledged at all, so you end up with a bunch of situations where you have to config gyro manually per game as a bit of a Steam-level hack, and then your controller is all wonky anywhere other than Steam because the way Switch/DI/PS input modes get picked up in non-Steam stuff can be weird.

    And it gets worse in handhelds where you're absolutely at the mercy of how the manufacturer decided to set up their controller and gyro support, and sometimes need to do a lot of weird stuff to pass it on outside of Steam.

    It's the jankiest part of controller set up left on PC gaming, and it's all down to this weird "mom and dad aren't talking" dance where MS keeps pretending PC controllers are fundamentally Xbox controllers at the XInput layer and Steam is the de facto curator of the controller support but has no interest (and to be frank no expectation or need) to have their controller layer work outside their launcher.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 11 months ago* (4 children)

    Researching this a bit more, there is an answer in the making already - GameInput. How long that will take to take over from every game using xinput is left to be seen.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 11 months ago* (last edited 11 months ago) (3 children)

    That's interesting, but considering this note:

    We recommend the GameInput API for all new code, regardless of the target platform, because it provides support across all Microsoft platforms (including earlier versions of Windows) and provides superior performance versus legacy APIs.

    For games developed on the GDK for Xbox One, GameInput is the only input API

    I'm really not sure this would do what we both want it to do. If everybody has had a GameInput version of their controller support since last-gen and we're still getting limited to the XInput feature set I don't think it sorts out gyro-on-Xinput at all. I am not familiar with the behind the scenes of how modern engine controller code is handled, but this sounds like maybe it's how games with native PS controller support are doing that, but not necessarily a new standard that will allow the default XInput PC setting of new controllers to pass gyro input to games detecting them as an XInput device. I think it's more like MS's answer to Steam Input as an additional layer between the games and the hardware, regardless of what the hardware is using.

    It does show that all the tools are in place. MS has control over all the involved APIs. They could expand the Xbox controller API feature set tomorrow, whether or not they add the hardware feature to their base controller model. They just... don't. And Steam could deploy a Steam-independent Steam Input driver or software to just take over all controller support on a dedicated full-feature OS layer, but they also don't (on either Windows or Linux, as far as I can tell).

    Honestly, there are enough workarounds (add games as non-Steam games, use Switch modes and so on), I just bump against the edge cases of it often because I'm both a controller and handheld nerd, so I'm stuck with a GPD Win handheld that insists on injecting their internal gyro as mouse inputs, which confuses the hell out of half the games, along with a bunch of GameSir and Gullikit controllers that do weird things with gyro, like injecting it at the firmware level instead of passing it to the OS. And I mess around with enough emulators to also end up with "oh, this was on DI mode when I booted RetroArch, so now all my buttons are in the wrong places until I quit". It's only dumb for like ten of us... but man, is it dumb.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 11 months ago* (2 children)

    They could expand the Xbox controller API feature set tomorrow

    No, they couldn't. There's over 20 years of legacy hardware and software that expects Xinput data to be returned exactly in this format:

    typedef struct _XINPUT_GAMEPAD {
      WORD  wButtons;
      BYTE  bLeftTrigger;
      BYTE  bRightTrigger;
      SHORT sThumbLX;
      SHORT sThumbLY;
      SHORT sThumbRX;
      SHORT sThumbRY;
    } XINPUT_GAMEPAD, *PXINPUT_GAMEPAD;
    

    Changing any of that would break every single xinput controller and game made in the last 20 years. Modifications require a new API, which is exactly what GameInput is.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 11 months ago* (1 child)

    There are definitely ways to send backwards compatible data when required and separately support additional features in a new iteration of an API. This wouldn't be in the top 10 backwards compatibility challenges MS has figured out.

    But in any case, I don't care if they call it XInput2 or Game Input. I just need it to support all controller features in all games. It's a bit hard to tell whether Game Input will ever do that, but so far it seems more concerned with acting as a layer to explicitly support a bunch of different hardware, each with its own standards, than a XInput replacement for controllers. There doesn't seem to be a concept for a "Game Input controller" there at all, actually, just supported controllers you can listen for regardless of what they're sending through.

    I guess over time if they stick with it and it does end up working as a Steam Input-style intermediary layer that just recognizes anything you'd just ship controllers that match whatever format with gyro support and Game Input-enabled games would just pick them up fine more or less universally, but that doesn't seem to be what it does right now, or at least not something that either games or manufacturers are relying upon.

    Anyway, this was interesting and informative, but I think I'm good now. I definitely don't want to have a conversation formatted as an argument in which nobody is disagreeing with anybody else. Those are exhausting.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 11 months ago

    Agreed :)

    And no matter how they do it, it's clear they need to make changes; "everything is an Xbox controller and now just works" actually was pretty nice solution 20 years ago to fix the complicated mess that was PC gamepads with DirectInput, but it is very much outdated idea today.

    Thankfully it appears changes are happening that might solve the issue in the near future, and all we can really do is wait and see.

  • source
  • parent
  • [–] 8 points 11 months ago (7 children)

    The worst part is that it is incredibly difficult (impossible?) to update the controller firmware on anything other than an Xbox or a Windows PC...

  • source
  • hideshow 7 child comments
  • [+] -19 points 11 months ago (6 children)

    How inconvenient to only be able to upgrade on 95% of PC's out there.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 11 points 11 months ago (4 children)

    "The Fediverse Disliked that"

  • source
  • parent
  • hideshow 4 child comments
  • [+] -8 points 11 months ago (3 children)

    The Fediverse is a fucking fantasy world. Some real shit takes from people who live on the fringe who have convinced themselves that everyone thinks and acts like them.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 7 points 11 months ago*

    Welcome to Linux development!

    Actually, the Fediverse is ideologically predisposed to this type of thinking. The Fediverse as a concept assumes that people will forgo convenience for a more granular experience. As such, it should come as no surprise that the people you find here think that convenience should be forgone for a more granular experience, because the people who don’t think that will never use the Fediverse.

  • source
  • parent
  • [–] 9 points 11 months ago (12 children)

    I have NEVER heard of any controller before this current generation needing firmware upgrades.

    Even the launch model PS4 controller I use on my PC never asked for an update and still works fine...

  • source
  • hideshow 12 child comments
  • [–] 24 points 11 months ago (3 children)

    Even the PS3 controller received firmware updates. This isn't all that new.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 11 months ago (2 children)

    I mainly played on PS3 for years from release and that was never a thing...

    The console got plenty of updates but never the controller.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 11 months ago

    Controller updates were performed during system updates, or could be done manually from the settings iirc. I mention it because I mainly played on PS3 for years too and definitely remember updating those controllers.

    I don't think any of the updates were ever mandatory though.

  • source
  • parent
  • [–] 19 points 11 months ago (2 children)

    Have you ever used that PS4 controller on a PS4? If you did the console would definitely ask you to plug the controller in with a USB cable to update it.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 10 points 11 months ago*

    I'm almost entirely sure that PS4 and XOne controllers did get upgrades at some points. Definitely Switch 1 ones, which matters or not depending on how you split the gens. There were definitely revisions in older controllers, though. Some were labeled and had obvious new features, some were quieter. And PC-side drivers got updates all the time, obviously.

    Also, your current gen controller will also keep working indefinitely without an update. In this case Valve is annoyed about a particular dependency where THEY need the upgrade to happen for a feature compatibility thing, but the controller proper will work if you plug it in.

  • source
  • parent
  • [–] 1 point 11 months ago* (last edited 11 months ago)

    I updated my EOL'd Stadia controller to get bluetooth support and it works fine with the deck. The Luna controller also works well with the deck and has an android app that can update the firmware.

  • source
  • parent
  • [–] 4 points 11 months ago (2 children)

    Trailling off the issue here but xbox controllers sucks ass. I swear they add input delay if you use bluetooth instead their own dongle. Joysticks feel cheap and buttons are super loud and clicky. The shell is pretty decent with nice color selection and easy battery swaps but that's about it.

    Prefer the ps4 or ps5 controller which feel nice. The buttons are firm but quiet, joy sticks feel decent. Same with the switch controller but they have no analog triggers.

    Are 8bitdo controllers similar? Playstation controllers are expensive and don't have hall effect joysticks.

  • source
  • hideshow 2 child comments
  • [–] 3 points 11 months ago

    What annoys me is that previous generations of Xbox controllers had quite good build quality. The Xbox 360 controller was amazing in that regard, and the Xbox One controller was pretty decent too. The Xbox Series X controllers (and I am explicitly not excluding the "Elite" model) feel like cheap trash in comparison.

  • source
  • parent
  • [–] 26 points 11 months ago (19 children)

    I'd personally buy a new controller from anyone that isn't mucrosoft before I flash new firmware on a controller

  • source
  • hideshow 19 child comments
  • [+] 50 points 11 months ago (6 children)
  • [–] 3 points 11 months ago (4 children)

    The feature recently added to the PS5's Dualsense that allows them to pair with multiple devices was such a huge QoL change.

    Does that only apply to playstations or can you pair to multiple PCs? Might have to upgrade then.

  • source
  • parent
  • hideshow 4 child comments
  • [+] 7 points 11 months ago* (3 children)
  • [–] 1 point 11 months ago

    Agreed. Multi-pairing is such an underrated feature. It's especially great when it comes with a hardware selector (in case you've got multiple devices paired in range).

    I picked up a Logitech mouse that pairs up to 3 devices and has a button+LED's on the bottom to switch between. It's awesome

  • source
  • parent
  • [–] 24 points 11 months ago (2 children)

    Are you trying to say, "Don't buy a Xbox controller then flash it"? I can understand the decision to not do business with MS, but I assume most people already possess that controller and are trying make use of what they have.

    This is not a critique, I just don't understand what you are intending to communicate.

  • source
  • parent
  • hideshow 2 child comments
  • [+] -7 points 11 months ago (1 child)

    I assume the new ms firmware will inject copilot into the controller and make it worse. zero trust in anything microsoft

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (-1 replies)
  • [–] 12 points 11 months ago (3 children)
  • [–] 13 points 11 months ago (1 child)

    Maybe they like bugs that make their controller incompatible with other systems other than the manufacturers.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 8 points 11 months ago

    I'm often reluctant to upgrade firmware. Often because I like to tinker and upgrading firmware (now-a-days) doesn't allow downgrading. Which is kinda silly (from a technical perspective) as it "forces" you to keep chasing the next updates for hardware I own.

    If my network printer works and addresses all my needs (works on windows, apple, Linux, and Android) - I don't gain a lot by upgrading the firmware, but I do risk a lot (in terms of compatibility) if I do upgrade (with no downgrade path).

    Like wise with my controller firmware. I only update if it's something in the internet (printer doesn't count as it's firewalled off) or if something is broken/I'm not happy with the device.

  • source
  • parent
  • [–] 2 points 11 months ago (3 children)

    8bitdo is perfect. There is no reason to buy anything else these days.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 11 months ago* (2 children)

    Do they make a pad that is exactly like the upcoming Steam Controller Mk.II, except with two extra face buttons next to B & Y (like an old Sega controller)? It should also have cooling fans for my hands without sacrificing rumble (just like an old Logitech controller I had back in the day).

    Something like that is my dream controller and I've been waiting for someone to come along and make it for years. At this point I think I'm going to have to buy a 3D printer, and get in touch with someone who fabricates circuit boards, because I'm tired of waiting.

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (1 reply)
    [–] 3 points 11 months ago

    Controllers? Upgrading?

  • source
  • [–] 2 points 11 months ago

    Warning! Shoot the thing!

  • source
  • 13 comments in c/gaming@lemmy.zip view that post
    [–] 7 points 11 months ago (11 children)

    To fix these issues you must connect the controller to a Windows PC and update the firmware via the Xbox Accessories App.

    Well shit. I don't have a windows PC anymore.

    Never should've gotten an Xbox controller. Always thought they were kind of shit, but my friends insisted they were the best and most standard.

  • source
  • hideshow 11 child comments
  • [–] 3 points 11 months ago

    I always liked the xbox controllers, but mainly because they are generally bigger and i have big hands. I paid way to much for the pro controller or whatever it's called. It's hot garbage. But to he honest, other than the steam controller which i liked a lot, i wouldn't really know what to get.

  • source
  • parent
  • [–] 2 points 11 months ago (8 children)

    Have a spare computer?

    Just throw Win10 on it to update the controller. It’s what I did recently for two new controllers.

    PITA? Yes, but ehh.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 4 points 11 months ago (7 children)

    I wonder if you can do it in a VM, actually...

  • source
  • parent
  • hideshow 7 child comments
  • [–] 4 points 11 months ago (5 children)

    I tried passing the controller through to a VM, no dice. Windows would detect the controller, but the Xbox Accessories app itself that handles the updates could never detect it. After tinkering for a while on it, I just went the Win10 on spare machine route. Fast enough and worked fine.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 11 months ago (2 children)

    Unfortunately I don't have a spare windows machine, and I don't think my girlfriend's work would be happy with me installing the Xbox app on her laptop.

    Oh well. Maybe someone will find a way to update it on Linux

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 11 months ago (1 child)

    Do you have a spare machine at all? Windows install is easy, you don’t need a key for activation or anything. Just pull down the official iso from Microsoft and install Win10 Pro. Let’s you setup a local account when you select domain join machine.

    Again, it’s a pain in the ass that you have to do it all but it gets the job done.

    The linchpin of needing Windows is because Microsoft only lets you update the firmware on the controller two ways, either via a Xbox console itself or via the Xbox Accessories app via a Windows machine. There is no standalone client or web version to do it. It’s a longstanding “problem” for Linux or MacOS users who just want to use the damn controller via its BT connection.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 11 months ago (1 child)

    Just curious, did windows VM see it as a genuine Xbox controller or just a generic input device?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 11 months ago

    It’s been a few months since I worked on it but IIRC Windows VM saw it as a controller, which made it that much more confusing as to why the app wouldn’t recognize it.

    I was using QEMU/KVM on my Fedora box for the VM. It’s possible it would work using a different client such as VirtualBox or the likes. I had spent enough time on it by that point so I just went the Win10 on spare laptop route to get it done as I was sick of screwing around with it.

    The irony is I spent almost 20 years in IT supporting Windows and solving all kinds of unique issues that arose from unconventional business needs. Glad to be out of the MS world now.

  • source
  • parent
  • [–] 1 point 11 months ago

    I can't speak to xbox controllers, but I have a VM on my desktop for updating my 8bitdo controllers and de-drm'ing my kobo (formerly kindle) purchases.

    For the former, the qemu gui "redirect usb device" is sufficient.

  • source
  • parent
  • [–] 1 point 11 months ago

    Good to know. I never realized this was a downside to the Xbox controllers. Granted, I haven't run into the issue so maybe they auto-update if you connect them to a Windows machine?

    The Xbox controller isn't my favorite, but it takes AA batteries so it's nice to have an option that will work if I forget to charge and which has easily replaceable batteries since that seems to be the main point of failure for so many electronic devices these days.

  • source