I tried it a few hours after I made this post but for some reason, Gnome on Xorg kept crashing and going back to GDM as soon as I moved the cursor. By that point it was getting late and I stopped debugging. I have no idea how to debug that anyway.
Damn, I am stumped then, it works fine for me on steam.
You could try installing it in lutris perhaps? The game doesn’t have any achievements or enhancements on steam so you wouldn’t be missing out on any extra features besides possibly cloud save (though backing up wine prefixes is amazing, I copy fl studio to a flash drive to sync with my various computers).
Okay this is extremely weird. No matter which version of wine/proton I pick in Lutris, I get the exact same issue where the window doesn’t show up but the game is running. The only difference with Steam here is that I can hear the game audio.
I am almost certain this is an issue because of Wayland but I can’t seem to figure out why Gnome on Xorg keeps crashing for me.
This one is more of a bandaid than anything but have you tried using gamescope?
Also, for testing purposes you could see if you are able to run another X window manager and see if it is a problem with X rather than Wayland. dwm is very small and in the AUR, if you install that and xorg-xinit, you can jump over to a getty and create .xinitrc in your home folder with the line exec dwm and run startx. You’ll need dmenu as well to run things and that can also be found in the AUR.
I figured out why Gnome on Xorg was crashing. It was because of libinput-config. I noticed because it wouldn’t actually crash until the moment I moved the mouse. The game seems to work perfectly on Xorg.
I already tried gamescope. The results of that attempt are in my original post above.
Still, while I can finally play the game now, it’s a bit annoying having to remove a package and reboot everytime. I don’t even know if this is a Wayland issue or a Gnome issue but I don’t have the disk space to install KDE or anything.
Ideally I would like to figure out why this is happening in the first place and maybe report it upstream, but I have no clue how to even get debug logs out of this.
Sounds like that may actually be an issue with a config file somewhere. You could check the wiki on libinput and poke around the configs if you think it may be necessary to keep the package.
I axed Windows a while ago, I play exclusively on Linux with either my keyboard or a wired Xbox 1 controller. It fits my needs pretty well as I don’t play online or super recent games. Steam with wine/proton does a great job at running my games on my shitty x230.
Big thank you to all outsourced and Steam developers. Steam is the one of a few companies that most of the time actually do great things for their player base
Yeah games mostly just work, and just as well as in Windows. It’s not slow or clunky. Some games require fiddling or won’t work at all but the majority are good.
I’ve almost completely switched over at this point. The only reason I really keep Windows around anymore is because of some specific games that use incompatible anti-cheat systems (like CoD), and for VR (although, I hear the Valve Index works almost perfectly on Linux, and projects like OpenHMD are getting closer to running Oculus on Linux too)
I started dual booting Linux back when Steam for Linux was reasonably new and Portal 2’s native port was on beta. Briefly went back to Windows after building a new, much powerful system for about a year, DXVK & later on Proton happened, and now all the games I care about work flawlessly.
There have been games on my Steam library that I never ran on Windows despite them not officially supporting Linux.
With the deck I seriously hope devs slowly but surely start thinking about native ports as well, but I won’t mind waiting another - uhh, 10?! - years for that to happen. I expect Steam Linux Runtime & Flatpak to be the DXVK & Proton of native ports - as in, the thing that will make them “viable” instead of “theoretically possible”. Win32 is still the most stable ABI on Linux after all.
I’ve been playing BG3 using Proton since Patch one. It went from running alright, too absolute shit, too Amazing recently. There was a period during EA where Vulkan wasn’t working at all. Possibly because they were optimizing. As of now, I run it 1440p, max or near max settings, on a mediocre PC with Proton 8.0x. It’s a truly beautiful game, and I’ve only seen about 75% of ACT 1…
So yes, although not natively supported, it runs perfect with Proton.
I know I’m super late to this post, but I just bought a brand new gaming laptop that came with w11. Was installing games to play and installed days gone. It refused to launch. Went over to my steam deck, installed it, and it ran flawlessly.
Moral of the story, w11 is so bad that sometimes games work better on Linux! 😂
Ahh thanks this looks promising. The only thing that I don’t get from that article is where they talk about the nvidia gui settings. I’m not seeing that. Is that the same as the nvidia xserver application?
So I found the issue in case anyone comes across this. I had to switch to x11 gnome instead of wayland on the login screen in fedora 38. After that Diablo runs like butter!
Afaik it's nearly impossible. Even the Index has a lot of issues and is I think somewhat semi abandoned in favor of the Deckard and because of their internal SteamOS change towards Arch. I would expect some news & improvements with the Deckard release but right now I wouldn't recommend it.
this is what I have been dealing with on steam both Xorg and Wayland, it will launch after a really long time, wondering if this has anything to do with. Other games also work fine one steam is opened however
linux_gaming
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.