I have just watched this video and in it 2 things are said that made my Linux newbie heart sink:

• Debian 13 is not going to get the latest versions of Nvidia drivers and there are better distros for us.
• Debian in general is not meant to run on the latest hardware.

I am on a regularly upgraded desktop tower gaming PC and currently I have an Nvidia card and an Intel CPU (which, I know, even just because of the mobo chipset is not a great choice).

In this conditions and wanting to invest even more in gaming and new hardware in the future, what should I run on, instead of LMDE 6?

Follow-up video to https://lemmy.world/post/32690521

Spoiler alert: the main reason he says the experience "hasn't been great" is because shortly before posting the video his Linux install mysteriously broke and he had no idea why. Therefore, he recommended dual-booting Windows just in case.

Cue sea of comments explaining that the reason for the error he was getting was that Windows screwed up his bootloader (i.e. the problem was caused by dual-booting to begin with, LOL).

Hotfix:

• Fixed video playback in Ghostwire Tokyo

• Fixed video playback in Castlevania Dominus Collection

• Possibly other games fixed that use webm/vp8/vp9 video

Starting about a month ago, I started getting lots of crackling audio in games. Not sure what the issue is. It tends to be with loud noises, almost sounds like clipping.

Anyone else had this?

Edit: Fixed by installing realtime-privileges (arch) and adding my user to the realtime group

I recently saw the game called "Bongo Cat" on Steam which monitors yours keystrokes and accordingly plays the bongo drums. I saw that it was not working properly on Wayland because it does not allow the game to record keystrokes from other apps.

This got me thinking; how does ~~Steam~~ Valve protect us from malware? I was searching for "steam games malware" on DDG and found out that there were a few incidents regarding this. I understand that Steam probably has a robust mechanism for understanding game behavior but it's kind of a black-box for us.

Is there any independent vulnerability checker for games? How paranoid should one be before downloading games from steam?

PS: I know that as Linux users, most attack vectors don't work for us but it's good to be aware just in case.

Edit: I need to clarify. I know Steam is just a game-launcher, it's not supposed to protect the user after the game is installed. I meant to say how does Valve protect the user from malicious games? Is their mechanism known?

Id like to hear thoughts. Of course us gamers hate kernel level anti cheat, but is that actually tied to secureboot?

I know some/most distros can boot in secure mode, so it doesn't seem like an issue there.

With all the new games moving to it, looks like we will all have to sit them out or install Spyware (microshit) to play. I will opt not to.

• Fixed videos having wrong audio language in Back 4 Blood

• Fixed Devil May Cry HD collection wmv playback not working when proton wine compiled with ffmpeg

• Fixed video playback in Injustice 2

• Possible other video playback regressions fixed that happened since proton 9->10 update.

• farlight 84 patch added (yes, another one)

• patch added that may give minor CPU performance improvement (https://github.com/Etaash-mathamsetty/wine-valve/commit/6559c43fe15e55749aa1f39df98e97c24835b012)

• patch added that may help with denuvo being triggered when changing proton versions (https://github.com/Etaash-mathamsetty/wine-valve/commit/cd3efb2ade393776b40a5731eb8a81dec46e8b30)

• protonfixes proton script import location moved to beginning of the protron script, should fix a bug with dll overrides not working properly (it was affecting things such as winetricks dotnet installs)

• protonfixes added for EGS and standalone versions of guild wars 2 (thanks tvgold42)

• protonfix added for EGS version of MudRunner (thanks loathingKernel)

• wine updated to latest bleeding edge

• vkd3d-proton updated to latest git

• dxvk updated to latest git

• build and proton changes imported from upstream

I have been able to run games whether it was Steam, GOG, or itch and now I can't get shit to run. I don't have the worst rig. I was playing Fo4, and now suddenly I can't. I switched from a shitty Windows to Garuda. That was working wonderful, until I suddenly couldn't get it to work no matter what Proton version. Then I switched to Ubuntu, same issue. Then Cachy, then back to Ubuntu, and now back at it again with Garuda. Still. The. Same. Fucking. Problem. I have scoured the net for answers and fixes to no avail and I feel like driving into traffic. I cannot get any Proton version to run ANY GAME at this point, not just the more intensive ones. What the fuck do I do? Here are some specs:

• Processor: 8 x Intel Core i7-2600 CPU @ 3.40Ghz
• Mem: 32 GiB RAM
• Graphics Processor: Quadro K620
• Dell Optiplex 990 (7010 housing)
• 245GB SSD, with additional 500GB HDD and 4TB external drive

I have been able to seamlessly play all kinds of games for months, and then it just up and doesn't let me anymore. I haven't done anything to tweak shit out of whack. No matter how many clean installs and following instructions otherwise, this shit feels BROKEN and I'm LOSING IT. Someone help me please.

-Little extra info, I always skip the Vulkan shaders bullshit and it was fine before. Sometimes it'd load with the "Downloading Windows (somethingsomething), but I don't get that anymore, and as soon as I skip the thing crashes before any launchers of sorts can load so I can mess with configuration with the little GUI bullshit before total launch.

• UPDATE:

I have switched to Bazzite and have set my external drive to ext4. Shit seems to work seamlessly now. Thank you all very much.

I just got my system all set up and using KDE Neon distro. I got Steam installed and been playing a few games that work fantastically.

My biggest issue is that the shaders take a very long time.

So far I’ve played Ghost Recon Wildlands and Ready or Not and both took longer than the download of the game. Like 30 minutes.

I was okay with this as a first time setup sort of thing, but it seems it did this on first two starts of the game. On the third time opening Ghost Recon Wildlands, I didn’t see this again.

But my question is, is there any way I can speed this up and is this normal to take this long? I remember shaders taking a minute on Windows too on this same machine, but never this long. At most, 10 minutes, but never more than that.

My setup:

• KDE Neon User Edition
• AMD Ryzen 5 5600
• PNY RTX 4080 Super
• 64GB DDR4 RAM
• 2TB Samsung 860 Evo SSD

I dual boot with win 11, I do so for programming purposes, not gaming. I read online that the game straight up blocks Linux on all fronts (typical EA). So, I booted into win 11 and launched the beta. It still refused to start and complained that secure boot was "disabled". Booted into BIOS and it was enabled, but not active. I had to reset the keys to the windows default keys to be able to play this game. This is a no go for me. Not giving them my money until they stop this bullshit. Just wanted to let everyone know the situation so far.

OC text by @DonutsRMeh@lemmy.world

For some reason this took me a lot longer to figure out than it should. I have a bunch of games on GOG which only support an Xbox style controller, but I really like my DualSense 5. I searched online, but found that people were mainly sticking to using steam. For some reason when I played my GOG games via steam it still didn't work.

I then remembered that AntiMicroX exists and is included in the repositories of most distos/flatpak. So that's how I made my PS5 controller work like an Xbox controller on linux 👌

So far I've tested this with Kingdom Come Deliverance and Mirror's Edge