Desktop Mode HDR Profile Options Menu (Gamescope vs. Accurate)

Open
#2,535 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
linux
Domain
desktop

Research direction

Start by tracing the Desktop Mode HDR path through KDE Plasma/KWin and comparing it with the Gamescope presentation used in Gaming Mode. Define how an optional Accurate, Balanced, Gaming, or Vivid profile would be exposed in the HDR quick settings or Display Settings, and consider the existing HDR behavior preserved when the option is disabled.

Written by the indexing model from the issue text.

Description

Your system information
  • Steam client version: 1782533657
  • SteamOS version: 3.8.11 Build 20260620.1
  • Opted into Steam client beta?: No (Steam Deck Stable)
  • Opted into SteamOS beta?: No
  • Have you checked for updates in Settings > System?: Yes
Please describe your issue in as much detail as possible:

Feature Request: Optional Gaming Mode HDR Presentation for Desktop Mode

First, I'd like to say that Desktop HDR on SteamOS has come a long way. HDR is functioning correctly, and I appreciate all of the work that has gone into bringing HDR support to Desktop Mode.

After extensive testing, however, I noticed a consistent difference between Desktop Mode and Gaming Mode.

Using the same:

  • Hardware
  • HDR monitor
  • HDMI cable
  • GPU
  • Game
  • Proton version
  • DirectX 12 renderer

Gaming Mode consistently produces a noticeably more vibrant HDR image with greater perceived contrast and color volume than Desktop Mode.

Desktop Mode HDR is not broken—it simply presents HDR differently.

To rule out configuration issues, I verified the following:

  • HDR enabled in KDE Plasma
  • Wide Color Gamut enabled
  • 10-bit output active
  • Wayland session
  • Proton Experimental
  • DirectX 12 renderer
  • PROTON_ENABLE_HDR=1
  • ENABLE_HDR_WSI=1
  • DXVK_HDR=1

Desktop Mode correctly negotiates HDR with the monitor, and HDR output is confirmed.

After comparing the two environments, the remaining difference appears to be the HDR presentation and tone mapping performed by Desktop Mode (KWin) versus Gaming Mode (Gamescope).

Rather than changing the current Desktop HDR behavior, I would love to see an optional Gaming Mode HDR presentation profile available in Desktop Mode.

For example, under the SteamOS HDR quick settings (the "^" menu) or Display Settings:

HDR Presentation

• Accurate (Current Desktop Mode Default)
• Balanced
• Gaming (**Gamescope**)
• Vivid

or simply

☑ Use Gaming Mode HDR presentation for fullscreen applications

This would allow users to choose between:

  • a standards-based desktop HDR profile for productivity and color-critical work, and
  • a Gamescope-style HDR presentation optimized for gaming.

As SteamOS expands to Steam Machines and Desktop Mode becomes a first-class gaming environment, providing a consistent HDR presentation between Desktop Mode and Gaming Mode would create a much more unified user experience while preserving the existing accurate HDR implementation for users who prefer it.

This request is not asking to replace Desktop HDR—only to expose an optional presentation mode that more closely matches Gaming Mode.

Steps for reproducing this issue:
  1. Connect an HDR monitor (BenQ EL2870U in my case).
  2. Enable HDR in Desktop Mode.
  3. Launch the same game in Desktop Mode.
  4. Launch the same game in Gaming Mode.
  5. Compare HDR presentation.
Expected result

Desktop Mode should optionally be able to match Gaming Mode's HDR presentation for fullscreen games.

Actual result

Desktop Mode HDR functions correctly but appears noticeably less vibrant than Gaming Mode despite identical hardware, monitor, and game configuration.

Hardware
  • SteamOS 3.8.11 Build 20260620.1
  • KDE Plasma 6.4.3
  • Wayland
  • AMD Radeon RX 5700 XT
  • AMD Ryzen Threadripper 1950X
  • 160 GB RAM
  • BenQ EL2870U HDR monitor (HDMI)
Dominant language
No language data
Stars
2.6k
Forks
83
Avg merge
4m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ValveSoftware/SteamOS

All issues in ValveSoftware/SteamOS

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.