• thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    23
    ·
    29 days ago

    Anyone know how the Wayland driver in WINE will impact? I mean Wine works on XWayland so far, so what can we expect to get better with native Wayland support? I’ve searched a bit in web, but its hard to find some definitive answers (lots of general WINE and Wayland topics, often outdated).

    • exu@feditown.com
      link
      fedilink
      English
      arrow-up
      28
      ·
      29 days ago

      From my testing of the Wayland backend when it was still hidden behind a registry setting, it’s mainly for DPI awareness. For example, I use a 1440p screen with 1.25 scaling. Currently Wine through Xorg therefor sees my desktop as 1152p high. With the Wayland driver it would still correctly identify as using a 1440p screen.

      • Bogasse
        link
        fedilink
        arrow-up
        3
        ·
        28 days ago

        I’ve been using the unstable branch for this exact reason. Otherwise I’d have to change my scaling every time I launch a game.

      • Domi@lemmy.secnd.me
        link
        fedilink
        arrow-up
        3
        ·
        29 days ago

        Do you happen to know if you still need the HDR layer when using Wayland directly? I know gamescope didn’t require it for a while now but I never saw anything about it for Wine.

  • jokro@feddit.org
    link
    fedilink
    arrow-up
    7
    ·
    28 days ago

    Wow, i would’ve expected it to take longer.

    I wonder how quick Valve will switch to it on the Steam Deck

    • hallettj@leminal.space
      link
      fedilink
      English
      arrow-up
      3
      ·
      28 days ago

      I’m wondering if Wayland support in Wine will encourage Valve to support Wayland in the Steam app too.

      On my desktop I run a Wayland window manager that doesn’t implement XWayland so I can’t run Steam directly. So I’ve been running it in Gamescope in big picture mode - which is actually exactly what the Steam Deck does.