submitted by /u/TheQuantumZero
[link] [comments]

If I manually download and add a mod, it will just stick on the installation process and not let me install any more mods. It seems like it's completely at random and I need a single dependency for a mod I want to install but it refuses to. any suggestions?

submitted by /u/Salt-Cup9788
[link] [comments]

I would say its a draw

submitted by /u/RoniSteam
[link] [comments]

my gpu doesnt support vulkan rendering mode (sober is using it) so my cpu doing gpu's job.Can i change the rendering mode?

submitted by /u/Amazing-Angle-5740
[link] [comments]

does anybody know how to play the finals? i installed it but it doesnt launch. i change proton and nothing happens

submitted by /u/Dismal-Investment-56
[link] [comments]

Did anyone see the steam page for iracing arcade. It's minimum spec include "LCD steamdeck". I think this is a pretty big win for racing game fans

submitted by /u/afreakineggo
[link] [comments]

It is version 1.4.1 (Appimage x86_64)

submitted by /u/shawn_blackk
[link] [comments]

Hey folks,

With Linux gaming on the rise (thanks to Steam Deck and Proton), there’s still one big wall keeping us from full parity with Windows: anti-cheat support.

Right now, every anti-cheat vendor (EAC, BattlEye, Vanguard, etc.) has to hack together their own fragile Linux solutions. Because Linux has so many kernels and distros, devs often just say “no Linux support” instead of dealing with the mess. That’s why games like Fortnite and Destiny 2 won’t launch.

The Idea: A Standardized Anti-Cheat Runtime

Instead of waiting for every vendor to reinvent the wheel, what if Linux had a runtime layer — like Vulkan or Proton — that all anti-cheat systems could plug into?

• Installable layer: Ship it as Flatpak, Snap, DEB, RPM, AppImage, etc. Gamers install it once, it works everywhere.
• Stable API: Games talk to the runtime, not directly to the kernel.
• Kernel-agnostic: Handles the differences between Ubuntu, Arch, Fedora, etc. under the hood.
• Secure: Signed, verified updates so it can’t be tampered with.

Why This Matters

• For devs: No more “does it work on Linux?” headaches. If you support the runtime, you support Linux.
• For anti-cheat vendors: Lower cost, fewer exploits.
• For gamers: More multiplayer titles unlocked.
• For Linux itself: SteamOS could act as a baseline, while still letting distros stay diverse.

Next Steps

• Start a discussion between Valve, Proton/Wine devs, distro maintainers, and maybe even anti-cheat vendors.
• Sketch out what the API/runtime would look like.
• Treat it like Vulkan: a shared standard, not another per-vendor patchwork.

💡 Linux doesn’t need anti-cheat shoved into the kernel — it needs a standardized runtime that anyone can rely on.

What do you all think? Would this make Linux gaming more future-proof?

submitted by /u/isaacbinder
[link] [comments]

Basics

I just bought a qd oled monitor and obviously my first thought was that I'd need to try HDR on all of my games. Now typically, when running on both hyprland and kde, the process is very simple. All you should need is a compositor that supports hdr (Hyprland/KDE/GNOME/maybe some others), an HDR monitor, a new version of mesa and a game with hdr support. If you're playing games on wine you'll probably also need Proton GE 10 since HDR requires proton to be on wayland. The launch options that work for me in 99% of cases are `PROTON_ENABLE_HDR=1 PROTON_ENABLE_WAYLAND=1 %command%`. This kind of HDR implementation should work for any games support HDR PQ. The expected and usual behavior is that when the game opens, your screen should switch into HDR mode and you should be good to go.

Common issues:

HDR BLOWN OUT:

I found nearly instantly a few issues with the approach I just outlined above. Some games show an HDR option but their colors are obviously overblown, additionally my monitor doesn't actually switch into HDR mode. Through some research I found out that the issue stems from Hyprland (and possibly KDE) supporting a 10bit color space (AKA: HDR PQ), while some games hdr implementation is actually 16 bit scRGB. In this situation I found gamescope to be a great solution.

I first had to downgrade gamescope to 3.16.4-1.

On hyprland I set a few options in the config. Under the monitor: section I only have to set bitdepth = 10, I don't have any cm. experimental:xx_color_management_v4 = true (I don't think this is really needed since gamescope should be using its on CM protocol but it doesnt seem to hurt anything).

render:cm_enabled=true, render:cm_auto_hdr=1, cm_fs_passthrough = 0. Finally debug:full_cm_proto=true.

With these settings in my config, and running an scRGB game (like no mans sky) with these launch options: `DXVK_HDR=1 gamescope --mangoapp --backend sdl -W 5120 -w 5120 -H 1440 -h 1440 -r 240 -f --hdr-enabled --hdr-debug-force-output -- %command%; kill -9 gamescope-wl`

You should have HDR working perfectly. The important part here is --backend sdl. When using scRGB it seems to only work properly on the sdl backend.

STEAM INPUT DOESN'T WORK WITH HDR ENABLED:

This problem drove me absolutely insane, thankfully the solution is actually very simple. What seems to happen is that when a game launches with HDR support, a different WSI layer loads that gets in the way of steams overlay and also steam input. This results in lack of controller function in any game that needs steam input. To fix this problem, run steam with the -steamos3 flag. In my case I changed the application file command from `steam` to `steam -steamos3`. And just like that, your controller should work even when using gamescope or native HDR.

Hopefully this little info dump helps somebody out there. I found it extremely difficult to debug why some games worked with HDR and some didn't, and the info about this stuff is all very scattered. If you have any questions about my setup I'm happy to answer.

Specs:

GPU: RX 6800 (amd)

Display: MSI 49 in QD Oled

Mesa: 25.1.7-1

Hyprland: 0.50.1-1

gamescope: 3.16.4-1

Proton: GE 10-10

submitted by /u/Ethannij
[link] [comments]

I have been having issues with a game freezing (Marvel Rivals) and causing me to force close at times and I was advised that doing PROTON_LOG=1 %command% could help me catch whatever is happening.

Unfortunately I'm not really sure what I'm looking for. And since the freeze isn't something that I have been able to replicate on my own. The file ended up being 16,768,059 lines long. So I have no clue where to even go about looking where the freeze occurred for my game session. (Game froze for a bit but ended up unfreezing after about five seconds). Is there any keywords I can search the file for? Or is it a lost cause?

submitted by /u/Suspicious_Fly_2942
[link] [comments]

Title says it all. On my Ryzen 7600X/RX7900XT box running Ubuntu 24.04.3 (kernel 6.14) and Mesa 25.2 (from the mesarc PPA) enabling frame gen drops my 1440p FPS to ~120 from the usual ~180. I'm not running any FSR/XESS or RT and all settings but motion blur are on high. This is fairly standard setup, no optiscaler or other tweaks.

On my Windows 10 install on the same box turning on frame gen results in an average FPS of ~320. I installed Zorin 17 to see if a older kernel (6.8) and an older Mesa revision would help but it didn't. I've also tried every combo of upscaling/graphics tweaks to no avail. I just bought Cyberpunk this weekend so I don't have any data from an older version to compare it to nor do I have another game that uses frame gen. Any thoughts?

edit: all FPS measurements are from the canned benchmark not actual game play.

submitted by /u/Solid_Woodpecker8538
[link] [comments]

I have OCD so this troubles me for no reason. I love dual booting, why is it that I get 20-30 fps less on the same game and same settings than on Windows 11? I tried a variety of different distros and it's the same hmmm

submitted by /u/GrigorisKleanthous
[link] [comments]

I have every proton thingy installed and the game is in a ext4 formatted disk I have no idea why it doesn't work

submitted by /u/TightSelf5144
[link] [comments]

submitted by /u/InevitableCow8909
[link] [comments]

This link is close to the issue I'm seeing; for the past few months, steam recording shows "No Recording Available" in the overlay for The Finals. I'm on kubuntu 25.04, basically a clean install, 7900xtx, 3900x, 32gb ram.

I believe this is related to the startup with EAC: a wine CMD window opens at the same time as the eac splash screen. Recording in every other game I have installed works fine, I think the recording just doesn't grab the game window, does anyone know a fix?

submitted by /u/dirtywibs
[link] [comments]

I'm on Endeavouros using the heroic launcher. I'm having video issues no idea what to do. If I turn around I'll see the actual images but the blackness catches up

submitted by /u/Forward-Chance-4509
[link] [comments]

Since I know that a lot of people in this sub play cs2 and no post has been been made, I think this post is appropriate, for those who don't know, the newest cs2 update broke the first person model where it causes it to shake. this has been the case only for the linux port. When can we expect an update.

submitted by /u/Known_Job511
[link] [comments]

i want less keyboard input lag for linux gaming, i know there are setting but it doesn't enough, there are alternative in windows(Filterkeyssetter).

submitted by /u/Thileckva
[link] [comments]

A special announcement from Team Cherry has been revealed for Hollow Knight: Silksong.

.

Read the full article on GamingOnLinux.

Is having Shader Pre-caching enabled worth it? I have a Ryzen 5 5500 and have added the command 'unShaderBackgroundProcessingThreads 12' to steam_dev.cfg but it still is very slow (20+ minutes). Is it even necessary especially if the game already has a shader compilation screen? If it's necessary is there anything else I could do to speed it up besides upgrading the CPU which I already have planned? Thank you

submitted by /u/unhopeiguess
[link] [comments]