AutoHDR not working for any fullscreen HDR enabled application

[ChangoTheBeast]

Hyprland version

Hyprland 0.50.0 built from branch main
Tag: v0.50.0-5-g75c0675e1

Describe the bug

As in title, I have an OLED monitor with an auto HDR mode. When I set cm to hdr or hdredid, the monitor changes to HDR mode as expected.

If I do not set those and instead try to use the auto hdr feature via the renderer config the HDR mode stays off even with fullscreen HDR content:

render {
    direct_scanout = true
    cm_fs_passthrough = 0
    cm_auto_hdr = 1
}

Launching a game using gamescope with the following config doesn't toggle the HDR mode on my monitor: (Note: The games I have tried have HDR support that I have gotten to work with a dedicated gamescope session before such as Baldurs Gate 3, Path of Exile 2, Cyberpunk)

PROTON_ENABLE_HDR=1 PROTON_ENABLE_WAYLAND=1 ENABLE_HDR_WSI=1 DXVK_HDR=1 gamescope -w 2560 -h 1440 -f --hdr-enabled --hdr-debug-force-output -- %command%

I also have tried using mpv with a HDR video (from youtube) and same issue applies there:

ENABLE_HDR_WSI=1 DXVK_HDR=1 DISPLAY= mpv --fs "https://www.youtube.com/watch?v=njX2bu-_Vw4"

I tried both with and without the ENABLE_HDR_WSI=1 DXVK_HDR=1 DISPLAY= part and no change.

I also have tried all the previous with cm_fs_passthrough = 2 and with cm_auto_hdr = 2.
My monitor is a Corsair XENEON 27QHD240 OLED if that helps.

Let me know if any more info is needed for this issue, or if there is something I am missing. Thanks!

System info and config

Monitor config is the following:

monitorv2 {
    output = DP-1
    mode = 2560x1440@240.0
    position = 2560x0
    scale = 1
    bitdepth = 10
    sdrbrightness = 1.0
    sdrsaturation = 1.0
    supports_hdr = 1
    supports_wide_color = 1
    sdr_min_luminance = 0.005
    sdr_max_luminance = 225
    min_luminance = 0
    max_luminance = 1000
    max_avg_luminance = 225
}

system-config.txt

[LionHeartP]

Make sure you are on Aquamarine 0.9.2

Also, you don't need Gamescope. Those Proton environment variables handle HDR without it. That's the whole point of them.

[ChangoTheBeast]

Hi,
I am on Aquamarine 0.9.2. I did also try without using Gamescope (actually was what I tried first as the non-git version of Gamescope wasn't working for me either) but same issue is happening there.

[LukeDearden]

The only way I can make HDR work in Hyprland is by directly setting cm = hdr

Testing with Hunt Showdown and Proton-GE-10

PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 mangohud %command%

Monitor
Alienware AW3423DWF

I can't get the auto hdr stuff to work

Hyprland 0.50.0 built from branch main at commit 088e8af95567398ea0e339698e086039eba140ef  ().
Date: Thu Jul 17 22:11:00 2025
Tag: , commits: 6288
built against:
 aquamarine 0.9.2
 hyprlang 0.6.3
 hyprutils 0.8.1
 hyprcursor 0.1.12
 hyprgraphics 0.1.5


no flags were set


System Information:
System name: Linux
Node name: fedora
Release: 6.15.6-200.fc42.x86_64
Version: #1 SMP PREEMPT_DYNAMIC Thu Jul 10 15:22:32 UTC 2025


GPU information:
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 48 [Radeon RX 9070/9070 XT/9070 GRE] [1002:7550] (rev c0) (prog-if 00 [VGA controller])


os-release: NAME="Fedora Linux"
VERSION="42 (Workstation Edition)"
RELEASE_TYPE=stable

[doomperfect]

Which proton version are you using? On hyprland 0.50.0, latest proton-cachyos and Proton-GE-10.10 releases, using this launch option:

PROTON_ENABLE_HDR=1 PROTON_ENABLE_WAYLAND=1 ENABLE_HDR_WSI=1 DXVK_HDR=1 %command%

along with

render:cm_fs_passthrough = 0
render:cm_auto_hdr = 2

in both cm=wide and cm=edid, with bitdepth=10, always works for me, except in AC: Shadows for some bizarre reason (ref: #10993). Using AW3423DW OLED with nvidia GPU (open drivers).

For MPV, I use these config options, which work to trigger auto-hdr on 0.40.0 when fullscreening with an HDR source video:

vo=gpu-next
profile=high-quality
gpu-api=vulkan
gpu-context=waylandvk
target-colorspace-hint=yes

I notice that you didn't set cm explicitly - could you try? It might not be needed tbh, but worth a shot since it's the only difference I can see between our configs.

Also, I noticed two monitor configs in your monitors.conf file - the lower monitor entry might be overriding the monitorv2 entry, maybe this is causing issues.

Also also, you shouldn't use DISPLAY= envvar anymore, it's not needed and might break things.

[LionHeartP]

AutoHDR works fine in Elden Ring at least. It's a bit picky with it. You have to toggle the HDR setting off>on sometimes then wait like a minute in the title screen before it eventually triggers. Sometimes it triggers immediately when you press a button in the title screen (aka it parses your save file), sometimes not. Thankfully most of the times it's the former. As you can see I'm in HDR mode since my screenshot's colors are all wrong lol.

monitorv2 {
	output = DP-1
	mode = 2560x1440@180
	position = auto
	scale = 1
	vrr = 1
	bitdepth = 10
	}

[ChangoTheBeast]

So far I have tried Cuberpunk (with launch options to skip the launcher), Baldurs Gate 3 (with options to skip the launcher), and Path of Exile 2. I could be wrong but I think none of those have easy anticheat.

Also with Cyberpunk the HDR options show in-game but switching to them doesn't turn the monitor HDR mode on either (so looks bad)

I did also try removing the config of the second monitor as suggested bu that also didn't work unfortunately

However I have now tried it with Doom Eternal as above and it worked as expected the first time (after enabling HDR in-game).
Though subsequent launches resulted in no display at all

[doomperfect]

Yeah Elden Ring is a bit wonky, but it does sort of work eventually. I sometimes have to go in-game for it to actually go into HDR mode lol.

One thing I noticed in some games is that they need to be explicitly set to fullscreen mode ingame, or sometimes even set to borderless and then back to fullscreen, and then restarted, otherwise auto-HDR doesn't work properly. Had this issue with STALKER 2 and Dragon Age Veilguard iirc. But after setting them up like that it usually works for subsequent launches.

@ChangoTheBeast if you are still having issues, can you try to launch steam from a terminal and look at the logs for lines starting with [HDR Layer]? Following the process in #10993 - I think that will at least tell you what colorspace the game is trying to use.

Also here's my working config for autohdr, in case it helps anyone. Not all of these options are actually used/some of them are just default values, but I'm lazy and didn't remove any of them lol

monitorv2 {
	output = DP-3
	mode = 3440x1440@143.97Hz
	position = 0x0
	scale = 1
	transform = 0
	bitdepth = 10
	cm = edid
	sdrbrightness = 0.9
	sdrsaturation = 1.25
	vrr = 0
	supports_wide_color = 1
	supports_hdr = 1
	sdr_min_luminance = 0.005
	sdr_max_luminance = 400
	min_luminance = 0
	max_luminance = 1000
	max_avg_luminance = 300
}

debug:full_cm_proto = false
experimental:xx_color_management_v4 = true
render:send_content_type = true
render:direct_scanout = 1
render:cm_fs_passthrough = 0
render:cm_auto_hdr = 2
render:new_render_scheduling = false
cursor:no_hardware_cursors = 2

[doomperfect]

Also slightly off topic, but Nightreign specifically doesn't have support for SDL controllers, so I can't use Wayland native on it for HDR because Wayland native doesn't support Steam Input, so I'm forced into gamescope HDR on that game anyway to be able to use a controller (via Steam Input) + HDR lol.

But the auto HDR still works through these convoluted gamescope launch options (has to be full screen ingame):

ENABLE_HDR_WSI=1 game-performance gamescope --fullscreen -w 3440 -h 1440 -r 144 --hdr-enabled --hdr-debug-force-output --force-grab-cursor --mangoapp -- env ENABLE_GAMESCOPE_WSI=1 DXVK_HDR=1 DISABLE_HDR_WSI=1 %command%

[ChangoTheBeast]

@doomperfect
I think that might be part of the issue for some games I tested, I will give them a go again with the exact same options you have here and get back on it. I will also do as suggested with the terminal logs and see if I find anything. Thanks for all the suggestions