• Nico198X
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    7 days ago

    with KDE and Wayland i have no issues, using Steam launch parameters:

    PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1

    Linux 6.18
    AMD Radeon 9070XT
    Mesa 25

    • RipLemmDotEE@lemmy.today
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 days ago

      This is exactly what I do on Garuda Arch with KDE and Wayland.

      I usually use the latest GE Proton 10-x for games with HDR.

    • jalkasieni@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 days ago

      Doesn’t this require you to also be on plasma 6.4?

      Using proton wayland also breaks steam input, which can be deal breaker.

      • Nico198X
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 days ago

        maybe. i’m on plasma 6.5 and usually on latest.

        i can’t speak to steam input, but i’ve not had any controller issues with my 8bitdo and Gulikit.

        • FauxLiving@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          ·
          7 days ago

          It isn’t a controller issue. That still works through SDL.

          Steam Input uses the Steam overlay, it takes your controller input and allows for more custom remapping options, macros, etcetc. I primarily see it being used to let people use a controller to play games that were not designed to play with a controller (by remapping the controller to move the mouse cursor and send keyboard inputs with the controller buttons)

          I use Wayland and my xbox controllers work fine. I’d use Steam Input if I could, but most games are already designed to accept controller input directly so the damage is limited.