Rename vkd3d to vkd3d-proton, and add version 2.5. about components HOT 10 CLOSED

@mirkobrombin Yeah I looked in vkd3d-proton-2.5/setup_vkd3d_proton.sh, at the top you will see:

vkd3d_lib32=${vkd3d_lib32:-"x86"}
vkd3d_lib64=${vkd3d_lib64:-"x64"}

It loads the DLLs from the correct dirs. :)

from components.

Closed by 6e0c51f

from components.

@mirkobrombin Great news! Thanks! <3

from components.

I was looking into making a pull request for the update but I dunno. I see this file:

https://github.com/bottlesdevs/components/tree/main/vkd3d

Which reveals that you pull from a Lutris fork of VKD3D-Proton:

https://github.com/lutris/vkd3d/

This seems really strange to me. It's hundreds of commits behind the real project?

Let's just pull directly from the real project at https://github.com/HansKristian-Work/vkd3d-proton/releases.

Because this is just a DLL file which emulates DX12 and translates it to Vulkan graphics API. It isn't dependent on Proton or Steam. So we should go straight to Valve's official version at the HansKristian-Work repo. That's where the innovation happens.

from components.

Official vkd3d builds came in zst format which is not supported in Bottles. Lutris provide builds in tar.xz format which is compatible. We are planning to build our vanilla builds, until this we stuck on lutris one

from components.

@mirkobrombin Ah okay I understand, makes sense, I see the .zst extension on the releases yeah.

Well, it looks like Lutris fork has 2.5 too, so we can update to that one for now. :)

https://github.com/lutris/vkd3d/releases

It's a little bit behind the official 2.5 release (the official 2.5 has like 10-20 more commits), but good enough.

from components.

The problem with lutris releases is that they eventually remove them or update attachments, I am waiting to see if this is not happening to update. We will probably finish our builds in the meantime

from components.

@mirkobrombin Ahh I see, yeah that's a problem. Also it's weird that their 2.5 build is on an older tag than the official 2.5 release.

Well, I can do without DXR raytracing support in the meantime (2.5 marks DXR 1.0 as "mostly stable" and DXR 1.1 as "works in some games" so it's a big update for that). But raytracing is not very useful for most games. :D

from components.

@mirkobrombin Hey :) I was just working on trying to add VKD3D 2.5 and I noticed this commit:

8d567b3

One surprising thing is that v2.5 has renamed the DLL folders. It turns out that the Lutris version we had before in Bottles uses x32 folder for x86 architecture. The official VKD3D rep uses x86 folder.

• setup_vkd3d_proton.sh: Identical in Lutris 2.4 and Official 2.5
• 32-bit folder: x32 in Lutris 2.4, x86 in Official 2.5
• 64-bit folder: x64 in both.

Bottles may not be ready to handle the new name for 32-bit DLL.

Edit: I noticed that your new file is a special build for this project, awesome! :D

Edit 2: I can't find any references to the DLL files or to the script in /Bottles repo, so I can't figure out how Bottles loads these DLLs. Perhaps the renamed folders don't matter. :) But letting you know just in case! :)

from components.

Bottles handle dxvk and vkd3d with their official scripts. So every path change do not compromise the components installation.

Also we removed the -proton suffix to avoid users to miss understanding its purpose (it is not proton specific).

from components.