The sheer creativity people achieved trying to play songs over the built-in Text-to-Speech synthesis is amazing

The throttling message is a bit misleading. In fact it tells you why your GPU can’t reach higher boost clocks, and will say either temperature or TDP/power limit

SteamVR on Linux as of now is a joke, features necessary to experience VR without getting nausea are missing, namely working asynchronous reprojection and correct vsync_to_photon timings.

I’m using HTC Vive Pro on Arch Linux (one of 4 SteamVR native headsets) for context.

There is an open-source alternative called Monado which does work better than SteamVR, but it’s game compatibility is a hit or miss, and you don’t get features like Chaperone/Guardian on it

Which variant of it, if I may?

*In games running on Unreal Engine 5

1411 kbps before compression. FLACs can go as low as 200 kbps based on the content of a file

To my knowledge it’s lossless in CD quality only, in high-res modes it becomes lossy

I really hope Proton 10 will have some sort of Wayland support, even if it would be hidden behind an environmental variable

deleted by creator

deleted by creator

Thanks for the PSA, I was about to go on a troubleshooting spree with Discord not using KDE’s file picker

EAC on Linux uses special runtime usually provided by Steam and it runs in userspace. However, developers have to whitelist said runtime and that’s where the issue is

KDE Plasma Wayland, I’m using it for gaming mainly and occasionally for VR.

Pros:

• supports DRM leasing mandatory for wired VR headsets
• supports tearing (also in windowed apps but requires an additional setting) which reduces input latency in games
• usually all the new fancy features, ex. HDR, appear quickly
• decent support for fractional scaling (handy on laptops)

Cons:

• you might encounter bugs. While Plasma 6 has been a much better experience as opposed to older versions of it, there are still some bugs here and there appearing between the updates. As of this writing thought I can’t recall any bugs on my system.

I had no clue KDE has an image writer, good to know and will definitely give it a try :3

“Late is for a while suck is forever”

Steam Deck runs an embedded session of Gamescope which uses DRM (no not copy protection) to display games.

Running Gamescope as a launch command will run it in a nested session, where it’s output is being sent to your display manager, ex. Kwin. That’s where the lag can happen, and usually does especially in GPU bound scenarios

Try passing SDL_VIDEODRIVER=x11 in launch parameters

Gamescope will add input lag which is something you don’t want to have in a game like CS2

As a person who used to do Hackintoshes I am impressed people got it to boot on a Steam Deck

“Monopoly”, other platforms are free to compete, Valve isn’t actively trying to stop them