12 Mar
2025
12 Mar
'25
7:10 p.m.
On Wed Mar 12 18:58:46 2025 +0000, Nikolay Sivov wrote:
In where? I mean if we have this single function now that will presumably enable every quirk it needs to enable in vkd3d-shader, using just a version number, we don't really need those non-standard options in vkd3d api. That's what I meant. I think there's a bit of talking-past going on here; Matteo is pointing out that D3DCompile2VKD3D() doesn't currently have this version-specific behaviour implemented yet, so we need to submit a patch to vkd3d for it.
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/6925#note_97583