this post was submitted on 20 May 2025
72 points (98.6% liked)

Linux Gaming

18722 readers
390 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

No memes/shitposts/low-effort posts, please.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
monolalia@lemmy.world
72
GE-Proton10-3 Released (github.com)
submitted 1 week ago by CannonGoBoom@lemmy.world to c/linux_gaming@lemmy.world
9 comments fedilink hide all child comments
 

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).

you are viewing a single comment's thread
view the rest of the comments
[–] felsiq@lemmy.zip 1 points 1 week ago (1 children)

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

[–] FauxLiving@lemmy.world 2 points 1 week ago (1 children)

nvidia-open 570.144-5

[–] felsiq@lemmy.zip 1 points 1 week ago (1 children)

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

[–] FauxLiving@lemmy.world 2 points 1 week 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).