On Fri Dec 6 20:53:38 2024 +0000, Elizabeth Figura wrote:
I've submitted a new version that uses D3DCompile2VKD3D() directly, including from d3dx9. This does require the latest version of vkd3d, which can make e.g. bisecting difficult. This is not a new problem, but it was raised to me off-list. Unfortunately there is not really a way to prevent this without significant changes. The vkd3d headers do not include any indication of the version, and we cannot rely on compile tests since we cannot access config.h.
Yeah, it's tricky, but if we have to "break" bisecting better sooner rather than later, I guess.
Honest question: which version do you prefer, this or the old one? Having now seen both, I'm okay with either.