Final Fantasy XVI Crashes when HDR is enabled

[njdom24]

Running with gamescope --hdr-enabled --hdr-debug-force-support -- env DXVK_HDR=1 %command%, toggling HDR on causes the game to save the setting and instantly crash, preventing relaunching the game while the HDR flags are still in my launch options. Also crashes with Proton-EM with PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1

Works fine in KDE.

This is the only game I have with this issue. It has a demo on Steam.

PROTON_LOG=1 shows:

[Gamescope WSI] Creating swapchain for xid: 0x2000053 - oldSwapchain: (nil) - provided minImageCount: 3 - minImageCount: 3 - format: VK_FORMAT_A2B10G10R10_UNORM_PACK32 - colorspace: VK_COLOR_SPACE_HDR10_ST2084_EXT - flip: true
[Gamescope WSI] Created swapchain for xid: 0x2000053 swapchain: 0x7f80700fb1c0 - imageCount: 3
11688.807:0140:040c:info:vkd3d-proton:dxgi_vk_swap_chain_recreate_swapchain_in_present_task: Got 3 swapchain images.
[Gamescope WSI] VkHdrMetadataEXT: display primaries:
                                      r: 0.708 0.292
                                      g: 0.17 0.797
                                      b: 0.131 0.046
                                      w: 0.3127 0.329
                                  mastering luminance: min 0.001 nits, max 1000 nits
                                  maxContentLightLevel: 2000 nits
                                  maxFrameAverageLightLevel: 500 nits
                                  maxFrameAverageLightLevel: 500 nits

so the metadata doesn't look like anything crazy

[njdom24]

I'm running a 9070 XT with Mesa 25.2.4, but installing vk-hdr-layer-kwin6 and setting ENABLE_HDR_WSI=1 has the same issue.

[UjinT34]

PROTON_ENABLE_WAYLAND=1 doesn't work inside gamescope unless it is started with --expose-wayland. Doesn't make much sense to use it this way though.
Try with wayland-enabled proton and without gamescope. Works fine for me.

[UjinT34]

The log isn't useful, looks like it debugs the app inside gamescope. Should be without gamescope or WAYLAND_DEBUG=1 should be set before starting gamescope to debug gamescope itself.

If you have experimental:xx_color_management_v4 = true try removing it. Shouldn't be needed anymore.
Also try render:direct_scanout = 0

[njdom24]

Removing experimental:xx_color_management_v4 = true prevents Auto HDR from kicking in when I use gamescope. All games just display a fullscreen white until I manually set cm = hdr for my display, and even then, the cursor becomes a white square within gamescope. It does, however, not crash FFXVI. Still hangs with Wine Wayland, though.

This is with render:direct_scanout = 0, but I don't think it makes a difference since gamescope's Wayland backend gets DS blocked.

[UjinT34]

Your gamescope might be too old, it should support wp cm proto.

[njdom24]

I'm using gamescope-git from Chaotic-Nyx, which is at ValveSoftware/gamescope@0d3a197 on my system.

I had to leave for work, but I'll get a proper Wayland log tonight.

[njdom24]

with_xx.log
no_xx.log

These logs are captured with WAYLAND_DEBUG=1 on gamescope and WAYLAND_DEBUG=0 on the game.

I got them in Elden Ring Neightreign, which reports a bunch of 0s for its HDR metadata, but that shouldn't be relevant. The Auto HDR issue happens with every game in gamescope.
Just a white screen with my monitor still in SDR mode after I enter the title screen and the game enables HDR.

Update: Seems that Auto HDR works with:

• experimental:xx_color_management_v4 = false, debug:full_cm_proto = true
• experimental:xx_color_management_v4 = true, debug:full_cm_proto = false

Both gamescope Wayland debug logs were captured with debug:full_cm_proto = false