this post was submitted on 03 Apr 2025
33 points (100.0% liked)

Linux Gaming

27973 readers
50 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.

That includes posts generated by LLMs. It doesn’t matter if you “don’t have the time” or “would’ve written the same anyway”, or if “everyone’s doing it geez get with the times”.

For now it’ll also include AI-assisted projects that haven't had at least two months of (public, verifiable) dev time behind them.

Resources

Help:

Launchers/Game Library Managers:

General:

Discord:

IRC:

Matrix:

Telegram:

founded 3 years ago
MODERATORS
monolalia@lemmy.world
33
Does anyone here have a solution for KDE or Wayland crashing when VRAM runs out? (feddit.nl)
submitted 2 years ago by gerryflap@feddit.nl to c/linux_gaming@lemmy.world
11 comments fedilink hide all child comments
 

My transition to full on Linux gaming mostly went okay, but recently I've started running into some issues with more demanding games. In games like Cyberpunk 2077, Stalker 2, and inZOI I sometimes get KDE and/or Wayland crashes when the VRAM runs out. In Cyberpunk I can avoid it by not enabling RTX, which is fine. But Stalker 2 and inZOI are basically all-in on raytracing and therefore seem to also fully eat up my 8GB of VRAM.

Is there any way of constraining the games to like 7.5 GB or something? Because they seem to actively work to stay below 8GB, so clearly there is still stuff they can clean up. And even if they'd go over the limit, I'd prefer the game to crash rather than basically having Wayland restart, losing everything I had open. I'm curious for you experiences

you are viewing a single comment's thread
view the rest of the comments
[–] Matty_r@programming.dev 4 points 2 years ago (2 children)

Kinda, I have this issue with Diablo 4. It might with work other games that use dxvk, but you van try creating a config file in the same directory as the executable:

"dxvk.conf" with the following lines: dxgi.maxDeviceMemory=8192 dxgi.maxSharedMemory=8192

Worth a shot.

[–] Virkkunen@fedia.io 4 points 2 years ago (1 children)

As far as I know, there's no shared memory with Nvidia on Linux so that last flag might not do anything

[–] Matty_r@programming.dev 2 points 2 years ago

Maybe, but it definitely helped keep it playable.

[–] gerryflap@feddit.nl 2 points 2 years ago* (last edited 2 years ago)

Oh yeah I found something similar just now which might work? Using DXVK_CONFIG="dxgi.maxDeviceMemory = 6144:" %command% to try and limit the game to 6GB VRAM. It hasn't crashed since, but I'm unsure whether that's because of this. I could try the other parameter as well and see if that works, though reading the comments I'm unsure about that. Worth a try

EDIT: I also found a comment on the NVIDIA forums detailing this solution. Apparently you can configure this system-wide, which would limit the VRAM on all DXVK games