Upstream:

  • update wine to bleeding-edge (fixes battle.net broken updates)

  • update dxvk to latest git

  • update vkd3d-proton to latest git

  • update dxvk-nvapi to latest git

  • update vkd3d to latest git

  • import upstream proton game fixes

Patches:

  • proton: preserve drive letter for different mount points #129 (thanks loathingKernel)

  • wine: add fix for Vanguard: Saga of Heroes (thanks loisgomez) – triggered with SteamGameId=218210

Protonfixes:

Add directplay for Total Annihilation (https://github.com/Open-Wine-Components/umu-protonfixes/pull/196[)](https://github.com/Open-Wine-Components/umu-protonfixes/commit/2abbeb508355d1739f9b83bf7178609e8ade1885)

  • mox@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    20
    ·
    18 hours ago

    update wine to bleeding-edge (fixes battle.net broken updates)

    I wish GloriousEggroll didn’t keep discussions and other details of this project locked away behind Discord ToS. It would be nice to know what commit fixes a problem like this one, even if it was an upstream commit.

      • A_Random_Idiot@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        4 hours ago

        Exactly.

        Discord isnt a support platform.

        Its not a development/project management platform

        its not a customer service platform.

        Everything you post to discord is hidden away from the greater internet. Its not indexed, archived, or searchable. and its really hurting a lot of projects as time goes on and more technical support information is segregated behind discord and not findable to the average person…

  • Codilingus@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    ·
    20 hours ago
    • update wine to bleeding-edge (fixes battle.net broken updates)

    Just in time for me to have struggled with this just 5 hours ago, but I managed to fix it and I’m not sure how.