https://bugs.winehq.org/show_bug.cgi?id=51181
--- Comment #1 from Henri Verbeet hverbeet@gmail.com --- Some comments:
- From the results, it looks like the affected configurations are mishandling the instance data step rate of "2", instead behaving as if it was "0". In principle that would warrant a broken(), but there's also a small chance it could be avoided by using a different vertex data format like DXGI_FORMAT_R8G8B8A8_UNORM instead of DXGI_FORMAT_R8_UNORM. If the latter works, that would probably be preferred.
- This test has a d3d11 equivalent, and the affected configurations are failing in the same way there.
- It's perhaps overly broad to say "AMD GPUs". At first sight, the only AMD results we have on test.winehq.org are the win*_cw-rx460-*, and win2009_fgtb-*-rx550-* results. The "rx460" appears to actually be an RX 560, but in any case, those are all AMD POLARIS cards. On the other hand, these are certainly succeeding on my AMD GPU here, and presumably they were for Józef when he wrote that test.