• Added ntsync support:

Enable with PROTON_USE_NTSYNC=1

NOTES:

  1. Your kernel must be patched with ntsync patches. If your system does not have /dev/ntsync then your kernel does not have the patches required to use ntsync.

  2. Some applications, mostly 32 bit, may also need PROTON_USE_WOW64=1 when using ntsync

  • Added FSR4 upgrade support via PROTON_FSR4_UPGRADE=1 (auto upgrades from amd directly https://download.amd.com/dir/bin/amdxcffx64.dll)

  • Added fixes from upstream for flicker/rendering issue when using wine-wayland

  • Refactored a lot of the patches section and cleaned up outdated or merged patches

  • Update wine-wayland patches

  • Updated wine to latest bleeding edge

  • Updated dxvk to latest git

  • Updated vkd3d-proton to latest git

  • Imported all upstream proton changes

  • protonfixes: added a fix for winetricks wget gnutls failing inside fex

  • protonfixes: add fix for sifu freeze (thanks UsernamesAreNotMyThing)

  • Malix@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    1 month ago

    ooh, nice. finally some ntsync support starts showing up. I’m not expecting miracles, but in general it still should (?) be better than existing e/f-sync thingies in general?

    edit: probably depending on the application/game, but still. Nice to see things moving forwards.

    • bargu@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 month ago

      I did a very quick and dirty test here and it appears to be still slower than fsync by about 10 ~ 12%, I’ll test it better later.

      • Malix@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        hmhm, seems like some games don’t even start with NTSYNC on. I had heard that Cyberpunk specifically gets pretty nice performance boost, but I can’t even get it to start. Oh well.

          • Malix@sopuli.xyz
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 month ago

            heh, I was just watching it, saw your post about it. Thanks for making this!

            The differences seem pretty minimal, although occasionally the frametime graph looks a bit less bumpy on ntsync side, but that’s about it. Even if the avg, 1% and so framerates are tad lower.

  • vividspecter@aussie.zone
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 month ago

    Your kernel must be patched with ntsync patches. If your system does not have /dev/ntsync then your kernel does not have the patches required to use ntsync.

    It might also be compiled as a module, but not loaded by default.

    sudo modprobe ntsync can be used to test this.