[Not-an-Issue] DXVK will not be adding VK_EXT_present_timing functionality

[Digger1955]

Greetings, @netborg-afps

doitsujin's quote:

FWIW, I am also no longer interested in any kind of present timing support in DXVK. That entire extension is just completely unusable and the only thing it's ever going to do is break on various kinds of setups that we don't / can't test.

Link to the quote: doitsujin#5340 (comment)

No answer is needed, I am informing you, because I know that you and doitsujin agreed that upstream DXVK will implement VK_EXT_present_timing.

You can close the issue as soon as you read this message.

[netborg-afps]

Oh well, this is unfortunate. So I probably have to implement it on my own.

[LZeugirdor]

Oh well, this is unfortunate. So I probably have to implement it on my own.

Just to let you know, I really appreciate it. I feel as though doitsujin's has been very dismissive and close minded about the entire issue. I understand an open source project is not required to cater to anyone specific, but for something many people depend on, his takes have a scary connotation on the future of dependability, reliability, and capability of tools we use in the open source community. It's one thing to say they won't do the work themselves, it's another to actively shut down discussion and work towards making it happen and implementing it.

So again, thank you if you do decide to work on this, and even if you don't, allowing others to work on it and merge would still be better than what doitsujin's been doing in regards to the community. Frame limiting in dxvk has always been significantly better for me than alternatives such as in-game, manghud and gamescope for a variety of reasons.

[netborg-afps]

It is what it is. He still does a spectacular job and I respect he wants to limit his scope, but hopefully he'll eventually realize that pacing related things absolutely need to tightly communicate with dxvk. It's not good for the community him advertising inferior solutions that only operate in the Vulkan domain. The Direct3D domain is where games are rooted at and that domain needs to be respected in order to get great frame pacing / fps limiting.

Not sure how much time I'll have in the near future, but I definitely want to get present_timing in. At first I'll check out its effect in vkd3d-low-latency - since it's already available there - it just needs to talk to the pacing, then depending on the results, I'll have the motivation to implement it in dxvk or not.