• Vash63@lemmy.world
    link
    fedilink
    arrow-up
    147
    ·
    13 days ago

    It’s annoying all the articles are focusing on performance versus stock wine here when basically everyone uses Proton or a fork of it anyway, which has had fsync for years now that does similar performance uplift.

    The story here should be that we’re getting fsync level performance with fewer bug and it can be upstreamed to wine. There is no relevant performance uplift for Proton users, but I guess performance gets clicks so that’s the story all the press are going with.

    • refalo@programming.dev
      link
      fedilink
      arrow-up
      18
      ·
      13 days ago

      I can’t believe stock wine is still so bad with so many games. GTA5 is still unplayable with a keyboard, it just freezes for 5 seconds with every single keypress.

        • MentalEdge@sopuli.xyz
          link
          fedilink
          arrow-up
          10
          ·
          13 days ago

          You don’t even have to do that.

          Wine managers like Bottles make it extremely easy to slap on whatever fixes and wine variants you might need.

            • MentalEdge@sopuli.xyz
              link
              fedilink
              arrow-up
              6
              ·
              edit-2
              13 days ago

              You google the game to see if smarter people have done the investigating.

              If not, you parse logs and errors best you can and try to determine what needs enabling. If you get it working, share it on protondb.

              Generally though, enabling “everything” doesn’t come with any direct drawbacks. This is basically what bottles will do when you tell it you want to run a game, which will then allow most games to work fine.

              The latest version of GE is generally what you want, too, as wine/GE isn’t supposed to have regressions requiring the use of an older version with some games.

  • atzanteol@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    87
    arrow-down
    2
    ·
    13 days ago

    I promise I won’t go more into the tech bits meant for developers

    I truly hate authors who speak down to me.

    • steeznson@lemmy.world
      link
      fedilink
      arrow-up
      11
      ·
      12 days ago

      Often you see that in blog posts where the author themselves doesn’t fully understand the details.

      • Zozano@lemy.lol
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        1
        ·
        edit-2
        12 days ago

        “I’m healthy, I eat fruit, vegetables, etc.”

        “What’s etc.?”

        “Other things”

        “Like what?”

        “… Let’s move on.”

  • Mactan [he/him]@lemmy.ml
    link
    fedilink
    arrow-up
    43
    arrow-down
    1
    ·
    13 days ago

    article from February, anybody got benchmarks? pretty sure this is long since merged and working iirc

    • Vash63@lemmy.world
      link
      fedilink
      arrow-up
      16
      ·
      13 days ago

      It’s not merged, but the benchmarks are against upstream wine. Proton has hacks (fsync) that have almost identical performance uplift but were not suited to upstreaming.

      So basically this will improve “correctness” versus current Proton, not performance. Should fix some bugs and improve compatibility.

      Versus stock wine, it’s a huge perf uplift though.

    • pbjamm@beehaw.org
      link
      fedilink
      English
      arrow-up
      11
      ·
      13 days ago

      Only thing I can find is this OS News article saying it should be in the 6.10 kernel

      I can not find any confirmation that it is.

    • Magnolia_@lemmy.caOP
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      10
      ·
      13 days ago

      If you had read it you’d have answers to your questions.

      They are trying to merge it in 6.11 bit has to go through Greg and Torvalds himself. The benchmarks, once again, speed-reader, are on the article.

      • pbjamm@beehaw.org
        link
        fedilink
        English
        arrow-up
        13
        ·
        13 days ago

        No need to be rude.

        It seems to me that Mactan was hoping for some independent recent benchmarks.

      • Chaotic Entropy@feddit.uk
        link
        fedilink
        English
        arrow-up
        3
        ·
        13 days ago

        Presumably they wanted something a bit more thorough and clear than a table of numbers with no information besides:

        These tests were done on various hardware running games, both old and new, with and without the new driver being active.

  • Ooops@feddit.org
    link
    fedilink
    arrow-up
    28
    arrow-down
    1
    ·
    edit-2
    13 days ago

    Doing that improved performance for Windows apps on Linux when using Wine or Valve’s Proton that is based on the former. […] benchmarks that show games running better with average improvement rates ranging from 50% to 150% when using the new driver compared to not using it.

    Talking about improvements for Wine and Proton then providing no actual data for Proton (which is already using a completely different mehod for syncs - yes the basic wine method sucks) is either stupid or intentionally misleading.

    • False@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      13 days ago

      I believe this replaces esync and fsync. IIRC it’s slightly faster and has the benefit of being mainlined.

    • Sina@beehaw.org
      link
      fedilink
      arrow-up
      1
      ·
      2 days ago

      It doesn’t matter much in this case. Once ntsync is working, we all will benefit just the same. (Bottles, Lutris etc need to implement it as well)

  • kbal@fedia.io
    link
    fedilink
    arrow-up
    19
    ·
    13 days ago

    More recently, from Phoronix:

    While the initial driver patches were merged to char/misc and now in turn within Linux 6.10 Git, much of the enablement work wasn’t accepted in time. Thus for Linux 6.10 the new NTSYNC driver is marked as “broken”, so it won’t even be built for normal kernel builds.

    Hopefully for Linux 6.11 or sometime soon the rest of the NTSYNC patches are upstreamed for yielding this massive boost to Windows games on Linux.

    • kbal@fedia.io
      link
      fedilink
      arrow-up
      11
      ·
      edit-2
      13 days ago

      Support for it already seems to be there in wine, so rather than wait for 6.11 I think I’ll just go ahead and apply the patches myself to 6.10-rc7 and see if it makes any difference to the one game I regularly play. If my computer blows up as a result I’ll let y’all know.

      (Result: None. The versions of wine I have probably need patching or at least configuring in order to use it. In the course of briefly considering trying to work out how to do that, I discovered that the expected improvements are not nearly as dramatic as were suggested compared to what’s already most often done in proton (fsync). The main benefit for most of us will be better compatibility, not huge performance gains. Well at least my kernel is ready for it.)

  • morrowind@lemmy.ml
    link
    fedilink
    arrow-up
    15
    ·
    edit-2
    13 days ago

    Basically implementing windows in the Linux kernel? Something about this is really funny