Bug 503579

Summary: HDR colors in Assassins Creed Shadows washed out
Product: [Plasma] kwin Reporter: Harald Sitter <sitter>
Component: colour-managementAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: normal CC: kdedev, nate, xaver.hugl
Priority: NOR    
Version First Reported In: master   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: SDR
HDR
wayland_debug log

Description Harald Sitter 2025-04-30 15:52:55 UTC
SUMMARY
With HDR enabled the colors look washed out. I am attaching two screenshots.

STEPS TO REPRODUCE
1. install AC Shadows on steam
2. enable HDR in systemsettings
3. set game launch command to `gamescope -f --hdr-enabled -- %command%`
4. start game
5. head to graphics settings
6. enable hdr & apply
7. disable hdr & apply

OBSERVED RESULT
HDR colors look awful

EXPECTED RESULT
HDR looks shiny

SOFTWARE/OS VERSIONS
Operating System: KDE Linux 202504290254
KDE Plasma Version: 6.3.80
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.4-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 32 ร— AMD Ryzen 9 5950X 16-Core Processor
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: AMD Radeon RX 7800 XT

ADDITIONAL INFORMATION
Gamescope from git master. It's unclear to me which part of the stack is to blame here. Works on windows though.
Comment 1 Harald Sitter 2025-04-30 15:53:31 UTC
Created attachment 180812 [details]
SDR
Comment 2 Harald Sitter 2025-04-30 15:53:46 UTC
Created attachment 180813 [details]
HDR
Comment 3 Zamundaaa 2025-04-30 16:13:52 UTC
Could you try running the game in a gamescope session for comparison? So
> gamescope -e --hdr-enabled -- steam -gamepadui
from a tty
Comment 4 Harald Sitter 2025-04-30 16:51:01 UTC
Curiously steam crashes when I try that :S

On the steam deck the game works as expected though.
Comment 5 Zamundaaa 2025-05-02 16:57:36 UTC
(In reply to Harald Sitter from comment #4)
> On the steam deck the game works as expected though.
Ok, then it might be a bug in KWin.

Can you start gamescope nested with WAYLAND_DEBUG=1 and give me the log for that? Would be interesting to know what colorspace the game is using
Comment 6 Harald Sitter 2025-05-03 10:58:49 UTC
Created attachment 180906 [details]
wayland_debug log

Attaching the log. Towards the end I'm disabling&enabling HDR for good measure.
Comment 7 Zamundaaa 2025-05-05 18:57:31 UTC
Alright, it does set the surface to BT2020PQ:
> May 03 12:51:15 ajax steam[8087]: [ 197692.195] {Default Queue}  -> wp_color_manager_v1#17.create_parametric_creator(new id wp_image_description_creator_params_v1#124)
> May 03 12:51:15 ajax steam[8087]: [ 197692.198] {Default Queue}  -> wp_image_description_creator_params_v1#124.set_primaries_named(6)
> May 03 12:51:15 ajax steam[8087]: [ 197692.200] {Default Queue}  -> wp_image_description_creator_params_v1#124.set_tf_named(11)
> May 03 12:51:15 ajax steam[8087]: [ 197692.202] {Default Queue}  -> wp_image_description_creator_params_v1#124.create(new id wp_image_description_v1#127)
> May 03 12:51:15 ajax steam[8087]: [ 197692.204] {Default Queue}  -> wp_color_management_surface_v1#50.set_image_description(wp_image_description_v1#127, 0)

Only thing that's a wrong is that it doesn't set any HDR metadata, which may make KWin do much more aggressive tone mapping than necessary. I see that was recently fixed in gamescope, could you try again with the latest version? Gamescope git master seems to work fine for me in other games at least (besides an annoying mouse input issue, but that's unrelated)
Comment 8 Harald Sitter 2025-06-04 09:22:40 UTC
Currently can't be tested because gamescope just crashes out https://github.com/ValveSoftware/gamescope/issues/1796

Setting needsinfo state so the bot can remind me to check in a couple weeks.
Comment 9 Bug Janitor Service 2025-06-19 03:47:59 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2025-07-04 03:47:51 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
Comment 11 Harald Sitter 2025-07-04 12:59:37 UTC
Still blocked upstream. I did leave some more info that hopefully should help resolve the upstream problem.
Comment 12 Harald Sitter 2025-07-04 12:59:57 UTC
Setting back to needsinfo state.
Comment 13 Bug Janitor Service 2025-07-20 03:47:08 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 14 Harald Sitter 2025-07-23 08:24:32 UTC
Still no upstream fix in sight. I'll reopen whenever that happens and the colors are still off.