12 Mar
2025
12 Mar
'25
7:19 p.m.
On Wed Mar 12 19:11:22 2025 +0000, Elizabeth Figura wrote:
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.
Well sure, I'm talking about vkd3d-shader side already, whether we want this option exposed and documented for any vkd3d_shader_compile() user, or make it into something internal. I don't see how any end user of vkd3d-shader, outside of wine, would think of using any of those custom options. Also I'm surprised we ended up having any logic involving windows module version numbering in vkd3d-shader.