Well yes… I was responding to your question about why a launcher would need HDR support.
It needs HDR support because “steam” is more than just a launcher. It includes proton, which needs HDR support so that games that have HDR support can use HDR.
Not really. Steam doesn’t include Proton by default. It’s downloaded on demand. It’s a separate product with its own code base (derived from WINE), bug tracker, and since recently even its own logo.
Just because it’s an optional component, doesn’t mean that it isn’t part of an overarching product. KDE contains many different parts that may or may not be installed, that doesn’t mean they aren’t part of KDE. “Steam” is a larger product composed of separate models such as the GUI and compatibility layer.
That’s just the client itself. It’s also not entirely their fault, since they use CEF, and CEF is a colossal pain in the ass. The issues and the pull requests are all there, but it doesn’t seem like anyone is actively working on them at this point
Steam isn’t even on wayland - complain about that ticket if you want HDR lol.
not to mention steam actually does have some degree of HDR support through gamescope, which steamdeck ships with.
(also HDR support on linux has barely started being a thing this year…)
Why would a games launcher even need HDR? Whether games support HDR or not is completely disconnected from HDR support of Steam.
Also Valve is sponsoring upstream development of HDR support in KWin and wlroots (Gamescope is based on it). Red Hat is working on Gnome stuff.
I’m assuming that they are including Proton in “Steam”, not just the launcher.
Steam Deck OLED was launched with HDR support in Proton and Gamescope.
Well yes… I was responding to your question about why a launcher would need HDR support.
It needs HDR support because “steam” is more than just a launcher. It includes proton, which needs HDR support so that games that have HDR support can use HDR.
Not really. Steam doesn’t include Proton by default. It’s downloaded on demand. It’s a separate product with its own code base (derived from WINE), bug tracker, and since recently even its own logo.
Just because it’s an optional component, doesn’t mean that it isn’t part of an overarching product. KDE contains many different parts that may or may not be installed, that doesn’t mean they aren’t part of KDE. “Steam” is a larger product composed of separate models such as the GUI and compatibility layer.
OK, whatever. I’m not fighting this battle for a minor thing you’re wrong about.
That’s just the client itself. It’s also not entirely their fault, since they use CEF, and CEF is a colossal pain in the ass. The issues and the pull requests are all there, but it doesn’t seem like anyone is actively working on them at this point