The vkd3d team is proud to announce that release 1.13 of vkd3d, the Direct3D to Vulkan translation library, is now available. This release contains improvements that...
Maybe not, but doesn’t really answer my question what this would be used for.
I’m not hating, just interested; my last knowledge was that if you wanted to play Direct3D 12 games, you’d need the proton fork. But I don’t know many other things Direct3D is used for, so…
The ultimate goal of the WIneHQ team is to have their own fully DX12 implementation. The reason why vkd3d-proton exists is that Valve didn’t want to wait for it to mature and AFAIK they did have differences in what should be included in vkd3d. Which is why they don’t work on the same project.
Is this at this point useful as anything else than being a base for vkd3d-proton?
I’m pretty sure vkd3d-proton does not rebase from vkd3d.
Maybe not, but doesn’t really answer my question what this would be used for.
I’m not hating, just interested; my last knowledge was that if you wanted to play Direct3D 12 games, you’d need the proton fork. But I don’t know many other things Direct3D is used for, so…
The ultimate goal of the WIneHQ team is to have their own fully DX12 implementation. The reason why vkd3d-proton exists is that Valve didn’t want to wait for it to mature and AFAIK they did have differences in what should be included in vkd3d. Which is why they don’t work on the same project.
Doesn’t it do dx12 translation?
Yeah but to my knowledge only limited, when I tried it back then, D2R wouldn’t run with it, you’d need vkd3d-proton.