On 25 October 2013 17:09, Stefan Dösinger stefandoesinger@gmail.com wrote:
I was thinking about marking some of those results broken, but in the end I couldn't find an argument why the results from GPU A are more correct than the results from GPU B, especially when considering that the differences between ddraw versions on the same GPU are just as big and strange as the differences between GPUs.
Yeah, but broken() is really more about what behaviour we want Wine to follow as opposed to some judgment about what's correct. I think it makes sense to try to be somewhat consistent there. Obviously that doesn't apply for things that depend on e.g. the hardware implementation, but this is for things that are purely in our ddraw/wined3d implementation.