Comment on Latest Steam Deck update will warn you if an Xbox controller needs upgrading

• MudMan@fedia.io ⁨3⁩ ⁨weeks⁩ ago

  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 mode 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.

  It does show that all the tools are in place. MS has control over all the involved APIs. They could expand the Xbox controller feature set tomorrow, whether or not they add the 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, 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

  • JohnEdwa@sopuli.xyz ⁨3⁩ ⁨weeks⁩ ago

    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.

    source

    • MudMan@fedia.io ⁨3⁩ ⁨weeks⁩ ago

      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

      • JohnEdwa@sopuli.xyz ⁨3⁩ ⁨weeks⁩ 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