⨯ Check out what systems our users are running on our special statistics page.
HDR support for Steam games
Sira 20 Sep 2026
I'm sorry if this has been covered somewhere else (I tried to search the GamingOnLinux site, but didn't find any articles on it and no hits on 'HDR' for the forum)

I'm trying to understand what I am missing for my Steam games to support HDR and I hope someone can help :)

I run openSUSE and are trying to get HDR back in Diablo IV and Palia. The same hardware ran these games with HDR when I used Windows, so I believe these to be a good starting point.

Both my monitor's display menu as well as openSUSE's Display configuration settings page, report that HDR is enabled.

As for Steam, I read somewhere that it was around Proton v9 that HDR support was introduced.
I sat the Steam default compatibility tool to: Proton 11-0-2 today, because Diablo IV started to experience issues with Proton Experimental, where the game would freeze if the monitor was turned off while the game was running.

I've tried to use start parameters: PROTON_ENABLE_HDR=1 DXVK_HDR=1 ENABLE_HDR_WSI=1 %command%
... but the HDR option in the games remain unavailable.

Thanks in advance,
~ Sira
This topic has an answer marked - jump to answer.
Ehvis 20 Sep 2026
User Avatar
Don't have HDR hardware myself, but probably good to add you GPU and desktop environment here to narrow down possible solutions.
I'm not home right now to check everything on my system but PROTON_ENABLE_HDR=1 is a proton-cachy and proton-ge options not vanilla proton options. Vanilla proton needs gamescope to have HDR with "DXVK_HDR=1 gamescope -f --hdr-enabled -- %command%"
more info is here (External Link: You need to be logged in to view this.)

Don't know what hardware you have proton-cachy says ENABLE_HDR_WSI=1 is only need for nvidia driver versions older than 595.x.x
Sira 21 Sep 2026
Thank you so much for the quick replies πŸ˜„

How could I forget my hardware info 😡

Sorry if this too much information. I have yet to understand how much of the OS-info is important when troubleshooting in Linux πŸ˜…
  • Operating System: openSUSE Tumbleweed-Slowroll 20260901

  • KDE Plasma Version: 6.7.5

  • KDE Frameworks Version: 6.29.0

  • Qt Version: 6.11.2

  • Kernel Version: 7.2.5-1-default (64-bit)

  • Graphics Platform: Wayland

  • Processors: 24 Γ— AMD Ryzen 9 7900X 12-Core Processor

  • Memory: 64 GiB of RAM (62.0 GiB usable)

  • Graphics Processor 1: AMD Radeon RX 7800 XT

  • Graphics Processor 2: AMD Ryzen 9 7900X 12-Core Processor

  • Manufacturer: ASUS

  • The screen is an LG UltraGear 27GN950-B (External Link: You need to be logged in to view this.) running 3840x2160 @ up to 144 FPS via a DisplayPort cable.

I also tried to add my PC info using the forum's feature for it, as I noticed others had. The forum does not have as detailed options though, which seem important when troubleshooting HDR?

As for Persephone the Sheep's reply:

Yeah... I simply searched around what others had done.
I should have known better than to just use {random gamer person from Reddit}'s solutions without much explanation, but I thought I owed it to everyone to try out some start parameters for HDR before posting here.
In hindsight, I ended up making it more complicated that it had to - Woopsies πŸ˜…

Well, I've removed PROTON_ENABLE_HDR=1. I read to use PROTON_USE_WAYLAND=1 - Something about how the info from Wayland had to be passed on into Proton, for HDR to work. Is that right - or would it be better to forget it all and take instructions from you? You seem to know exactly what you are doing :)

If I understand your reply correctly, Vanilla Proton (yet) need something "extra" for HDR to work?
K I'm now home from visiting my sister, going though it on my side with AMD hardware on KDE and using stellar blade.

proton-cachyos is PROTON_ENABLE_WAYLAND=1 %command% 
proton-ge is PROTON_ENABLE_HDR=1 PROTON_ENABLE_WAYLAND=1 %command%

I can't get vanilla proton to work not sure what I am doing wrong or what the issue would be.

Quoting: SiraIf I understand your reply correctly, Vanilla Proton (yet) need something "extra" for HDR to work?
From what I understand vanilla proton is just designed to be used in SteamOS' gamemode so it only works with their gamescope compositor. It's packaged on Tumbleweed so I assume Slowroll has it but seeing as the proton forks are easier to use probably just use them for HDR.

Think I should say vanilla proton doesn't have any wayland options so if you see someone using any its a fork or they don't know they need a fork one or the other.

And the PC info page should be enough for future help in my opinion.
Sira 22 Sep 2026
Wow... I am honoured by you spending so much time to get things set up just to try and figure this out for me!
Truly, the open source community, and Linux especially, is so helpful and not at all judgy πŸ˜„
It's a whole new world, coming from Windows where everyone has so little patience for a beginner's questions and the default solution to everything is to check file integrity πŸ˜…
Again: It is truly appreciated!

Okay, I read your post several times to try and understand it (this girl has a slow brain, sorry!)

Proton-cachyos and proton-ge are not vanilla proton versions, and won't be offered by Steam, right?

So... Because I really want to keep things simple and only rely on Steam and not something third party, I guess I will be going for the gamescope micro-compositor, since that seems to just be something you install and then call using start parameters inside Steam game properties - yes?

I'm currently looking for articles on Gaming On Linux on how that is done.
✏️: Unfortunately no tutorial on GOL, it seems, so I'll have to broaden my search into the vast internet.

Thank you for taking the time to reply to all my questions so far :)

Last edited by Sira on 22 Sep 2026 at 10:19 am UTC
Sira 23 Sep 2026
Thank you again for taking the time 🫢🏼
Your thorough explanations are still very appreciated, even if you are used to doing this :)
Don't worry about the response time, a thorough, well formatted reply is better than a rushed, and thus confusing or easily misinterpreted reply 😊

Unfortunately it didn't work.
I looked into the issue and on Reddit, someone mentioned that this was an issue for them because they ran Steam as Flatpak.

So... Now I am facing another issue entirely, outside the scope of this topic, because I am running Steam as Flatpak.
I will create a new topic for that, to avoid derailing this one :)

The remainder of the post is my reply before I saw yours.

Spoiler, click me
I did look into gamescope myself and found a nice video from LinuxNext (External Link: You need to be logged in to view this.), which was also the foundation of how I got openSUSE installed to begin with, but your code is much more complete and more concisely explained :)
Though I did have some trouble understanding your part about DXVK_HUD=1 but I interpreted it like this:
DXVK_HUD=1 enables HDR support. Even though it says DXVK, its for DX11 and DX12 games.
I don't have a Vulkan HDR game to see if this can be left out, but if you do, you can try to leave it out for those games.
.
A random character after quote-code was necessary to prevent the next paragraph from showing with no line separation; at least when previewing the post.

I tried to put similar code into the same input box, but then my game would stop running right after Steam registered it running. The following is gamescope code - but before HDR parameters - just to see if I could get it to simply run.
gamescope -w 3840 -h 2160 -- %command%

The only thing that does work is only writing gamescope, but that's not really useful πŸ˜…
Sira 25 Sep 2026
The continued journey towards HDR

I installed Steam from Zypper.
Using Discover, I was able to confirm that this is installed from the openSUSE Tumbleweed-Slowroll repository, and is thusly not just the Flatpak via console.

For reasons unknown to me, I no longer experienced games crashing using 'native' Steam as I did before I switched to Flatpak.

Super relieved, I then went ahead and moved most of my games from Flatpak-Steam to the 'native' Steam.

In this process, I created a new directory outside of Steam folder /Home/Sira/Gaming (to avoid the loooong var paths and have a place to store all game related stuff in the future).

Then I deleted the Flatpak-version of Steam as well as anything that sounded like it was installed by the Faugus Launched by my previous experimentation, which was mainly winetricks.

Then I went ahead and tested every game I had previously run successfully via Steam (Flatpak) to make sure all the moved (or reinstalled) Proton packs were working properly.

To the exciting stuff: Enabling HDR in game's properties
Now running games with your code: DXVK_HDR=1 gamescope -W 3840 -H 2160 -f --hdr-enabled -- %command% ...no longer crashes the games, but I am not able to see HDR options in-game for any game that supported it on my Windows-installation; or in-case of Diablo IV, the HDR option remains disabled.

My questions are now these
  • How can I verify that HDR is correctly sent to the game?
  • Does HDR work without touching the in-game options when enabled through gamescope, or must it also be enabled in-game to activate?


Thank you in advance 🫢🏼
~ Sira
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon Logo Patreon. Plain Donations: PayPal Logo PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register