https://bugs.winehq.org/show_bug.cgi?id=44143
--- Comment #12 from Józef Kucia joseph.kucia@gmail.com --- (In reply to Markus Elfring from comment #11)
Do you find another message worth for further considerations?
002e:warn:d3d9:d3d9_device_QueryInterface {580ca87e-1d3c-4d54-991d-b7d3e3c298ce} not implemented, returning E_NOINTERFACE.
No, it's harmless.
(In reply to Markus Elfring from comment #10)
- Can this log output be filtered for the details which would be really
needed for further clarification?
A complete log would be preferred. Logs compress very well.
(In reply to Markus Elfring from comment #9)
Can such development challenges be distinguished from difficulties with related software components like Mesa anyhow?
Generally, someone has to debug the issue and see where the things go wrong in order to confirm if it's a bug in Wine or in a graphics driver.
There are some shortcuts though, e.g. you could record an apitrace [1], upload it somewhere, then I could inspect OpenGL commands generated by Wine for your version of the game, and replay the trace on a different hardware.
[1] - https://github.com/apitrace/apitrace