Probably because vkd3d-proton now uses VK_EXT_swapchain_maintenance1, which allows you to change the present mode dynamically without recreating the swapchain and mangohud can't detect that.
May be it would be good to add some logging line to vkd3d-proton about what presentation mode it decides to set? I don't see it in the log (attached it above).
Also, is there a way to detect presentation mode for mangohud after it was set dynamically like that?
Mangohud should be able to detect it, but it would have to check the new EXT struct on every present. Looks to me like it currently only checks in CreateSwapchainKHR.
Not a vkd3d-proton bug, closing.
Can vkd3d-proton report the setting of presentation mode in the log at least? Or it already does that?
MANGOHUDx1 2024-02
New version of mangohud can report Vulkan presentation mode. When running Cyberpunk 2077 (2.11), for some reason it's showing me fifo, even though vsync is off in the game. Shouldn't it be mailbox? Or how does vkd3d-proton decide on what presentation mode to set?
According to kwin developers, presentation mode is set by the client not by compositor, so it's likely vkd3d-proton deciding it.
The way to enable it in the HUD:
MANGOHUD_CONFIG=present_modeSee also: https://github.com/flightlessmango/MangoHud/issues/1190
Screenshot:
Wine log:
wine.log