The correct fix is to remove the option entirely. There's no reason for it to exist and when it was there, it didn't work as expected on anything.
Also, shouldn't DXVK force default number of dxgi.numBackBuffers to be 4 for VK_PRESENT_MODE_MAILBOX_KHR (and maybe for VK_PRESENT_MODE_IMMEDIATE_KHR), as described in #806 ?
No, DXVK (or any Vulkan application) is not supposed to guess what the window system it's running on might require. This is not a bug, and the workaround is to specify it manually in the config file when running on XWayland.
Understood, thanks.
DXVK_HUD=fps,frametimesx1 2019-01
https://github.com/doitsujin/dxvk/blob/master/src/d3d11/d3d11_options.cpp#L17 -- never used ?
https://github.com/doitsujin/dxvk/blob/master/src/d3d11/d3d11_swapchain.cpp#L707
https://github.com/doitsujin/dxvk/blob/master/src/vulkan/vulkan_presenter.cpp#L283
Looks like "Present mode" will always be
VK_PRESENT_MODE_FIFO_KHRby default,and
VK_PRESENT_MODE_IMMEDIATE_KHRfordxgi.syncInterval=0.dxgi.syncMode = 1ignored.Also, shouldn't DXVK force default number of
dxgi.numBackBuffersto be4forVK_PRESENT_MODE_MAILBOX_KHR(and maybe forVK_PRESENT_MODE_IMMEDIATE_KHR), as described in #806 ?There is indeed difference for me in
DXVK_HUD=fps,frametimes d3d11-triangle.exetest.dxgi.numBackBuffers = 4: 2300+ fpsSame when I trying to force
VK_PRESENT_MODE_MAILBOX_KHR.