https://bugs.winehq.org/show_bug.cgi?id=44964
--- Comment #22 from Toni tonix64@inventati.org --- (In reply to Fabian Maurer from comment #21)
(In reply to Toni from comment #19)
Fabian in this case I think it's more about an incorrect translation of shaders (see log and analysis above) inside wine so not sure apitrace will be of much help.
Maybe I didn't make that clear, but I meant running apitrace under wine, capturing the D3D calls. This way you can replay it under wine, and let it translate the shaders again.
Yep, sorry I also didn't make myself clear, I'm talking about apitrace under wine of course... if wine is generating a bad shader and sending it over you will see the same shader you can see with wine's own debug.
Anyways who knows maybe you find something else with apitrace :)