https://bugs.kde.org/show_bug.cgi?id=495111
Zamundaaa <xaver.h...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Ever confirmed|0 |1
Status|NEEDSINFO |CONFIRMED
--- Comment #7 from Zamundaaa <xaver.h...@gmail.com> ---
(In reply to Noah Davis from comment #3)
> Isn't gamescope a Steam Deck thing? I don't think the reporter is using a
> Steam Deck. They seem to be using a desktop computer.
No, it's the only way (outside of Quake II RTX) to get games working with HDR
on the desktop too.
(In reply to Oleg from comment #4)
> Created attachment 175085 [details]
> Lutris log
>
> Here's a log from Lutris. I've observed one thing that I'll describe in the
> next attachments.
There's this in the log:
> [HDR Layer] wayland compositor lacking frog color management protocol..
You shouldn't use my Vulkan layer with gamescope, at best it does nothing, but
it can cause problems.
Other than that I just see absolutely nothing in the log. This suggests that
the game just doesn't set any HDR metadata whatsoever, making this rather hard
to deal with. Maybe we could just assume the game's configured to work well
with your screen's metadata, or that it's configured for HGIG recommendations,
but that could still mess things up.
Aside from just supporting HDR screenshots properly, the only proper-ish thing
I can think of here is to analyze the image before tone mapping, to figure out
the maximum luminance and use that for tone mapping.
(In reply to Oleg from comment #5)
> When I take screenshot from screen it is actually tone mapped correctly.
Yes, but that's more of a bug than intentional. When you take a "screen"shot,
KWin takes the HDR metadata of the screen, instead of the content that's
currently shown on it.
--
You are receiving this mail because:
You are watching all bug changes.
