Gamescope is a compositor, a self-contained graphical session, meant to run a single application. When it’s running in a nested context, i.e. as a window inside another graphical environment, it needs some kind of interface to be able to render the picture onto a window’s surface, and to receive inputs from it. The --backend ... option defines which interface will be used to achieve that.

• The wayland backend uses some native Wayland protocols, but it’s been broken for a while.
• The sdl backend uses SDL, which is a standalone rendering library often used by Linux-native games like Factorio and Stardew Valley. It simply captures Gamescope’s output and renders it onto a window without any Wayland protocol fuckery.
• The drm backend is used when Gamescope runs in a rootful context, i.e. it is the only graphical environment, like big picture mode on the Steam Deck. It uses the Linux kernel’s Direct Rendering Manager interface to render directly to the output device.
• The headless backend runs Gamescope without opening a window or showing its output. Everything happens in the background.
• The default is auto, which tries to guess the most optimal backend based on the runtime environment.

It’s not just a prefix manager. Bottles also provides a more predictable runtime environment using Flatpak sandboxing (it uses its own libraries instead of whatever’s installed on the system), and is specifically developed with that in mind.

The Wayland backend has been fucky for a while. Try running it with --backend sdl.

Please share those options, don’t keep them secret.

PVE running on a pile of e-waste. Most of the parts are leftovers from my parents’ old PC that couldn’t handle Win10. Proxmox loves it. Even the 10GB mis-matched DDR3 memory. The only full VM is OPNSense (formerly pfSense), everything else runs inside Debian containers. It only struggles when Jellyfin has to transcode something because I don’t have a spare GPU.

+1 for OMV. I use it at work all the time to serve Clonezilla images through an SMB share. It’s extremely reliable. The Clonezilla PXE server is a separate VM, but the toolkit is available in the clonezilla package, and I could even integrate the two services if I felt particularly masochistic one day.

My first choice for that role was TrueNAS, but at the time I had to use an old-ass Dell server that only had hardware RAID, and TrueNAS couldn’t use ZFS with it.

Nice, can we do Tarkov next?

Honestly, the resolution doesn’t really bother me. It’s just about right for the screen size, about 200 PPI at 7". If the screen were larger (which is one of the things I want from a SD2), it might not be enough.

The other thing I’d want is more USB sockets (at least one with USB-PD) on both the top and bottom edge.

What games is it too old for, exactly?

Still don’t understand why they cut the fleeb.

Anti-intellectualism as a defence. Nice. Abandon grammar and take language where an LLM can’t follow. Surely we’ll be able to tell a text written by a human from one written by a machine if the human writes it like a dumbass, I can’t see anything wrong with that. i mean why even use proper punctuation and capitalization an ai wouldnt write sumthin like dis isnnnt it better you can tell a human wrote dis

Have I made my point?

You’re not getting downvoted for the LLM thing. You’re getting downvoted for doubling down on a stupid argument. Em dashes – and en dashes for that matter – have legitimate uses in the English language. One symptom does not make a diagnosis. English is barely a respectable language in the first place. Dumbing it down even further to satisfy your preconceptions is, simply, stupid.

Be warned that Windows Update can see your other partitions. It ate my boot partition, then choked on it and took the entire system with it. That was the last time I had Windows on my computer.

Fanatec will need an extra kernel module: https://github.com/gotzl/hid-fanatecff

The first question you should consider is whether you actually need a gaming distro. I’ve been using bare-ass Arch for both gaming and development and haven’t had any performance or stability issues I didn’t cause myself.

From the two options, Nobara is likely better for a beginner. It’s based on Fedora, which has good support and doesn’t do anything fucky with the kernel. (it does, the kernel is built with patches and custom options)

Cachy is based on Arch, which in itself requires a more in-depth knowledge of the system and/or a willingness to learn. The performance improvements they advertise with the customized kernel and scheduler options are really only relevant if you want to squeeze the last bit of performance out of the system. Your day-to-day experience will be the same.

I don’t think you fully comprehend just how many footprints people leave behind on the internet. Users would have to practice perfect opsec – and I mean completely, absolutely perfect. One mistake, like using an e-mail address or an alias off-site, will link a person to the account. If that person cracks under legal threats, the entire operation is fucked. It’s happened before.

Thinking you can solve the issue of privacy with a single idea is simply delusional.

Have you heard of surveillance cameras and facial recognition? If a hostile actor knows in advance that members of a targeted online community will be physically present at a location at a given time, those people will be linked to the community. It doesn’t take a lot from then to link specific persons to accounts.

Besides, libraries are having a hard enough time just existing in America. They don’t need the burden of protecting the identities of dozens of people and fighting off lawyers and enforcers.

Yes, the desktop mode uses Plasma on X11 by default. It can be changed, but X11 is still perfectly functional and Wayland doesn’t have a lot of advantages in that particular use case.

Big Picture (and the games launched from it) uses an entirely different compositor called GameScope, which is developed by Valve and is meant specifically for games or other single-window applications. It can also be used in a nested setup inside another compositor.

Only on X11, not on Wayland (as of 6.4).

Edit: Confirmed Gammastep to work on Niri and Hyprland, but doesn’t work on Plasma.

Depends on the compositor.

• Hyprland has hyprsunset, you can increase the brightness without changing the color temperature using hyprsunset -i --max_gamma 200% -g LEVEL.
• For Wlroots compositors, you can try Gammastep. Wlroots seems to be the only compositor that implements a gamma correction protocol (though there is already an official color correction protocol in Wayland).
• Plasma on Wayland doesn’t have a gamma setting at the moment, but you can load ICC color profiles that might work. Also see this thread for another approach.
• GNOME and Cinnamon have this tool.