• ExperiencedWinter@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    1 day ago

    Just build one yourself if it’s so easy… I’m sure you won’t run into any problems mapping the gyro, touchpad, or additional buttons to an xinput controller, it’s super easy right?

    • potustheplant@feddit.nl
      link
      fedilink
      arrow-up
      1
      ·
      1 day ago

      What an absolutely absurd non-argument. How can someone with no access to their codebase extract the bit of steam that makes the controller work? I’m not going to spend $100 on a controller amd then do Valve’s work for them.

      Valve made the controller and they did add support for their controller inside steam. Just extract the controller compatibility layer and make it standalone. Don’t force people to use steam. It’s not a wild thing to ask. I also never said they should use xinput.

      Stop defending rich corporations, it’s lame.

      • ExperiencedWinter@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        23 hours ago

        My point was there is no standard input library that the controller would map to without losing functionality.

        It’s not like valve told everyone who wants to play non steam games to fuck off, they built a way for you to launch non steam games through steam then the controller will work.

        • potustheplant@feddit.nl
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          8 hours ago

          If the controller can work through steam then it can work through a stripped down version of steam that does not have the store, library, community, etc features. That’s what I’m asking. A program that can work as a compatibility layer and does not require you to log in to anything or give your data to valve in any way.

          Yes, steam does give you a workaround. A workaround that involves giving them user data.