• ashx64@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      25 days ago

      Unfortunate. Though I did find out that Minecraft can use Wayland natively, if you block its access to the X11 socket or don’t have Xwayland installed.

      • SmoochyPit@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        24 days ago

        I read in the comments of your previous snapshot post that the Wayland default had some issues with cursor theming… perhaps that’s why it’s reverted? Odd either way.

        • Chloé 🥕@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          5
          ·
          24 days ago

          tbh, i think it’s a fair decision on their part. it wasn’t just cursor theming, but also the cursor didn’t center properly, key combinations like CTRL-C would instead just type “c” (a big problem when you have text selected), and worst of all, the game straight up wouldn’t boot on nvidia graphics cards apparently. if you scroll to the end of this snapshot’s changelog, you’ll see they fixed a bunch of issues with Wayland. and rolling back support is their fix.

          and it’s fair enough, imo. when you consider that fixing all these bugs just requires you to downgrade the LWJGL version (which seems to be what they did), that XWayland is what is expected since it’s been the behavior all this time and the vast majority of other games use it, that it’s possible for players (using mods and third-party launchers) to reenable Wayland support, and that most of these Wayland-only issues are problems with LWJGL/GLFW and not minecraft…

          yea. i can see why they did that.

          still, i hope we get official Wayland support back in someday.