EDIT: Something seems to have changed and I’m struggling to figure out what, but HDR has broken again. I’m not sure if it was a system update or not but I no longer see HDR in the display configuration, and running games like Baldur’s Gate 3 or Tiny Tina’s Wonderlands results in washed-out colors when HDR is enabled in them. I will update here if I figure it out.

For those of you like me who are fed up with Microsoft’s BS but invested too heavily in hardware that Linux distros have yet to support well, I finally figured out a way to get HDR games to run well on my Nvidia GPU. This will be a brief description of more or less what I did to get this working. I’m very much a Linux noob so I don’t fully understand the way everything here works but I’m happy to try to answer questions if you have any.

OS: Bazzite –Desktop Nvidia KDE edition (BDNK) Bazzite was developed as a capable alternative to SteamOS on handhelds like the Steam Deck and ROG Ally, so the website is full of references to HDR, however from my attempts to get this working my understanding is that it’s easier to get that working in Gaming mode which is unsupported on Nvidia GPUs. Nevertheless, this version of Bazzite, while only for desktops, comes with KDE Plasma v6 installed by default meaning it technically supports HDR and you will likely see a difference if you install this version and flip the HDR switch from the display settings. I had tried installing Ubuntu on my desktop before and since it didn’t support HDR all the colors on my monitor were almost obnoxiously saturated; I see the same effect in BDNK when I disable HDR.

Drivers: I didn’t fiddle with my drivers. BDNK comes with up-to-date Nvidia drivers bundled and installs them when you install the OS.

Software: SteamTinkerLaunch (installed using ProtonUp-Qt) SteamTinkerLaunch (STL) is a user interface for making it easy to configure your launch options for any given game in your Steam library. If you don’t know what a compatibility tool is, it’s functionally a layer of software between the game you want to play and the OS you’re using which can tell the game to do certain things that your OS is not configured to do. STL can be added to the list of compatibility tools you have to use in your installation of Steam, though it is not technically a compatibility tool itself. STL is used to configure other compatibility tools that Steam already has at its disposal, like Proton which is the primary compatibility tool SteamOS uses to make Windows games run on Linux.

Follow the instructions in the SteamTinkerLaunch GitHub ReadMe to install the tool and add it as a compatibility tool in your installation of Steam. Once you’ve done that, I recommend rebooting. I have yet to get STL working as the * default * compatibility tool, so for the time being I have been manually editing the properties of each game I have installed (Steam Game Library > right click on a game > click properties > go to the compatibility tab) to set the compatibility tool to STL. From here, whenever you launch the game in Steam, it should bring up STL’s menu before launching the game.

Within STL, the key settings to mark are as follows: Gamescope: Use gamescope and mark HDR as enabled for gamescope. I also recommend setting gamescope to fullscreen with your desired resolution, and then also locking your cursor to the gamescope window so that you don’t end up with weird double mouse cursors that aren’t aligned on the screen. Proton: since you told Steam to use STL instead of Proton as the compatibility tool, you need to tell STL to tell Steam to launch the game with Proton.

And that’s pretty much it. Or at least, that’s all that I did. From there, you should be able to configure HDR settings within each game’s menus.

TL;DR – install Bazzite Desktop Nvidia KDE, then install and configure SteamTinkerLaunch for your games.

What games will this work with? No idea. So far I have tested it with Cyberpunk 2077, DOOM Eternal, and Elden Ring and HDR is looking to me as good as it does in my Windows installation.

Will the Gnome version of Bazzite work for HDR on an Nvidia GPU, or for that matter any other OS as long as I’m using gamescope to run the game with HDR enabled? Good question! I don’t know, please give it a try if you’re curious and respond back with your results.

I have another question that you didn’t list here, what’s your answer? Probably “I don’t know” since what I wrote here is more or less what I know, but by all means ask away and I’ll try to answer it!

  • Virkkunen@fedia.io
    link
    fedilink
    arrow-up
    6
    ·
    5 months ago

    You don’t really need STL, just set gamescope as the launch parameter. I suggest checking --help to see what the flags do, but in general you’ll want gamescope -W <res width> -H <res height> -r <refresh rate> -f --force-grab-cursor --hdr-enabled -e -- %command%. This works for me on TEKKEN 8, Helldivers 2 and Deep Rock Galactic.

    There are some issues, however. Some games might just freeze when running with gamescope (or gamescope with HDR flags), which is the case for me with Deep Rock, it’ll freeze merely 20 seconds after it starts. Second issue is that, at least for me, the image will be incredibly dark and for some reason the SDR content brightness slider on Plasma settings will change the brightness of the HDR gamescope window, so I have to set it to 1000 to “fix” the brightness, but my desktop will be blown out with brightness.

    • naticus@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 months ago

      Does --force-cursor-grab fix the issue where the mouse cursor might be misaligned with where you’re clicking? Hadn’t ever used that parameter in my setup and have avoided games that had 3rd party launchers because of this very issue.

      • BmeBenji@lemm.eeOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 months ago

        I believe that’s the flag that worked for me, though STL obscures the exact flag names away

      • Virkkunen@fedia.io
        link
        fedilink
        arrow-up
        1
        ·
        5 months ago

        It’s --force-grab-cursor, sorry. It should fix this issue of having a secondary cursos on screen and the cursor leaving to other monitors.

        • naticus@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 months ago

          Err yeah, lol… That’s what I meant, but typed it wrong. And hmmm, not sure that’ll do it then but I will give it a try.

      • Virkkunen@fedia.io
        link
        fedilink
        arrow-up
        1
        ·
        5 months ago

        Deck’s game mode is already running an embedded gamescope session with the flags enabled, so that wouldn’t be needed. Might be something else going on that’s worth searching about, though

      • Virkkunen@fedia.io
        link
        fedilink
        arrow-up
        2
        ·
        5 months ago

        If you’re running it as a launch parameter on Steam you need it for the overlay and input to work, however this has been broken for quite a while now. Some people say gamescope 3.14.24 fixed it, but it wasn’t my case.