Package Details: vkd3d-proton-mingw 3.0a-1

Git Clone URL: https://aur.archlinux.org/vkd3d-proton-mingw.git (read-only, click to copy)
Package Base: vkd3d-proton-mingw
Description: Fork of VKD3D. Development branches for Protons Direct3D 12 implementation
Upstream URL: https://github.com/HansKristian-Work/vkd3d-proton
Licenses: LGPL-2.1
Conflicts: vkd3d-proton
Provides: vkd3d-proton
Submitter: loathingkernel
Maintainer: loathingkernel
Last Packager: loathingkernel
Votes: 4
Popularity: 0.147763
First Submitted: 2021-09-22 23:30 (UTC)
Last Updated: 2025-11-20 11:21 (UTC)

Latest Comments

lxe commented on 2025-09-11 01:59 (UTC)

for clarity, this is the one that ends up compiling the dll's that you can use with wine. The vkd3d-proton-git and lib32-vkd3d-proton-git only build the .so's (I'm not quite sure why)

dreieck commented on 2025-05-26 09:34 (UTC)

vkd3d and vkd3d-proton at this point are completely different projects sharing very little or even nothing other than the name.

Thanks.

OK, that's confusing.

I added comments to vkd3d-proton-git and lib32-vkd3d-proton-git: [1], [2].

Maybe you want to/ can say more to make sense to the maintainers of those packages.

Regards!

loathingkernel commented on 2025-05-26 09:04 (UTC) (edited on 2025-05-26 09:06 (UTC) by loathingkernel)

vkd3d and vkd3d-proton at this point are completely different projects sharing very little or even nothing other than the name.

vkd3d has remained in the repos from the time wine needed it. For the past two major versions at least, wine-9.0 and wine-10.0, vkd3d has been bundled with wine's source.

dreieck commented on 2025-05-26 09:02 (UTC) (edited on 2025-05-26 09:02 (UTC) by dreieck)

I argue from the standpoint that vkd3d (without -proton) is even in the main repositories (but not vkd3d-mingw), and that this also installs .so and not .dll files.

From this I conclude that the Linux native version is the default.

loathingkernel commented on 2025-05-26 08:45 (UTC) (edited on 2025-05-26 08:47 (UTC) by loathingkernel)

@dreieck

I would argue that these packages have a confused identity

They build from the vkd3d-proton repo but they list the wine upstream vkd3d as the url, and they are building the linux native libraries, which could be packaged as libvkd3d-proton following the way libdxvk naming for native dxvk packaging.

Since vkd3d-proton is primarily meant to be used as Windows dlls with Wine, I'd argue that these should have priority of the vkd3d-proton name.

dreieck commented on 2025-05-26 08:21 (UTC) (edited on 2025-05-26 09:00 (UTC) by dreieck)

This actually differs from vkd3d-proton as the former installs Linux .so files and header files, and this here installs .dll files. So they neither should conflict nor provide each other.