This is the third (and last) part of the Wayland driver Vulkan subseries (part 10 subseries):

  1. Implement vkQueuePresentKHRand support reporting VK_ERROR_OUT_OF_DATE_KHRand VK_ERROR_SURFACE_LOST_KHR.
  2. Misc. enhancements/fixes to ensure the subsurface containing the vulkan rendering is displayed properly.
  3. Implement a couple of remaining Vulkan functions.

With this MR you can start enjoying some of your games with the Wayland driver (either directly with Vulkan or with a D3D->Vulkan translation). Please note, however, that we don’t currently support what’s needed for mouselook (you will currently get erratic view movement), so most first-person 3D games are not playable yet.

Source: https://gitlab.winehq.org/wine/wine/-/merge_requests/4522

  • Matt_Shah@alien.topBEnglish
    1·
    10 months ago

    Nice! Is there some environment variable to activate or deactivate this in certain cases?

    BTW: Don’t listen to BlueGoliath, the self-proclaimed hero to rescue poor rich nvidia with his likewise proprietary Envious FX app. What a coincidence that he also finds objections against wayland. Grow a spine dude!

  • Aeroncastle@alien.topBEnglish
    1·
    10 months ago

    Please note, however, that we don’t currently support what’s needed for mouselook (you will currently get erratic view movement), so most first-person 3D games are not playable yet.

    Wayland always getting support for things 20 years after it should and even then with glaring issues…

    • adalte@alien.topOPBEnglish
      1·
      10 months ago

      It’s not Wayland per say, it’s the driver in Wine (winewayland.drv) that isn’t fully developed. Context really matters !

  • BlueGoliath@alien.topBEnglish
    1·
    10 months ago

    Is there actually going to be a benefit to native Wayland support or is it “just because”?

    • adalte@alien.topOPBEnglish
      1·
      10 months ago

      The most logical answer (without being technical) would be the transition between Wayland to XWayland, e.g. Gamescope. The transition has a latency, a small one but it exists.

      As /u/VastAd8540 mentions too, Nvidia proprietary drivers doesn’t support XWayland that well, so a native Wayland goes a long way for usable drivers.

      The benefits of modern technologies that Wayland is suitable for (and less so for X11 because X11 was created in an era for a different mindset, XWayland is a middle ground for a more secure X11 environment), maybe not implemented yet though…

      • bankimu@alien.topBEnglish
        1·
        10 months ago

        Would you know approximate time line for this to land for users to game natively in Wayland?

        Since the post mentions the it is the last of planned changes, guessing it would be pretty soon?

    • BujuArena@alien.topBEnglish
      1·
      10 months ago

      Yeah. Here are some fixes that I think this should bring:

      • Scaling to keep wine game window size the same on different-DPI displays
      • Drag/drop and clipboard sharing (copy-paste) to and from wayland-native windows and wine windows will work as intended
      • Easy application of window effects, like window rotation, without looking broken
      • Cross-process rendering (quote from Collabora: “A significant improvement compared to last year is support for cross-process rendering, which is required by Chromium/CEF applications. Chrome is now supported without any special flags, and is fully GPU accelerated on both OpenGL and Vulkan!”)