Re: Unable to completely replace vkd3d with vkd3d-proton?

Hi,

Il 27/11/24 17:16, Francisco Casas ha scritto:
> The version of vkd3d in stable releases of Proton (not to be confused 
> with vkd3d-proton) keep this hack to avoid regressions.
> 
> You can apply the following patch to your vkd3d in proton before 
> compiling proton to add the hack again.
> 
> https://gitlab.winehq.org/fcasas/vkd3d/-/ 
> commit/4d2637bfc66edd449745b7410043b81b68189af7

To add to what Francisco said, notice that a merge request is open to 
update the vkd3d version shipped with Wine 
(https://gitlab.winehq.org/wine/wine/-/merge_requests/6899). This was 
just accepted by Matteo, so it's likely to be merged soon (and you can 
merge it in your Wine copy anyway).

It won't add support for overload resolution, though, so you'd still 
probably want to use Francisco's patch. However, it shouldn't be too 
hard to apply it directly to Wine's embedded copy of vkd3d. That way you 
can spare yourself from the complexity of crosscompiling vkd3d to PE.

Gio.

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQSpO7VGf+9dH7iic+7pbX5hj2wLgwUCZ0gz2QAKCRDpbX5hj2wL
g0slAP46tJm5Rjn9jecDmP4a5vnJ5/7JoPKPFYLvbJw9EmNfSgD/R5uyuHZgwqc/
lReX1xZ3mi40xsuDpBBsvP+kh1BhkwI=
=eskH
-----END PGP SIGNATURE-----