On Fri May 8 18:35:26 2026 +0000, Stian Low wrote:
swapchain_vk_present() calls wined3d_swapchain_vk_blit() which calls vkAcquireNextImageKHR() which always blits back_buffers\[0\] to vk_images\[image_idx\] so vk_images may handle back_buffer \> 1 at that level. These logs seem to indicate triple buffering handled at vulkan level which blits back_buffers[0] onto vulkan swapchain backbuffers and may fulfill wined3d_swapchain_vk_rotate()
01e8:trace:d3d:wined3d_swapchain_vk_blit image_idx 0 01e8:trace:d3d:wined3d_swapchain_vk_blit image_idx 1 01e8:trace:d3d:wined3d_swapchain_vk_blit image_idx 2 01e8:trace:d3d:wined3d_swapchain_vk_blit image_idx 0 01e8:trace:d3d:wined3d_swapchain_vk_blit image_idx 1 01e8:trace:d3d:wined3d_swapchain_vk_blit image_idx 2I attached screenshots of Frostpunk running via RenderDoc at https://bugs.winehq.org/show_bug.cgi?id=45364#c16 with and without the patch since it was mentioned by:
wine-staging/patches/wined3d-rotate-WINED3D_SWAP_EFFECT_DISCARD/0001-wined3d-Do-not-rotate-WINED3D_SWAP_EFFECT_DISCARD-sw.patch @hverbeet do you remember how to reproduce whatever bug the wine-staging patch was supposed to fix? RenderDoc v1.44 .exe seems to work the same regardless of this merge request patch with the only differences being the corrected graphics addressed by this patch. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10567#note_139273