Add patches for FIFO Latest Ready support

[silvanshade]

This PR adds patches for VK_PRESENT_MODE_FIFO_LATEST_READY_KHR.

Both dxvk and vkd3d-proton are modified.

FIFO Latest Ready is preferred over Mailbox when supported.

The second change adds a new option VKD3D_CONFIG=tear_free. If specified, this option changes the behavior when finding the unlocked mode to prefer tear-free modes, so FIFO Latest Ready or Mailbox will be chosen before Immediate.

The new option is intended to be similar in behavior to dxvk.tearFree. This also makes it possible to override an application to use an unlocked tear-free mode:

DXVK_CONFIG="dxgi.syncInterval = 0" VKD3D_CONFIG=tear_free

These patches are taken from the respective upstream PRs:

• [dxvk] Support VK_PRESENT_MODE_FIFO_LATEST_READY_KHR doitsujin/dxvk#5550
• vkd3d: Support VK_PRESENT_MODE_FIFO_LATEST_READY_KHR HansKristian-Work/vkd3d-proton#2874

I'm submitting the patches here in the meantime in case someone wants to try them out with proton.

Tested working on an NVIDIA GeForce RTX 5090 with driver 595.45.04.

[loathingKernel]

Thank you for the PR, appreciate it.

While this seems rather harmless on its own, I have made it a habit of not touching upstream DXVK or VKD3D. Sometimes people report issues with things we do here to upstream projects, which rightfully causes friction, thus I try to keep any testing stuff either optional or out of wide circulation.

I want to include this, so I think I could make it part of the dxvk-llsasync build, and maybe include another alternative vkd3d-proton build for this, descriptor-heaps or any other future experimental stuff. So give me some time to think about how to go about it.

[silvanshade]

Thanks.

Understand your point about the upstream issue reporting.

Just to be clear, I was mainly offering this as a way for people to experiment with it, so I wouldn't expect it to be part of a main release. Maybe an experimental one like you suggested though, with the usual caveats.

[silvanshade]

I think I will close this since these PRs have changed upstream.

I've submitted an alternate vkd3d-proton PR that allows to directly configure the present mode which is more flexible and should be less controversial since it doesn't favor any present mode implicitly. I've closed the dxvk PR pending a possible rewrite to do the same thing there.

For anyone looking for this functionality in the meantime, MangoHud just merged a PR that also allows to specify the Vulkan present mode directly in a similar way, including supporting FIFO Latest Ready.

[loathingKernel]

Thank you for the update and sorry for not trying them out earlier. Too many things have been happening lately, and I just got back to this PR today, and show that the DXVK one was closed. After reading the conversation there, I thought it would be better to wait some more for things to settle.