• Dyskolos@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      1 day ago

      “Require” isn’t right OFC. But why would i buy one and use third party stuff that may or may not work with all features of a product?

        • shalafi@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          21 hours ago

          Probably the unifying software (runs multiple peripherals on one dongle) or the solar app (kinda neat, not needed).

        • Dyskolos@lemmy.zip
          link
          fedilink
          English
          arrow-up
          2
          ·
          23 hours ago

          I know what you want to tell me. But I buy product x, y and z and want to use one singular controlling software to, well, control them…

      • Kairos@lemmy.today
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        1 day ago

        That does not require a proprietary driver. Controller interfaces have been standardized for the last decade.

        • Harry@lemmy.world
          link
          fedilink
          English
          arrow-up
          9
          ·
          edit-2
          1 day ago

          For controller sure, but bear in mind if you’re looking at something like a wheel with force feedback, and pedals with pressure sensitive response, that changes more than just button presses

          Edit: to be clear I’m not defending the shit in this article in question. Just that some of the stuff they do may actually need a driver. But not everything…