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.
WoW server emulators have been in development for over a decade, they’re public projects on GitHub and released under opensource licenses, all private servers use those emulators, none of them has original code, it’s never been stolen.
You can compile them for Linux (as well as Windows), how well they work depends on the version, up to WoTLK they’re fine, from Cata on they’re quite bad.
You will need the original clients that are Windows only but they work flawlessly with WINE.
If you never played WoW before, I suggest you play the official one before dabbling with emulators/private servers, it’s a much better experience if you know nothing about the game.
WoW client is not native on Linux but it runs flawlessly regardless, always have, it’s also very easy to install with Lutris: lutris.net/games/world-of-warcraft/, use the battle.net script and follow instructions to install dependencies first.
I’ve played WoW classic on Linux without any real issues. The easiest way imo is through Lutris.
Install Lutris (should be in most distro repos)
Add game, choose battle.net
Let it install, launch, and login to battle.net
Install WoW classic from inside battle.net
Be sure to note where Lutris is installing your games (it’s configurable), so that if you decide to use add-ons you’ll know where to put them. I used WowUp, specifically the CurseForge version to manage my add-ons.
WoW itself runs pretty much flawlessly. I may have made some VK3D tweaks, but I’m not home and can’t check my notes. Let me know if you run in to any problems.
So if it would require kernel module how the heck would they do for snap/flatpak users would it ask everytime for root password at launch? They didn’t said anything other than it will be supported.
Looking through their Discord it seems there hasn’t been any details yet regarding how this is going to work if this indeed is real. I highly doubt Faceit would want to vastly weaken their effectiveness on Linux in the same way EAC and Battleye do by running it as a user process. Even if just speculation, that would mean a kernel module that would need secure boot enabled (though even that is not required for the windows variant in battlebit) with a signed kernel and so on and would only work for specific distros?
From the statement above and other comments, it’s a new FaceIt product sometimes described as “lite”, which gives me the impression it is a Usermode anti-cheat.
Yeah, looking at the weekly recap stream where they actually talked about it, it is indeed a new anti cheat like you mention that (according to their own statement) is still more effective than “what they have now” (that being eac). youtu.be/nIay2Aq2ars?t=702Apparently they want to do a stream again with the team from Faceit talking about it in more detail.
I’ve spent quite a lot of time trying to get The Hell mods running on Linux. Finally today I managed it. I wrote up some instructions (below) and provided the special Wine prefix were required to get the game running. Please let me know if you have any issues or have suggestions for improvement!
It was very difficult to find a way to run this on Linux - so I wrote this guide to help others who I know have also beat their heads against the table. The trick which finally allowed me to run it was I lucked into building a Wine prefix which is apparently crucially important to running the game. I have no idea what makes this Wine prefix special, but I’ve tested it on four computers (Ubuntu 20.04, 22.04, & Pop!OS) and it works on them all.
Downloads
You need the following four files
The mod: TH3_vx.xxxx.zip, and music pack: TH3_music_vx.x.zip
Available on the game CD-ROM, a copy from GOG, etc.
Wine setup and install
We’ll create the Wine prefix, install The Hell into that prefix, and then set up Lutris to point to it. This guide will create the prefix at ~/Games/diablo-the-hell, but you can put it elsewhere if you like.
Unpack the wine prefix file diablo-the-hell-wine-prefix.tar.xz to ~/Games/diablo-the-hell
Create a Windows folder for the game. You can use the UI or the terminal: mkdir ~/Games/diablo-the-hell/drive_c/Program Files/diablo-the-hell/
Unzip the mod file TH3_vx.xxxx.zip to ~/Games/diablo-the-hell/drive_c/Program Files/diablo-the-hell/
Unzip the music file TH3_music_vx.x.zip to ~/Games/diablo-the-hell/drive_c/Program Files/diablo-the-hell/
Copy diabdat.mpq to ~/Games/diablo-the-hell/drive_c/Program Files/diablo-the-hell/
Open ~/Games/diablo-the-hell/drive_c/Program Files/diablo-the-hell/config.ini and make the following changes:
set DDraw onVery important!!
set fps 60 Limits frames per second (optional)
set startvideo off Skips opening cinematic on startup (optional)
set screenwidth 1920 Sets resolution width (optional)
set screenheight 1080 Sets resolution height (optional)
Lutris config
Press + to add a new game, and set the following:
Name: "Diablo - The Hell"
Runner: Wine
Click Game Options, set the following:
Executable: ~/Games/diablo-the-hell/drive_c/Program Files/diablo-the-hell/TH2.exe (for The Hell 2), or ~/Games/diablo-the-hell/drive_c/Program Files/diablo-the-hell/TH3.exe (for The Hell 3)
Wine prefix: ~/Games/diablo-the-hell/
Click Save
Optional, if the game art doesn’t auto-populate:
Right Click on “Diablo - The Hell” -> Configure
Next to “Identifier” click Change
Change text to "diablo"
Click Apply -> Save
Click Lutris under “Sources” on the left -> Community Installers
Search for “diablo”, and wait for results to populate (the search downloads the art)
Exit the community installer section
Final thoughts
Important note on running the game: the opening UI menu has a visual bug But with the mouse & arrow keys (& some patience) you can navigate the menus to create a character. Once through the initial screens the game runs perfectly fine.
The special Wine prefix was built using Bottles, however Bottles is not required to run the game (these instructions use Lutris). If anyone can learn what is special about this prefix which makes the game work please let me know!
Despite what I’ve read online this mod works fine with DXVK. I don’t recommend disabling DXVK in Lutris when running the mod (contrary to what others have).
In case anyone asks: the specific Wine version doesn’t seem to matter. I had success with: lutris-GE-Proton8-8, lutris-7.2-2, and soda-7.0-4
Well tried upgrading to n38 last night, now it’s not booting up all the way. I followed the guide on Nobara’s website.
Currently stuck at “Failed to start systemctl-user db.service”
I can do an ALT + F3 and it takes me to the terminal where I can log in just fine but that’s about all I can do. No GUI, No KDE. Did I search on Google and Nobara’s discord but nothing useful. Would really rather not have to reinstall clean. Any ideas?
It’s starting to sound like I need to reinstall the OS.
Shouldn’t have dnf groupinstall “KDE Plasma Workspace” installed everything I needed if the DE was corrupted or deleted during upgrade? Do I need to run any other commands?
My best guess would have been that they mean Ubuntu, since thats what companies usually use in tutorials/develop for. But since they also want to include the steam deck, they must also mean arch. With Arch and Debian (probably) covered, im not too worried about compatibility.
To me it sounds like that will mean most of them, they just don’t want to commit to saying all because there will always be another distro they missed.
Almost certainly means they will only actively support one distro. But of course, all distros can run the same software, it just may need to be packaged manually by distro maintainers. Most proprietary software only officially supports Ubuntu. Even Steam only officially supports Ubuntu outside of SteamOS.
@zbecker@toallpointswest@Hextic@atmur i was surprised how well Factorio plays on the steam deck at end game. Really didn't think proton would handle it
But a lot time they weren’t good native ports, at least for AAA games. A lot of the time they slapped a translation layer on the Windows version, so it may end up running better in Proton.
For me this even smells like “kernel module that has to be loaded”. I highly doubt this is even worth trying. There are already only a few Linux gamers. How many of them will switch distribution just for a game?
edit: I’m going to try it next week. I wanted to play modded fallout and tried a different script to make MO2 open when you launch fallout but this looks better.
It does work, but buggy though. For now, I’ve opted to using the VM with a gpu passed through so I can easily install collections.
Once I have the game the way I want it, I might move it over and see if I can get it running on my host OS, and import the vortex config to keep my mods up to date.
Oh interesting. Thanks for the reply. Maybe I’ll end up doing that too. I got fallout tale of two wastelands installed on Linux with some script to make mod organizer 2 launch when you launch the game but it randomly stopped working
linux_gaming
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.