Release GE-Proton10-3 Released · GloriousEggroll/proton-ge-custom
github.com
Hotfix release: added envvar needed for winewayland patch fixes to work (automatically set when PROTON_ENABLE_WAYLAND is set) added patch so that PROTON_ENABLE/DISABLE_HIDRAW works as expected. I...

Hotfix release:

added envvar needed for winewayland patch fixes to work (automatically set when PROTON_ENABLE_WAYLAND is set)

added patch so that PROTON_ENABLE/DISABLE_HIDRAW works as expected.

Important note: PLEASE do NOT manually set DISPLAY= when trying to enable winewayland. ALL that is needed is PROTON_ENABLE_WAYLAND=1. When you manually disable DISPLAY= it can break many applications that need to render natively, in particular things like launchers or things that need to render with OpenGL or Vulkan directly. (not via dxvk/vkd3d).

      • felsiq@lemmy.zipEnglish
        2·
        12 days ago

        On gamescope or another compositor? I’m trying to run it on plasma and having no luck on any version
        Edit: should also mention it starts, it just freezes usually during the load screen and only occasionally makes it to the main menu

        • FauxLiving@lemmy.worldEnglish
          2·
          12 days ago

          I’m using KDE Plasma 6.3, not using gamescope.

          Using:

          PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command% --skip-launcher --vulkan

          • felsiq@lemmy.zipEnglish
            1·
            12 days ago

            Damn yeah exact same args I’ve been using, with no luck. Are you running amd or nvidia?

              • felsiq@lemmy.zipEnglish
                1·
                12 days ago

                Okay exact same versions of everything, this’ll be interesting to try to troubleshoot lol
                Thanks for giving me hope on this!

                • FauxLiving@lemmy.worldEnglish
                  2·
                  12 days ago

                  The first time or two that I launched it, it crashed. And it also took a long time sitting at a blank screen (compiling shaders or something, I’m guessing) and then it showed the menu.

                  To start troubleshooting, open a terminal window and run steam-d. It may include some errors around the time of the crash that you can search for on github, it’s possible that other users have experienced and reported the issue. You can also set PROTON_LOG=1 to enable proton logging, it’ll saved in ~/steam-*.log (where * is the AppID).