On Thu Sep 28 19:11:57 2023 +0000, Henri Verbeet wrote:
Is this waiting for tests or for something else? Regarding tests, I
don't see right now how this could fit in current shader runner, we might be able to compile test, but anything else requires effects handling in the runner. From my point of view, the main thing it needs is sign-off by Zeb and Giovanni. I think tests would be helpful though, and making sure things (and non-effect profiles in particular) at least compile seems like a good start. Support for actual effect handling in the shader runner would be a fair bit more involved, but perhaps not terribly hard either? I imagine that initially we'd just need a way to verify the state contained in a compiled effect.
What we can do is some extension to our tests that will check state objects for initial values, this will only cover statically initialized ones at first. I don't think it should necessarily render anything. Unfortunately this is tied to d3d API too much, and we'll have to provide some sort of dxvk-like layer. I was thinking we might start using d3dcompiler for d3d10/d3d9 effects tests, once the compiler is capable enough. That would validate at least something, and would be stable enough because of the imported vkd3d.