https://bugs.kde.org/show_bug.cgi?id=503579
--- Comment #7 from Zamundaaa <xaver.h...@gmail.com> ---
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)
--
You are receiving this mail because:
You are watching all bug changes.
