https://bugs.winehq.org/show_bug.cgi?id=46118
--- Comment #8 from Henri Verbeet hverbeet@gmail.com --- (In reply to Nathan from comment #7)
The minor graphical glitches can be reproduced with a demo.
Ok, so in principle I should be seeing these as well.
command: dmidecode ...snip... Processor Information Version: AMD A10-9600P RADEON R5, 10 COMPUTE CORES 4C+6G
command: fglrxinfo display: :0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon R7 Graphics OpenGL version string: 4.5.13399 Compatibility Profile Context 15.201.1151
Hmm, maybe this is specific to fglrx/Catalyst. I think most people are either using something Mesa-based or proprietary NVIDIA. It may be interesting to see whether anyone else can reproduce this, either with or without fglrx. If it's easy for you, it may also be interesting to know whether the issue goes away for you when switching to Mesa/radeonsi.
As for debugging this, in principle what you'd do would be to enable something like WINEDEBUG="+d3d9,+d3d,+tid,+seh", disable csmt if possible, and force a backtrace on GL_DEBUG_TYPE_ERROR_ARB in wined3d_debug_callback(). Chances are that that will either make the issue go away though, or result in a log that's too large to attach here.