#linux fixes

If you've noticed Diablo 4 is crashing specifically under Wayland with an Nvidia GPU, it's likely running out of VRAM. When you run out of VRAM on Wayland, it kills the process. (It's more complicated than that, but this explanation is good enough).

Firstly, I want to mention that I'm not 100% on the effectiveness of these fixes. I don't understand DXVK and d3dvk enough to know whether these actually do anything or not. In my anecdotal experience though, they seem to help and others have reported similar results. First lets go to the Diablo IV folder with Steams UI

It'll bring you to the root Diablo IV folder. From here, right click, new, then text file.

Copy paste this into the text file, save it, and name it dxvk.conf.

[Diablo IV.exe] dxgi.maxDeviceMemory = 2048 dxgi.maxSharedMemory = 2048 dxvk.maxChunkSize = 4

By default, this is set to 2 gigabytes, but you'll want to change it to what's right for your system. So if you've got say, 7 gigs of vram, I'd probably set it to 5. Remember that the game isn't the only thing using VRAM, so don't set it to max. The memory chunk setting should be left at 4. To be completely honest, I'm not really sure what this does, but it seemed to help. The memory settings above it get ignored by Diablo IV (on my setup, at least) so I'd try the memory chunk to see if it helps at all.

This one is a somewhat specific fix, but I think it could apply to other games as well. I was having an issue where for some reason, whenever I would alt tab out of DW8E, the game would stop visually refreshing. I specify visually, because the sound was clearly still playing and I could hear myself pressing buttons in the game.

Before we get into it, I want to link to where I found the command for this which is here. Important to note this is better than the usual way of launching gamescope and connecting it, because this command does it all in one.

If this sounds similar to your issue, we can try fixing it using gamescope. I'm also assuming you are using steam. The fix is pretty simple. First we need to install gamescope. I'm on a Fedora based system, so for me the command for this is:

Sudo dnf install gamescope

If you're debian based, like Linux Mint, Pop OS, or Ubuntu, it'll be:

Sudo apt install gamescope

If you already have it installed, no worries, it just won't do anything besides tell you it's already installed. First of all, we need to figure out which display number gamescope is going to launch on. Press control + alt + t, or open a terminal window however you see fit, and type

gamescope

Scroll down, and eventually you'll see a line that looks like this:

This means my display is 1, but it might be different for you.

Now go back to steam, right click and click properties.

It'll open this window. Click on the launch options box below it, and paste in this:

gamescope --force-grab-cursor --backend sdl -H 1080 & DISPLAY=:1 gamemoderun %command%

A couple things to note here. For one, the number for DISPLAY=:1 needs to match the number we got earlier, which for me was 1. Also, the value to the right of -H is your monitors resolution, so you might need to change that depending on what you have. Otherwise, the game will now launch using gamescope, and you'll notice that tabbing out doesn't even make it minimize in fullscreen! Not only is this way less annoying, but it prevents the bug from happening because there is no minimization.

Okay so first things first we're gonna wanna open up our settings.

Then go up to the top left search bar, and type keybinding, above quick settings.

Then click on shortcuts. It should be the only thing that appears.

Then, type fullscreen into the search bar.

From there, click add (or it may say none) and press the key you want to toggle full screen.

This one had me stumped for awhile! First off, ask yourself if you're using a Nintendo controller, and if so, if you've installed joycond. If you have, we'll need to stop it and remove it.

This will stop the joycond daemon. If you don't have the joycond daemon installed, the terminal will tell you this:

In which case, you might just need to restart, or you can jump to the part where we use lutris to run Warframe instead.

But for now, lets remove that daemon from our PC.

First type:

Then:

And then do the same thing again, but replace 72 with 89.

After that, type these two commands in succession.

Then type these two commands:

Then reboot. Essentially what we're doing here is manually removing any joycond daemon files, manually. Technically we only need to remove the service file, but its good to clean it all out.

Now if it still doesn't work, we can run Warframe using Lutris. First, launch lutris, then click the plus on the top right.

Click search Lutris website for installers

Then type warframe and run through the install process. After you launch warframe for the first time, click the gear icon on the top right, and make sure your settings look like this:

This will result in the updater saying "Downloading updates..." with no progress (as seen in the screenshot) but it is downloading the game. It should work as is, but I personally recommend using wineGE instead of the default wine given by Lutris. To do this, download it using this link:

Then, navigate to /home/<your_username>/.local/share/lutris/runners/wine/ with your distributions file browser. After that, extract the downloaded wineGE into this folder. Restart lutris, right click warframe and go into configuration, runner options, then select wineGE from the dropdown.

Most likely if you're unable to connect online, it's due to time sync issues. This an issue on Windows as well as Linux, and I've experienced this annoyance on both. To fix this, we need to sync our clock.

First, open a command prompt.

Type in "timedatectl"

Timedatectl will most likely show this:

In this case we need to enable ntp. To do this, simply type in "sudo timedatectl set-ntp true"

We also may need to install ntp if on arch, in which case type "pacman -S ntp"

And after restarting the game, it should connect just fine. I hope this helps!

Sources:

I wanted to put all the random fixes I've learned over my time on desktop Linux into one place. That's basically it! To start off here's one of my own videos:

This first one is probably out of date, but I'll leave it up here anyway. This video explains how to install mods on beat saber on Linux. As a said, it's probably out of date but I'll put it here anyway, just in case.

Linux, the free and open source operating system, it comes in many distributions. From Red Hat to Yellow Dog. From Arch to Suse.

However, if there is one enemy of this great operating system is is the Intel Corporation, which for some reason whenever you put your screen to sleep part of the memory that is allocated to process graphics, espeically with on-board Intel Graphics with the i3, i5, and i7 series of processors is lost in a memory leak every time the screen turns off.

The problem: Everytime your screen turns back on, the processor thinks that that’s a new monitor, so it allocates another piece of memory used with that first monitor (which is really the same monitor as before) to that second monitor.

After a while of switching off and on, the graphics memory runs out.  And instead of running your box for a few weeks, you run out of memory in a few hours.