What do you mean? Screen savers have been possible for many, many years...
Zamundaaa
joined 3 years ago
VRR doesn't require additional bandwidth.
Try Linux on a 4k HDR 120hz TV and see what happens.
It works fine, with chroma subsampling. At least I personally don't ever notice it on the TV.
That's not to say this getting fixed isn't important, but it's mostly relevant for monitors and maybe smaller TVs that you sit closer to.
Not the person you asked, but I do have the new controller, and it works as they described it.
How it works afaik is that SDL has a driver for it, even if the kernel doesn't have a generic one yet. The controller also works in emulators without Steam running because of that.
All the distros use fprintd, but that's not related to Framework aside from the laptop using a sensor that fprintd supports.
The headset has eye tracking to make it possible, but yes, apps have to implement foveated rendering for it to work.
I think it is possible for the VR compositor to do some eye tracking optimizations for the app without the app doing special stuff, but I don't know how much that helps (or if it's even implemented in SteamVR).
There's no icc profile for it, it's just read from the EDID
Literally no other desktop has this functionality...
Yeah, afaik MacOS can do it too.
ICC profile is built-in in memory of my laptop screen?
Yeah. Surprisingly, nearly every display comes with somewhat accurate color information in its EDID.
Even Windows can't do it
Afaik they did actually implement something in this direction in Windows 11, but it's not exposed in a user friendly way yet.
There is no saturation slider, though. I've seen it on some screenshots.
It's currently always shown if the built in color profile, HDR or an ICC profile is used. IIRC it wasn't visible with the color profile in some older version of Plasma though, maybe that's why you don't see it.
Afaik Youtube is doing that, not Pulseaudio, and there's nothing that can be done about it.
view more: next ›
Aka "thing that isn't sandboxed, never has been sandboxed, and never has been claimed to be sandboxed, is in fact not sandboxed". Just like any app from your distro repositories, or appimages, or games in Steam... Or even most Flatpaks by default for that matter.
Widgets being sandboxed would be cool and is a long term goal (which is way easier said than done!), but don't present them not being sandboxed as some irresponsible thing someone does because they don't care. Your expectations of security simply are simply completely misplaced.